When neptune-release is invoked it will create tags and new branches, apply new patches (to clear release notes) and attempt to push references without ever validating that the local branch is up to date with its remote counterpart. This means that both a release tag and a minor release branch can be pushed before git fails due to the inability to push to one of the remote branches.
To avoid the need for a great deal of manual cleanup it seems like a good idea for neptune-release to first fetch from the remote and validate that the current branch is up to date.
When
neptune-releaseis invoked it will create tags and new branches, apply new patches (to clear release notes) and attempt to push references without ever validating that the local branch is up to date with its remote counterpart. This means that both a release tag and a minor release branch can be pushed beforegitfails due to the inability to push to one of the remote branches.To avoid the need for a great deal of manual cleanup it seems like a good idea for
neptune-releaseto firstfetchfrom the remote and validate that the current branch is up to date.