THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
-n
option is need to avoid tagging the release, the Maven Release plugin did that already. If the release branch was published to the remote it won't be deleted locally, it must be done manually after removing branch from the remote:
Code Block |
---|
git push --delete origin release/X.X.X.X |
This will remove the branch from the remote, now we can merge once more the release branch (when on develop
) and remove it
...
Now both master
and develop
branches should be up to date with the changes introduced by the release.
...