releaseMergeFFOnly is not used when merging release to develop. #60
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
Typically the develop branch moves on while the release is being prepared. Therefore it does not make sense to require the use of fast-forward when merging to the develop branch. On the master branch, however, it is useful to be able to require the use of fast-forward to make sure that the final commit on the release branch ends up in the master branch unmodified.
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.
Typically the develop branch moves on while the release is being prepared. Therefore it does not make sense to require the use of fast-forward when merging to the develop branch.
On the master branch, however, it is useful to be able to require the use of fast-forward to make sure that the final commit on the release branch ends up in the master branch unmodified.