Skip to content

Commit 96b48e7

Browse files
szokeasaurusrexantonpirker
authored andcommitted
docs(cli): Clarify release commit range (#13850)
Specifiy that the "from" commit is supposed to be the last commit of the previous release. Fixes #10045
1 parent 90312ce commit 96b48e7

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/cli/releases.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -85,10 +85,10 @@ To see which repos are available for the organization, you can run `sentry-cli r
8585

8686
Note that you need to refer to releases you need to use the actual full commit SHA. If you want to refer to tags or references (like _HEAD_), the repository needs to be checked out and reachable from the path where you invoke _sentry-cli_.
8787

88-
If you also want to set a previous commit instead of letting the server use the previous release as the base point you can do that by setting a commit range:
88+
If you also want to set a previous commit instead of letting the server use the previous release as the base point you can do that by setting a commit range. Replace `<commit_of_previous_release>` and `<commit_of_current_release>` with the last commit of the previous release and the release you are creating, respectively.
8989

9090
```bash
91-
sentry-cli releases set-commits "$VERSION" --commit "repo-owner/repo-name@from..to"
91+
sentry-cli releases set-commits "$VERSION" --commit "repo-owner/repo-name@<commit_of_previous_release>..<commit_of_current_release>"
9292
```
9393

9494
### Alternatively: Without a Repository Integration

0 commit comments

Comments
 (0)