Revelo

Rich hover cards and detail panels for GitHub, Sentry, and Jira references in your code comments and Markdown. Hover a reference to see live details; Cmd/Ctrl+click to open a full detail panel inside the editor.

Works in VS Code and Cursor.

Features

• GitHub — issues, PRs, and discussions. Detects #123, GH-123, owner/repo#123, and full github.com URLs (including GitHub Enterprise). Shows title, state (open/closed/merged/draft with the correct color), author, labels, and a body snippet.
• Sentry — issues by URL or short ID (PROJECT-42). Shows title, level, status, event/user counts, and last-seen date. Region-aware (US/EU/self-hosted).
• Jira — issues by key (ABC-123) or Cloud/Server URL. Shows summary, status, type, priority, assignee, and description (Atlassian Document Format rendered inline).
• Create Jira tickets from TODOs — with revelo.jira.requireTicketForTodo on, TODO/FIXME comments without a linked ticket get a warning and a quick fix that opens a create form in the panel (summary, description with a source link, project, type, priority, assignee search, epic/parent search, labels, due date). Options (types, priorities, labels, epics) are fetched from Jira and prefetched at startup so the form opens instantly. On create it writes the new key back into the comment (// TODO(ABC-123): …) and opens the issue.
• Ticket templates — define reusable defaults in revelo.jira.ticketTemplates (project, type, priority, parent, labels, etc.). Each template adds its own "Create Jira {name} ticket from TODO" quick fix that opens the form pre-filled, and a template picker in the form lets you switch. Use revelo.jira.visibleIssueTypes / visiblePriorities / visibleLabels to trim long Jira lists down to the ones your team uses.

References are detected only inside comments (per-language) and Markdown/plaintext prose, so ordinary code isn't matched.

Setup

References resolve against live APIs, so each provider needs credentials.

GitHub

Uses your VS Code GitHub sign-in automatically — run Revelo: Sign in to GitHub (or Set GitHub Token to paste a PAT). Public repositories work unauthenticated at a lower rate limit.

Bare #123 resolves against the workspace's origin git remote, or set revelo.github.defaultRepo.

Sentry

1. Create a User Auth Token (User Settings → Auth Tokens) with event:read, project:read, org:read.
2. Run Revelo: Set Sentry Token and paste it.
3. Configure:

{
  "revelo.sentry.enabled": true,
  "revelo.sentry.orgSlug": "your-org",
  "revelo.sentry.apiBaseUrl": "https://your-org.sentry.io",
  // Only needed for bare short IDs — the uppercased project slugs:
  "revelo.sentry.shortIdPrefixes": ["BACKEND", "WEB"]
}

Jira

1. Create an API token at id.atlassian.com/manage/api-tokens.
2. Run Revelo: Set Jira Token and paste it.
3. Configure:

{
  "revelo.jira.enabled": true,
  "revelo.jira.siteUrl": "https://your-company.atlassian.net",
  "revelo.jira.email": "you@company.com",
  // Optional: restrict bare-key matching to your project keys
  "revelo.jira.projectKeys": ["ABC", "PROJ"],
  // Optional: templates that pre-fill the create form (name is required,
  // everything else optional). Each also adds a quick fix.
  "revelo.jira.ticketTemplates": [
    { "name": "Bug", "projectKey": "ABC", "issueType": "Bug", "priorityId": "2", "labels": ["triage"] }
  ]
}

Tip: priority and assignee use internal Jira ids. Enable revelo.jira.debug to show them beside each option in the create form, then copy the id into your template.

Commands

Settings

Editing

The detail panel (Cmd/Ctrl+click a reference) can edit issues, not just view them:

• GitHub — close/reopen, set assignee, edit labels. Controls appear only when your token has push access to that specific repo.
• Jira — change status (transition), set assignee, edit description. Each control appears only if you have the matching permission on that issue (TRANSITION_ISSUES, ASSIGN_ISSUES, EDIT_ISSUES).
• Sentry — change status (resolve/ignore/unresolve). Off by default; enable with revelo.sentry.enableEditing and a token with event:write.

Releasing

Two channels ship from this repo, following the VS Code Marketplace convention (a single extension can't use semver pre-release tags, so channels are split by minor-version parity):

• Pre-release — every merge to main auto-publishes a pre-release build (.github/workflows/pre-release.yml). These use odd minor versions (0.1.x, 0.3.x); the patch is the commit count, so builds are monotonic. Users opt in via Switch to Pre-Release Version in VS Code.
• Stable — cut by pushing a version tag (.github/workflows/publish.yml). These use even minor versions (0.2.x, 0.4.x). The tag must match package.json and the CI validates the even-minor rule.

To cut a stable release:

npm version minor   # bumps to the next even minor, creates the v* tag
git push --follow-tags

Both channels publish to the VS Code Marketplace and Open VSX (Cursor), gated behind type-check + lint + tests. PR titles are linted for Conventional Commits (feat:, fix:, …) so squash-merges keep history parseable.

Privacy

Tokens are stored in VS Code's encrypted SecretStorage, never in settings files. Reference details are fetched directly from your configured GitHub/Sentry/Jira instances and cached in memory only.

License

MIT