-
Notifications
You must be signed in to change notification settings - Fork 96
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
Support different methods for merging a pull request via autosubmit and revert #2442
Conversation
This reverts commit 0555407.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some minor comments/nits, otherwise LGTM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One change reqeust
d9058db
to
b4074dc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Abandoning this because the commit history for this branch is not in a good state. |
This change will allow users to specify the merge strategy type by adding a comment to the open pull request in the format of:
'@autosubmit:merge',
'@autosubmit:rebase',
or
'@autosubmit:squash'.
If this comment is present the chosen merge strategy will be used to merge the pull request.
The default merge strategy that will be used is squash which is what is currently used to merge a pull request via the autosubmit bot.
List which issues are fixed by this PR. You must list at least one issue.
Fixes flutter/flutter#118361
Fixes flutter/flutter#114557
If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.
Pre-launch Checklist
///
).If you need help, consider asking for advice on the #hackers-new channel on Discord.