chore: add concurrency and run name configuration to rollout workflow#18096
chore: add concurrency and run name configuration to rollout workflow#18096
Conversation
There was a problem hiding this comment.
Pull request overview
This PR enhances the CentralRepoOps documentation by adding concurrency controls and run name configuration to the Dependabot rollout worker workflow example. These additions help prevent workflow conflicts when multiple rollouts target the same repository and provide better workflow run visibility.
Changes:
- Added
run-nameconfiguration to display the target repository in workflow runs - Added workflow-level concurrency control to prevent multiple runs for the same target repository
- Added engine-level concurrency control to isolate AI execution per repository
- Added
persist-credentials: falseto the checkout action as a security best practice
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| with: | ||
| token: ${{ secrets.ORG_REPO_CHECKOUT_TOKEN }} | ||
| repository: ${{ github.event.inputs.target_repo }} | ||
| persist-credentials: false |
There was a problem hiding this comment.
The addition of persist-credentials: false is not mentioned in the PR title or description, which only references adding concurrency and run name configuration. While setting persist-credentials: false is a security best practice when using a custom token (to prevent the token from being persisted in the Git config), this change should be documented in the PR description to ensure it's an intentional modification rather than an accidental inclusion.
central-repo-opsdocumentation to improve concurrency handling, workflow naming.