Try out GH auto merge and merge queue

[dibyom]

Feature request

Currently, we use Tide to manage merging PRs when tests pass. GitHub has also now similar functionality:

1. https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository

2. https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue

Use case

• This could simplify some of our CI configuration but also help us move towards Dogfooding Roadmap - Tekton Based CI/CD for Tekton #912

Approach

• 1. Try experimenting with auto merge with a lower traffic repo (where we probably don't need the merge queue) e.g. triggers/cli/operator
• 2. Wait till we are in merge queue beta
• 3. Modify our CI jobs to run on pushes to gh-readonly-queue/ branch: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue#about-merge-queues
• 4. Try merge queue in one of the lower traffic repos
• 5. If experiment is successful, try with tektoncd/pipeline

[afrittoli]

Thanks Dibyo - I think it would be ok to experiment.
I'm a bit wary about switching an open source tool like tide for a closed source alternative though.

[dibyom]

I'm a bit wary about switching an open source tool like tide for a closed source alternative though.

That's a fair concern but we do already use GItHub for a lot already :) My main motivation though was that I wasn't sure if we could still rely on tide when we are fully off of Prow for running our presubmit tests (maybe we can and I'm wrong)

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.