You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Other parameters are available. See them with `sputnik --help`.
83
83
84
-
There's a bug/feature in Gerrit when you push same change set identified by particular changeId into two branches, for example your working branch and review branch.
85
-
You can recognize it by the following error message
84
+
Depending on your workflow it can happen that the changeId matches changes on multiple branches, for example when you push a change set identified by particular changeId into your working branch and review branch.\
85
+
You can recognize it by the following error message:
86
86
87
87
```
88
88
Request not successful. Message: Not Found. Status-Code: 404. Content: Not found: yours_change_id
89
89
```
90
90
91
-
Then it's necessary to add repository and target branch name to distinguish which change set you're addressing. Target branch would be typically master but actually it's the one
92
-
you're using making
93
-
```
94
-
git push origin HEAD:refs/for/BRANCH_NAME
95
-
```
96
-
So add REPO_NAME~BRANCH_NAME~ to changeId Sputnik's param, for example:
91
+
In this case the extended changeId format (`REPO_NAME~BRANCH_NAME~CHANGE_ID`) should be used which includes the repository and the branch name, for example:
0 commit comments