Add workflow to auto merge PRs #2485
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
michaelbeaumont
added
area/build-and-release
skip-release-notes
|
This is mostly alleviated by using the new |
michaelbeaumont
force-pushed
the
automerge
branch
from
0296abe
to
9bc45ba
Compare
michaelbeaumont
force-pushed
the
automerge
branch
from
9bc45ba
to
f0c9f3b
Compare
cPu1
approved these changes
Aug 21, 2020
It will always fail for forks and it's unlikely that a PR review will be the step before an automerge (usually the label comes after an approval OR a check completes). In cases where it would have triggered the workflow and a merge, the user can always manually merge after their approval anyway.
hacktoberfun
added a commit
to hacktoberfun/hacktoberfest-pr-sink
that referenced
this pull request
Oct 5, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
With this PR, we can add labels
automergeorautosquashto merge the PR when it becomes ready. Additionally,autoupdatewill merge changes from the base branch into the PR.This workflow needs to be in the target branch before it can work (i.e. this PR needs to be merged first)
One small limitation is that the workflow isn't triggered when a PR becomes out of date, it will only update it if another trigger happens and it sees it's out of date.
Checklist
README.md, or theuserdocsdirectory)area/nodegroup), target version (e.g.version/0.12.0) and kind (e.g.kind/improvement)