为代码检查集成 reviewdog - #6692
Conversation
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c7ef111911
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e940f016e7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - '**.properties' | ||
|
|
||
| permissions: | ||
| checks: write |
There was a problem hiding this comment.
For pull requests submitted from forks, GitHub downgrades GITHUB_TOKEN write permissions to read-only, as documented under permissions for forked repositories. Consequently, the github-pr-check reporter cannot create the intended Check annotations for external contributors despite checks: write; publish the reports from a trusted follow-up such as a workflow_run workflow rather than relying on this token in the untrusted PR run.
Useful? React with 👍 / 👎.
2 participants
优化代码检查流程，通过
reviewdog将检查结果直接体现在 PR 状态检查中。https://github.com/reviewdog/reviewdog
https://github.com/reviewdog/action-setup