ES-1621: active forward merge automation from 5.1 -> 5.2 #204
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
|
Jenkins build for PR 204 build 1 Build Successful: |
ronanbrowne
changed the title
ronanbrowne
requested review from
driessamyn,
jasonbyrner3,
dimosr,
rick-r3,
simon-johnson-r3,
blsemo,
Omar-awad,
aditisdesai,
vinir3,
vkolomeyko,
thiagoviana and
Sakpal
as code owners
ronanbrowne
deleted the
ES-1621-Activate-forward-merge-automation-from-5.1-5.2
branch
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.
This PR will activate forward merge automation between 5.1 and 5.2, reducing the need for manual merges. Only one PR is raised per target branch. at a time, any outstanding changes will be swept up in the next merge once PR A is merged.
PR Description generated by merge bot
The description of the PR will be automatically filled out with all pull requests carried forward in the merge.
PR Reviewers
The original authors of the pull requests will also be tagged in the forward merge so they can sanity-check their work.
Manual merges:
On occasion, you may not wish for a change to be brought forward if this is the case, on the original PR you can add the label
manual-merge. The automation checks for the presence of this label and will take no action if it is found, your change will need to be manually merged forward, if required.Slack integration:
c5-forward-merge-bot-notificationswill auto-update by a bot user once a PR is ready to be merged