geogi / rslease Goto Github PK

During rslease own dev, I mistakenly forgot to pull before running it, but I had modified the README directly from GitHub. I had used no-push so no harm was done but it would be better if rslease tried to pull before any other action.

Because it won't work in some instances, e.g. on a detached HEAD when starting from a tag (which might not be the best idea but still), maybe add a switch like no-pre-pull.

Currently, rslease must be installed with cargo install, which is perfectly fine since it’s a
Rust-centric development tool. Still, it is a standalone executable that could be automatically
built using GitHub Actions and distributed as an asset in each GitHub Release. This would be a
fine training for using Actions.

Right now pushing a patch reverts the -dev prefix, which is bad (see wiki). This was made because of possible interactions with --for (i.e. pushing a v1.0.1 when v1.1 exists should not create a v1.1-dev) but even beyond that some thinking may be necessary.

Should patch releases go to a different branch ? We probably don't want to see the manifest in master do this :

• v1.1 is released: v1.2.0-dev
• v1.1.1 is released: rollback manifest with v1.1.1, then v1.2.0-dev
• etc.