Skip to content

chore: add concurrency and run name configuration to rollout workflow#18096

Merged
mnkiefer merged 1 commit intomainfrom
upd-central-repo-ops
Feb 24, 2026
Merged

chore: add concurrency and run name configuration to rollout workflow#18096
mnkiefer merged 1 commit intomainfrom
upd-central-repo-ops

Conversation

@mnkiefer
Copy link
Contributor

@mnkiefer mnkiefer commented Feb 24, 2026

  • Updates the workflow configuration in the central-repo-ops documentation to improve concurrency handling, workflow naming.

@mnkiefer mnkiefer self-assigned this Feb 24, 2026
Copilot AI review requested due to automatic review settings February 24, 2026 07:50
@mnkiefer mnkiefer merged commit ec76f09 into main Feb 24, 2026
78 checks passed
@mnkiefer mnkiefer deleted the upd-central-repo-ops branch February 24, 2026 07:51
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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-name configuration 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: false to 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
Copy link

Copilot AI Feb 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants