Clarify release command exit statuses
This commit is contained in:
@@ -81,11 +81,11 @@ go list -m gitea.maximumdirect.net/eric/ReleaseKit
|
||||
"$releasekit_bin" version
|
||||
```
|
||||
|
||||
The module-selected executable is ReleaseKit v0.2.0. Do not use `go run` or
|
||||
`go tool` for publication: the native executable preserves its exit status and
|
||||
the publication-state diagnostics. ReleaseKit's child Go commands use the
|
||||
`go` found on `PATH` with `GOTOOLCHAIN=local`; keep the selected executable
|
||||
first on `PATH` through the publication command.
|
||||
The module-selected executable is ReleaseKit v0.2.0. Use the built executable
|
||||
for publication to preserve its exit status and publication-state diagnostics.
|
||||
`go run` maps a nonzero child exit status to 1. ReleaseKit's child Go commands
|
||||
use the `go` found on `PATH` with `GOTOOLCHAIN=local`; keep the selected
|
||||
executable first on `PATH` through the publication command.
|
||||
|
||||
Verify access to the authoritative remote without displaying credentials:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user