Allow user to force using the current develop branch version when merging a feature #239
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
…ore the feature version before merging into develop
|
@bcluap Please commit your specific changes in different branch. You can force push to this one or create another PR. |
|
@bcluap Can you clean this up? |
|
@bcluap Are you still interested in this feature? If yes, can you clean this PR so I can review it. |
|
Pretty old one, let's focus on #367. |
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 is a fix for #238
Also note this is not just new functionality. This also fixes a bug where the feature version was not being correctly handled if skipTestProject=true