m/arch-fullupgrade
1
0
Fork 0
Code Issues Releases Activity

docs: clarify makerelease dry-run branch requirement

Browse Source
This commit is contained in:
MatMoul
2026-04-27 20:12:47 +02:00
parent b489272bc0
commit 37aa36d94f
2 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+3 -2
View File
@@ -44,7 +44,7 @@ sudo ./fullupgrade
`makerelease.sh` automates a Git release workflow:
1. checks that the current branch is `dev`
1. checks that the current branch is `dev` for real releases
2. verifies the working tree is clean
3. optionally computes a new version from an increment shortcut
4. switches to `main`
@@ -80,6 +80,7 @@ sudo ./fullupgrade
- Make sure the `dev` branch contains the changes you want to release.
- `VERSION` is used directly as the tag name.
- If `VERSION` starts with `+`, it is treated as an increment based on the latest existing tag.
- `--dry-run` can be used from any branch and only prints the computed tag.
- The script may fail if Git state is unexpected or if a tag already exists.
- The tag message is automatically generated as `Release <version>`.
@@ -87,7 +88,7 @@ sudo ./fullupgrade
This repository is intentionally minimal.
- `fullupgrade` is hardened with `set -euo pipefail`.
- `makerelease.sh` now includes clean-tree checks, duplicate tag protection, increment shortcuts, dry-run support, and a trap to return to the original branch on exit.
- `makerelease.sh` now includes clean-tree checks, duplicate tag protection, increment shortcuts, dry-run support from any branch, and a trap to return to the original branch on exit.
## License