Skip to content

Commit b4ff9f3

Browse files
committed
Fixed code block in the README
1 parent 987b557 commit b4ff9f3

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

README.md

+3-4
Original file line numberDiff line numberDiff line change
@@ -195,7 +195,6 @@ The `distance_to_latest_tag` is a special value that is replaced with the number
195195
Now when you run `bump-my-version show-bump`, you can see the new pre-release versioning path.
196196

197197
```console title="Showing the new versioning path with pre_n automation"
198-
199198
$ bump-my-version show-bump
200199
0.1.0 ── bump ─┬─ major ─ 1.0.0-dev0
201200
├─ minor ─ 0.2.0-dev0
@@ -211,17 +210,17 @@ $ bump-my-version show-bump 1.0.0-rc0
211210
├─ minor ─ 1.1.0-dev0
212211
├─ patch ─ 1.0.1-dev0
213212
╰─ pre_l ─ 1.0.0
214-
```
213+
```
215214

216215
The `pre_n` path is now missing because it is automated.
217216

218217
The full development and release path now is:
219218

220219
- `1.0.0`
221220
- `bump patch``1.0.1-dev0`
222-
- each commit will increase → `1.0.1-dev1`
221+
- each commit will increase → `1.0.1-dev1`
223222
- `bump pre_l``1.0.1-rc0`
224-
- each commit will increase → `1.0.1-rc1`
223+
- each commit will increase → `1.0.1-rc1`
225224
- `bump pre_l``1.0.1`
226225

227226
1. You must decide on the next version before you start developing.

0 commit comments

Comments
 (0)