[Feature Request] Add flag to enable/disable auto-merge logic #1
Conversation
This file contains hidden or 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
- Once the auto merge is disabled, will command on the PR to remind users this PR branch is not up to date. Signed-off-by: Kent Huang <kent@infuseai.io>
Signed-off-by: Kent Huang <kent@infuseai.io>
kentwelcome
force-pushed
the
feature/add-flag-to-disable-auto-merge
branch
from
bcb9d52 to
0c3d7d4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What does this PR do?
In this PR, we add a flag
autoMergeto configure the PR-Update action.Once the
autoMergeflag has been set tofalse,the action will post a comment on PR to remind the user instead of merging the base branch directly.Also, the user can use
descriptionMergedanddescriptionMergedto customize the output message of git commit and PR comment.By the way, the default value of
auto mergewill betrue, and it's not a required field.Adding this flag wrong changes the existing behavior if the user doesn't modify their GitHub action workflow.
Why is this PR needed?
It's great to know if a PR branch is up-to-date.
However, in some cases, auto-merging the base branch without user interaction is too aggressive.
By using
autoMergeflag, the user can configure the action behavior based on the need.