Repository navigation
Remove relock composite action - #72
Conversation
When the workflow token lacks access to a private action repository, the relock step now emits a ::warning:: annotation telling the user to run gh actions-lock locally instead of failing the entire workflow. This prevents Dependabot PRs from being blocked by token permission gaps that can only be resolved locally.
There was a problem hiding this comment.
⚠️ Not ready to approve
The new Bash snippet uses echo in a way that can subtly corrupt/alter captured output and makes the error-detection check less reliable; a small adjustment (e.g., printf + grep -F on the variable) is needed.
Pull request overview
This PR updates the actions/relock composite action so that when gh-actions-lock fails specifically due to a workflow token lacking access to a private repository (“repository not found or not accessible”), the workflow emits a ::warning:: and continues instead of failing the job—unblocking Dependabot PR workflows while still surfacing the remediation path.
Changes:
- Capture
gh-actions-lockstdout/stderr and exit code instead of letting the step fail immediately. - Detect the “repository not found or not accessible” failure mode and convert it into a workflow warning with an exit code of 0.
- Preserve existing behavior (non-zero exit) for all other error cases.
File summaries
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Low
Note
Your feedback helps us improve the quality of this feature.
Please use 👍 or 👎 to tell us whether this assessment is correct.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
The relock composite action can't work in practice — the workflow token (GITHUB_TOKEN) doesn't have access to private action repos like github/gh-actions-lock itself, so resolution always fails. See: github/actions-dispatch#768
nodeselector
changed the title
Removes
actions/relock/entirely. The relock composite action can't work in practice --GITHUB_TOKENdoesn't have access to private action repos likegithub/gh-actions-lockitself, so resolution always fails for any repo that uses private actions.Ref: https://github.com/github/actions-dispatch/issues/768