Issues
File bugs, ask questions, and track work directly from your browser. Issues you create are signed with your Radicle key and replicated to peers like any other Radicle data.
Browsing issues
Open the Issues tab on any repository. You'll see two state filters at the top:
- Open — issues that are still being worked on or triaged.
- Closed — issues that have been resolved or won't be addressed.
Each row shows the title, author, applied labels, comment count, and a relative timestamp. Hover the timestamp to see the exact UTC time. Click anywhere on a row to open the issue.
Opening an issue
- From the Issues tab, click New Issue. You must be signed in.
- Give the issue a clear, focused title.
- Use the description for context. The description supports Markdown — code fences, lists, and links all render in the issue view.
- Submit. Radish signs the issue with your key, writes it to local Radicle storage, and redirects you to the new issue page.
Once submitted, the issue ID (a Git object hash) becomes its permanent identifier. The first eight characters are shown in lists for reference.
Writing good issues
- Be specific in the title. "Crash on startup with empty config" is more useful than "Bug".
- Include reproduction steps. What did you do, what did you expect, what happened instead.
- Quote the version. Either a commit hash, a release tag, or both.
- Use code blocks for stack traces. Triple-backtick fences keep formatting and prevent Markdown from misinterpreting the contents.
Commenting
From inside an issue, scroll to the comment box at the bottom and type your reply. Comments support the same Markdown rendering as descriptions. Each comment is independently signed by its author and links back to their profile.
Comments are append-only at the protocol level — there's no edit or delete. If you need to correct yourself, post a follow-up.
Labels
Labels are short tags ("bug", "good-first-issue", "docs", anything you like) used for filtering and triage. To apply a label, use the label form in the right sidebar of an issue. Labels accumulate over time as different contributors tag the issue from their own perspective.
Labels are themselves signed Radicle operations, so the history of who applied which label is preserved.
Closing an issue
Closing is currently performed via the Radicle CLI by the author or a delegate. Once closed, the issue moves into the Closed tab in Radish but remains permanently viewable, including its full comment thread.