Issues in other repos
Get started
GitHub
Add a screenshot to an issue in someone else's repo
For bug reports and contributions from outside the project.
How it works #
When you report a bug on a project you don’t maintain, the web editor is the usual way to add a screenshot. From a terminal or a coding agent, host the file first and paste a link. With the uploads CLI you can:
- Host a screenshot, recording, or log at a stable public URL.
- Get a Markdown line you can paste into any issue or comment.
- Replace the file later and keep the same URL.
Host the file #
uploads put ./bug.png --destination screenshotsThat uploads the file and prints its URL and a Markdown line. --destination screenshots keeps the
file out of your own repo’s pull requests when you run it inside a git checkout.
Uploaded files are public to anyone with the URL. Crop or redact tokens, emails, and personal data first.
Post it to the issue #
Paste the Markdown line into your issue or comment on GitHub. From the terminal, use gh:
gh issue comment 42 --repo owner/repo --body-file comment.mdwhere comment.md holds your text and the Markdown line.
Need to mark up the screenshot first? Use uploads annotate —
see Capture & annotate →.
FAQ #
- Can I add a screenshot to a GitHub issue if I can't push to the repo?
- Yes. Host the file with uploads put, then paste the Markdown it prints into your issue or comment. Anyone who can comment on the issue can do this.
- Do the maintainers need to use uploads?
- No. The screenshot is a normal Markdown image. GitHub shows it like any other image in the issue.
- Can a coding agent file the bug report for me?
- Yes. The agent runs uploads put for the screenshot, then includes the printed Markdown in the issue body it writes.