You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default CLI format is intentionally detailed. The GitHub comment format is optimized for maintainer scanning: the visible summary is bilingual, while detailed file lists, local commands, and hold conditions are kept in collapsible sections.
30
+
23
31
## GitHub Automation
24
32
25
33
DeePTB has two advisory workflows for this plan:
@@ -29,16 +37,18 @@ DeePTB has two advisory workflows for this plan:
29
37
30
38
The comment workflow is designed for fork PRs. It checks out the trusted base commit from the main repository, reads changed file names through the GitHub API, then runs the base-branch copy of `scripts/ci/pr_review_plan.py`. It must not checkout or execute code from the fork branch.
31
39
40
+
The comment workflow may also add an Evidence section based on GitHub check status. That evidence is owned by the workflow, not by `pr_review_plan.py`, because the script only knows changed file names.
41
+
32
42
Required permissions for the comment workflow are intentionally narrow:
33
43
34
44
```yaml
35
45
permissions:
36
46
contents: read
37
-
pull-requests: read
47
+
pull-requests: write
38
48
issues: write
39
49
```
40
50
41
-
`issues: write` is needed because PR timeline comments use the issues comments API. The workflow updates the existing bot comment using a hidden marker instead of creating a new comment on every PR update.
51
+
`issues: write` is needed because PR timeline comments use the issues comments API. `pull-requests: write` is needed for repositories where GitHub requires both issue-comment and pull-request write scopes for PR timeline comments. The workflow updates the existing bot comment using a hidden marker instead of creating a new comment on every PR update.
42
52
43
53
## How To Read The Output
44
54
@@ -48,6 +58,7 @@ permissions:
48
58
- **Suggested AI review** points to the minimum recommended prompts.
49
59
- **Suggested checks** lists likely local commands for this PR.
50
60
- **Hold conditions** names situations that should stop merge until resolved or explicitly waived.
61
+
- **GitHub comment summary** shows bilingual risk, reason, and review focus, with details folded by default.
51
62
52
63
The plan is advisory. When the PR body, maintainer judgment, or scientific impact suggests higher risk than the file map, use the higher risk level.
0 commit comments