You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To enhance our development workflow, we propose enabling GitHub's Merge Queue feature across all our repositories. This will ensure that pull requests (PRs) are merged only after passing all required checks, maintaining the stability of our main branches.
Action Items
1. Enable Merge Queue via Repository Rulesets
Configure repository rulesets to require a merge queue for the target branches.
Ensure that merge queue allow PRs with failed CI checks as long as last PR in a queue has all CI checks success.
Enable Merge Queue in All Repositories
Summary
To enhance our development workflow, we propose enabling GitHub's Merge Queue feature across all our repositories. This will ensure that pull requests (PRs) are merged only after passing all required checks, maintaining the stability of our main branches.
Action Items
1. Enable Merge Queue via Repository Rulesets
2. Update CI Workflows
merge_group
event.Example GitHub Actions workflow update:
Refer to GitHub’s documentation for details on the merge_group event: Events that trigger workflows.
Acceptance Criteria
Benefits of Implementing Merge Queue
By adopting the Merge Queue feature, we aim to enhance our development process’s efficiency and reliability.
The text was updated successfully, but these errors were encountered: