Make delivery asset outcomes disjoint
This commit is contained in:
15
docs/cli.md
15
docs/cli.md
@@ -105,7 +105,14 @@ build, or manifest. `deliver` never runs candidate checks or publishes a tag.
|
||||
The command returns 0 for complete delivery, 1 for a known failure, conflict,
|
||||
or partial delivery, 2 for usage, profile, or missing-credential errors, and 3
|
||||
when a remote write remains uncertain. The result lists matching, uploaded,
|
||||
pending, conflicting, and uncertain assets as available. Retry the same version
|
||||
with the same tagged source and destination; matching content is kept and only
|
||||
missing assets are added. See the [delivery consumer guide](consumers/delivery.md)
|
||||
and [Gitea integration guide](integrations/gitea.md).
|
||||
pending, conflicting, and uncertain assets as disjoint current observations;
|
||||
early failures may leave some declared assets unreported. On failure, the CLI
|
||||
prints state-based recovery guidance. Fix local or preflight failures before
|
||||
retrying; fix the reported cause before retrying partial delivery; resolve an
|
||||
unknown remote state before retrying; and investigate conflicts, using a new
|
||||
version if the source or published contents need correction. If rebuilding
|
||||
could change asset bytes already on the server, retain the original build
|
||||
artifacts and retry with `--assets DIR`. Matching content is kept and only
|
||||
known missing assets are added. See the
|
||||
[delivery consumer guide](consumers/delivery.md) and
|
||||
[Gitea integration guide](integrations/gitea.md).
|
||||
|
||||
Reference in New Issue
Block a user