fix(ci): grant contents:write to deploy-dev for commit annotation#419
Merged
Conversation
The #416 hardening set the workflow to contents:read top-level, but peter-evans/commit-comment needs contents:write, so the "Annotate commit" step 403'd on the first next push (run 27433460512). The GitLab trigger itself succeeded; only the annotation failed. Scope the write grant to the deploy-dev job, keeping the build job at read. Assisted-With: Claude Fable 5 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## next #419 +/- ##
=======================================
Coverage 10.68% 10.68%
=======================================
Files 195 195
Lines 17827 17827
Branches 1829 1829
=======================================
Hits 1905 1905
Misses 15875 15875
Partials 47 47 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
One-job permissions fix in
dev-conda-publish.yaml: thedeploy-devjob now haspermissions: contents: write.Why
The #416 hardening set the workflow to
contents: readtop-level. On the firstnextpush after that (the #417 dependabot merge, run 27433460512), the final Annotate commit step (peter-evans/commit-comment) failed with403 Resource not accessible by integration— creating a commit comment requirescontents: write.Delivery impact: none. The GitLab trigger step succeeded before the annotation failed, so the dev deploy pipeline for the analysis cluster fired normally; only the cosmetic commit-comment annotation was lost.
The grant is scoped to the
deploy-devjob only;dev-conda-buildstays at the top-levelcontents: read.Checked HyperCTui / CGC / NIS for the same pattern — no other repo uses
commit-comment, so this is iBeatles-only.🤖 Generated with Claude Code