Conversation
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
|
To view in Slack, search for: 1758127215.090299 |
There was a problem hiding this comment.
Codex Review: Here are some suggestions.
Reply with @codex fix comments to fix any unresolved comments.
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, or 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 fix this CI failure" or "@codex address that feedback".
| # Commit generated version metadata and README updates on release tags | ||
| - name: Auto-commit release assets | ||
| if: github.event_name == 'push' && steps.version.outputs.tag == 'latest' | ||
| uses: stefanzweifel/git-auto-commit-action@778341af668090896ca464160c2def5d1d1a3eb0 # v5 | ||
| with: | ||
| commit_message: "chore(release): sync generated assets [skip ci]" | ||
| branch: main | ||
| file_pattern: 'package.json **/package.json charts/**/Chart.yaml charts/**/README.md README.md' |
There was a problem hiding this comment.
[P1] Grant write permissions before auto-committing release assets
The new auto-commit step pushes generated files back to main, but the job’s permissions earlier in this workflow restrict the default GITHUB_TOKEN to contents: read. With read-only token scopes, git-auto-commit-action will fail when attempting to push on release tag runs, causing the QA workflow to fail. Either increase the job’s contents permission to write or use a separate PAT so the commit can actually be created.
Useful? React with 👍 / 👎.
3f5ca06 to
826d1d5
Compare
826d1d5 to
1f56cd3
Compare
Summary
Testing