MCPcopy Create free account
hub / github.com/atomicdotdev/atomic / not_found_push_message

Function not_found_push_message

atomic-cli/src/commands/push/helpers.rs:376–383  ·  view source on GitHub ↗

Build the user-facing message for a "not found" (HTTP 404) response during a push. The server deliberately masks private projects: it returns 404 to callers who are not authenticated/authorized rather than revealing that the project exists. Because a push is a write that always requires auth, a 404 almost always means the caller's credentials are missing/expired or they lack push access — not tha

(target: &str)

Source from the content-addressed store, hash-verified

374/// `target` describes what was not found, e.g. `"project/view 'dev'"` or
375/// `"the project"`.
376fn not_found_push_message(target: &str) -> String {
377 format!(
378 "Remote returned 'not found' for {target}. This means either it \
379 doesn't exist, or you're not authenticated/authorized to push to it. \
380 Make sure your identity is registered with the server \
381 (`atomic identity register <server-url>`) and that you have push access."
382 )
383}
384
385/// Convert a remote error to a CLI error.
386///

Callers 1

convert_remote_errorFunction · 0.85

Calls

no outgoing calls

Tested by

no test coverage detected