Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate GH Merge Queue #2154

Open
3 tasks
c-pius opened this issue Dec 27, 2024 · 0 comments
Open
3 tasks

Investigate GH Merge Queue #2154

c-pius opened this issue Dec 27, 2024 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. research

Comments

@c-pius
Copy link
Contributor

c-pius commented Dec 27, 2024

Description

GH offers a feature called merge queue. We need to investigate this as an alternative to requiring branches to be update to date before merging.

Reasons

Requiring branches to be up to date became quite cumbersome as the test pipeline takes about 30 mins to complete. If we have many pending PRs (e.g., from dependabot), it becomes cumbersome to keep an eye on the merges and updating the branches.

Acceptance Criteria

  • Understood the concept of merge queue including applicability
  • Understood the consequences of introducing a merge queue
  • Provided a knowledge sharing to the team and concluded if we want to proceed with a merge queue

Feature Testing

No response

Testing approach

No response

Attachments

No response

@c-pius c-pius added kind/feature Categorizes issue or PR as related to a new feature. research labels Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. research
Projects
None yet
Development

No branches or pull requests

1 participant