ci: .md のみ変更時は重い CI をスキップしつつ required check を維持#49
Conversation
|
Warning Review limit reached
More reviews will be available in 41 minutes and 17 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (3)
📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
yk-lab
force-pushed
the
feat/markdown-only-typo-check
branch
from
17798a2 to
d3b1c3d
Compare
- ci.yml / self-test.yml: paths-ignore 廃止、bridge job パターン導入 - docs.yml: 全変更で typo check を実行（.md に限定しない） - dorny/paths-filter で変更検出、常に成功する gate job を required check 用に追加
yk-lab
force-pushed
the
feat/markdown-only-typo-check
branch
from
d3b1c3d to
efca546
Compare
yk-lab
changed the title
## 概要 要求仕様書 NFR-5（可観測性）に対応。アクション完了時に `core.summary` で導入結果をジョブサマリに出力する。 ## 変更内容 ### `src/main.ts` - 実行中にサマリ用の情報（バージョン、アセット、cache、checksum、パス）を収集 - アクション成功時に `core.summary` で表形式のサマリを記録 - トークンは `core.setSecret` でマスク済みのため、サマリに漏れない ### ワークフロー修正（#49 フォローアップ、レビュー指摘対応） - `ci.yml` / `self-test.yml` の bridge job (`*-gate`) が `changes` job の失敗・キャンセルを正しく検出するよう修正 - `self-test.yml` に `pull-requests: read` を追加（`dorny/paths-filter` 用） ## サマリに含まれる項目 | Item | 例 | |---|---| | Version | `3.51.1` | | Asset | `task_linux_amd64.tar.gz` | | Source | `go-task/task GitHub Releases` | | Cache | `hit` / `miss` | | Checksum | `verified (SHA256)` / `skipped` / `n/a` | | Executable | `/runner/tool-cache/task/3.51.1/x64/task` | ## 注意点 - エラー発生時はこれまで通り `core.setFailed` で終了。サマリは成功時にのみ出力。 - `core.summary.write()` 自体の失敗は考慮していない（Actions API の失敗は極めて稀）。 ## 検証 - `pnpm run all` ✅ - `actionlint` ✅ - `dist/index.js` が再ビルド済み（source branch には commit しない方針） ## 参照 - Closes #39 - 要求仕様書 NFR-5
1 participant
概要
.md ファイルのみの変更時に、重い CI / self-test をスキップしつつ、branch protection の required check は常に green になるよう bridge job パターンを導入する。
変更内容
.github/workflows/ci.ymlpaths-ignoreを廃止dorny/paths-filterでコード変更の有無を判定checkjob をコード変更がある場合のみ実行check-gatejob を追加（常に成功 → required check 用）.github/workflows/self-test.ymlpaths-ignoreを廃止matrix/skip-checksumjob をコード変更がある場合のみ実行self-test-gatejob を追加（常に成功 → required check 用）.github/workflows/docs.yml.md変更時のみ発火から、全 PR/push で発火 に変更動作イメージ
check+check-gate, Self-testmatrix+skip-checksum+self-test-gate, Docstyposchanges+check-gate, Self-testchanges+self-test-gate, Docstyposfailure→ required check ❌branch protection 設定変更
required check を以下に変更してください：
CI / Typecheck / Lint / Test / Build (gate)Self-test / Self-test (gate)Docs / Typo check（任意）参照