tools: build the Forgejo release body inside the forgejo command #1
Loading…
Reference in a new issue
No description provided.
Delete branch "release-notes-stdout"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The release gate piped
nix develop -c python3 tools/release.py notesinto the file it then published, so anything else on the dev shell's stdout became part of the release page. On a runner's fresh checkout the pre-commit installer printed its config path and an "Installed Git hook" line there, and both opened the v0.1.0 notes.release.py forgejo <tag>now builds the notes itself and posts them, so nothing captures the shell's stdout. It still prints the notes to the job log. A new test checks that the posted body is exactlynotes().3e6ad86e673289951574nix: keep the pre-commit installer off the dev shell's stdoutto tools: build the Forgejo release body inside the forgejo command