neo attachment
Download issue and pull-request image attachments.
An attachment’s bytes live on the content origin at /a/<id>, which never accepts your token. neo asks the API host to sign the id (allowed only if you can read the repository the attachment belongs to), then downloads the returned five-minute signed URL with no credentials at all. Your token never leaves the API host, so there is no need to read it out of the config file. To fetch every image an issue or pull request references, pass --attachments <DIR> to neo issue context, neo ticket context or neo pr context.
neo attachment [OPTIONS] <COMMAND>neo attachment get
Section titled “neo attachment get”Download one attachment’s original bytes.
Writes <id>.<ext> into the current directory, with the extension taken from the served media type (png, jpg, gif, webp, avif, else bin), and prints the path it wrote. Exits 1 and writes nothing when the attachment does not exist or you cannot read its repository; the two are indistinguishable by design.
neo attachment get [OPTIONS] <ATTACHMENT>| Option | Value | Required | Default | Env | Values | Description |
|---|---|---|---|---|---|---|
<ATTACHMENT> |
yes | Attachment id (32 hex characters, with or without UUID dashes), or a URL whose path starts /a/<id>, as pasted from an issue body |
||||
--output, -o |
<PATH> |
no | Where to write: a file path (overwritten if present), or an existing directory to write <id>.<ext> into. Defaults to the current directory |