-
Notifications
You must be signed in to change notification settings - Fork 433
Add developer guide documentation build workflow #3997
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add developer guide documentation build workflow #3997
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ 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".
| await github.rest.issues.createComment({ | ||
| owner, | ||
| repo, | ||
| issue_number: context.issue.number, | ||
| body |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Handle lack of write permissions on forked PR comment step
The workflow tries to call issues.createComment using the default GITHUB_TOKEN whenever it runs on a pull request. For PRs opened from forks, that token is read‑only and cannot write to issues or PRs. When such a forked PR touches the developer guide, this step will consistently fail with a 403, causing the entire workflow to report failure even though the documentation build succeeded and no comment was required. Consider guarding the comment step behind a permission check, switching to pull_request_target, or marking the step continue-on-error so forked contributions do not see a failing check.
Useful? React with 👍 / 👎.
|
Developer Guide build artifacts are available for download from this workflow run: |
✅ Continuous Quality ReportTest & Coverage
Static Analysis
Generated automatically by the PR CI workflow. |
Summary
Testing
https://chatgpt.com/codex/tasks/task_e_68f59290abc88331aacb054a59356751