[CI] Skip CI for non-runtime directories#7870
Conversation
|
/skip-ci ci_iluvatar |
|
Thanks for your contribution! |
05f3165 to
754bd24
Compare
754bd24 to
7c2846f
Compare
CI报告基于以下代码生成(30分钟更新一次): 1 任务总览Required 任务当前无失败、无运行中、无等待中;本 PR 属于 CI skip 规则调整,部分测试任务按跳过逻辑被跳过。建议重点关注 Optional 失败任务是否需要人工确认;Required 侧暂无阻塞。
2 任务状态汇总2.1 Required任务 : 2/10 通过
2.2 可选任务 — 22/32 通过
3 失败详情(仅 required)无 required 失败任务。本次未调用深度失败分析;Optional 失败任务不阻塞合并,仅在上方可选任务区展示。 |
|
/skip-ci all |
c5c2e5f to
9fd57f7
Compare
PaddlePaddle-bot
left a comment
There was a problem hiding this comment.
🤖 Paddle-CI-Agent | pr_review |
2026-05-28 11:49:58
📋 Review 摘要
PR 概述:为 CI 跳过检查规则新增非运行时目录白名单(.claude/、benchmarks/、docs/、dockerfiles/、examples/、tools/),减少不必要的 CI 触发。
变更范围:.github/workflows/check-bypass.yml
影响面 Tag:[CI]
问题
未发现阻塞性问题。PR 规范问题在下面章节报,不要在这里重复。
历史 Findings 修复情况
| Finding | 问题 | 状态 |
|---|---|---|
| F1 | Checklist "Add unit tests" 未勾选且未说明原因 |
📝 PR 规范检查
Checklist 中 "Add unit tests" 项未勾选且未在 PR 中说明原因,模板要求 "Please write the reason in this PR if no unit tests"。建议在描述中补充说明(如:本 PR 仅修改 CI 配置,无需添加单元测试)。
标题建议:标题合规,无需修改。
PR 描述建议(点击展开,可直接复制)
## Motivation
Changes under documentation, tooling, benchmark, and auxiliary configuration directories do not affect runtime behavior directly. Running full CI for these modifications increases unnecessary resource usage and slows down development workflow.
## Modifications
- Added CI skip rules in `.github/workflows/check-bypass.yml` for changes under:
- `.claude/`
- `benchmarks/`
- `docs/`
- `dockerfiles/`
- `examples/`
- `tools/`
- Reduced unnecessary CI triggering for non-runtime related changes.
## Usage or Command
N/A
## Accuracy Tests
N/A
## Checklist
- [x] Add at least a tag in the PR title.
- Tag list: [`[FDConfig]`,`[APIServer]`,`[Engine]`, `[Scheduler]`, `[PD Disaggregation]`, `[Executor]`, `[Graph Optimization]`, `[Speculative Decoding]`, `[RL]`, `[Models]`, `[Quantization]`, `[Loader]`, `[OP]`, `[KVCache]`, `[DataProcessor]`, `[BugFix]`, `[Docs]`, `[CI]`, `[Optimization]`, `[Feature]`, `[Benchmark]`, `[Others]`, `[XPU]`, `[HPU]`, `[GCU]`, `[DCU]`, `[Iluvatar]`, `[Metax]`]
- You can add new tags based on the PR content, but the semantics must be clear.
- [x] Format your code, run `pre-commit` before commit.
- [ ] Add unit tests. Please write the reason in this PR if no unit tests.
- 本 PR 仅修改 CI 配置文件(`.github/workflows/check-bypass.yml`),无需添加单元测试。
- [ ] Provide accuracy results.
- [ ] If the current PR is submitting to the `release` branch, make sure the PR has been submitted to the `develop` branch, then cherry-pick it to the `release` branch with the `[Cherry-Pick]` PR tag.总体评价
变更逻辑清晰,Bash 正则语法正确,continue 跳过白名单目录的实现符合预期,不影响已有 .md/.yaml/.go 判断路径。PR 规范问题不阻塞合入。
Motivation
Changes under documentation, tooling, benchmark, and auxiliary configuration directories do not affect runtime behavior directly. Running full CI for these modifications increases unnecessary resource usage and slows down development workflow.
Modifications
.claude/benchmarks/docs/dockerfiles/examples/tools/Usage or Command
N/A
Accuracy Tests
N/A
Checklist
[FDConfig],[APIServer],[Engine],[Scheduler],[PD Disaggregation],[Executor],[Graph Optimization],[Speculative Decoding],[RL],[Models],[Quantization],[Loader],[OP],[KVCache],[DataProcessor],[BugFix],[Docs],[CI],[Optimization],[Feature],[Benchmark],[Others],[XPU],[HPU],[GCU],[DCU],[Iluvatar],[Metax]]pre-commitbefore commit.releasebranch, make sure the PR has been submitted to thedevelopbranch, then cherry-pick it to thereleasebranch with the[Cherry-Pick]PR tag.