uploads.sh
Star on GitHub
GitHub App

Docs

Guides

GitHub App

Optional, but nicer: bot-posted comments and live PR/issue titles.

What it adds #

Everything in these docs works without the App. Installing the uploads-sh GitHub App on your repos upgrades three things:

  • Comments post as uploads-sh[bot]. The managed "📎 Attachments" comment is created and updated by the App on the server, instead of under your own GitHub identity via the local gh CLI. That keeps attachment noise off your account — and it works in environments with no gh auth at all.
  • File pages show titles for private repos. A file attached to a PR or issue gets a share page that names its PR or issue. For public repos that works out of the box; for private repos the App is what grants read access to the title.
  • Titles stay current. The App's webhooks tell uploads.sh when a PR or issue is renamed, closed, or merged, so file pages don't show stale titles.

Install it #

Install from github.com/apps/uploads-sh. Pick the organization or account, then choose the repositories you attach files to — "only select repositories" is fine, and you can add more later from GitHub's settings.

That's the whole setup. The next uploads attach against an installed repo prints (uploads-sh[bot]) instead of (via gh):

uploads attach ./after.png
>> uploading ./after.png
>> attachments comment updated (uploads-sh[bot])

Permissions #

The App asks for the minimum it needs:

  • Issues and Pull requests: read & write — read titles and state, and post the one managed attachments comment. It never touches other comments, PR descriptions, or your code.

If your org installed the App before a permission was added, GitHub holds the upgrade until an org admin approves it. The CLI tells you when that's the case — it prints the exact approval link and falls back to posting via gh in the meantime.

Without the App #

No install, no problem: uploads attach posts the same managed comment through your local gh CLI, and file pages still resolve titles for public repos. Uninstalling later just returns you to that behavior — hosted files and their URLs are unaffected either way.