| Issue 575: | Gerrit GUI allows user to create branches pointing to tag objects | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Affected Version: 2.1.2.4 What steps will reproduce the problem? 1. Go to the Gerrit branch admin page on the project web GUI 2. Create a branch with reference "v2.6.32" What is the expected output? What do you see instead? Should error or create a branch with reference 22763c5cf3690a681551162c15d34d935308c8d7 (the commit object for 2.6.32). Instead it creates one with 459b3d520991ec1b8e5ba68fbc4b206d602fee6e (the v2.6.32 SHA). This results in all sorts of failures (replication errors in the Gerrit error log, can't submit reviewed changes on top of this branch, etc). Please provide any additional information below. The issue is similar (from a user perspective) to 411 tho it's entirely possible they use separate code paths.
Mar 27, 2012
(No comment was entered for this change.)
Status:
Released
Apr 23, 2015
On 2.8.4 you can still push a tag to a branch if the tag points to a commit that is in the history of the remote branch. To reproduce: # All commands below succeed git push origin HEAD:refs/heads/delme git tag -m'hi' delme HEAD # The below command should fail/block the tag git push origin delme:refs/heads/delme You can verify that origin/delme is a tag object: git show origin/delme tag delme Tagger: Andrew Wheeler <awheeler@motorola.com> Date: Thu Apr 23 15:26:46 2015 -0500 hi |
|
| ► Sign in to add a comment |
Labels: FixedIn-2.1.3