Fix minimum token permissions for workflows that perform git push #47
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.
This PR ensures that all GitHub workflows performing git push operations have the required "contents: write" permission with appropriate trailing comments as requested.
Changes Made
# required for pushing changesto thecontents: writepermission in.github/workflows/auto-update-pull-request.ymlAnalysis Summary
Reviewed all 52 GitHub workflow files and identified 8 workflows that perform git push operations:
✅ Already compliant workflows (had correct permissions with comments):
prepare-release-branch.yml- "# for git push to PR branch"auto-update-otel-sdk.yml- "# for git push to PR branch"release-update-cloudfoundry-index.yml- "# for git push to PR branch"overhead-benchmark-daily.yml- "# for git push to gh-pages branch"backport.yml- "# for git push to PR branch"release.yml- "# for git push to PR branch"prepare-patch-release.yml- "# for git push to PR branch"🔧 Fixed workflow:
auto-update-pull-request.yml- Added required comment to existingcontents: writepermissionAll workflows that perform git push operations now have proper "contents: write" permissions with trailing comments explaining why the permission is needed.
Fixes #46.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.