Skip to content

Commit ce4d75e

Browse files
authored
Adjust gerrit change id description in the readme (#237)
- github rendered the tildes in the changeId with strikethrough - made the description more compact
1 parent 3af8af7 commit ce4d75e

File tree

1 file changed

+3
-8
lines changed

1 file changed

+3
-8
lines changed

README.md

+3-8
Original file line numberDiff line numberDiff line change
@@ -81,19 +81,14 @@ sputnik --conf /path/to/conf.properties --changeId I0a2afb7ae4a94ab1ab473ba00e2e
8181

8282
Other parameters are available. See them with `sputnik --help`.
8383

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:
8686

8787
```
8888
Request not successful. Message: Not Found. Status-Code: 404. Content: Not found: yours_change_id
8989
```
9090

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:
9792

9893
```
9994
sputnik --conf /path/to/conf.properties --changeId myProject~master~I0a2afb7ae4a94ab1ab473ba00e2ec7de381799a0 --revisionId 3f37692af2290e8e3fd16d2f43701c24346197f0

0 commit comments

Comments
 (0)