English | Deutsch
GitHub issues for your current project, directly in Visual Studio Code's secondary sidebar (right by default).
- Detects the current GitHub repository from Git remotes.
- Shows issue numbers, titles, labels and a description preview.
- Opens issues on GitHub with one click.
- Filters open, closed or all issues.
- Lists open pull requests below the issues in a collapsible "Pull requests" group.
- Follows the active file's repository or pins a selected repository.
- Supports public and private GitHub.com repositories through VS Code's built-in sign-in.
- English and German UI, following VS Code's display language.
- No runtime dependencies, separate GitHub CLI, telemetry, or background polling.
Requires VS Code 1.106+ on Windows, macOS or Linux.
- Download
issueview-0.3.1.vsixfrom the latest release. - In VS Code, open Extensions → … → Install from VSIX… and select it.
- Open a trusted project folder with a GitHub remote.
- In IssueView, select Sign in to GitHub.
If the sidebar is hidden, enable View → Appearance → Secondary Side Bar, or use View: Open View… → IssueView. Placement follows your VS Code layout.
code --install-extension issueview-0.3.1.vsixThe prototype used the extension name project-issues-sidebar. Uninstall it before installing IssueView to avoid duplicate views.
Use Configure Display Language in the command palette to change VS Code's display language. IssueView uses German for the German locale and English as its default fallback. Commands, filters, empty states and errors are localized. Issue titles and bodies stay in their original language.
The toolbar provides Refresh, Filter by status, and Select repository. Automatic mode uses the active editor's repository, falling back to the first detected Git repository. Remote selection prefers the current branch's upstream, then origin, then another recognized GitHub remote.
Load more issues fetches the next API page. Pages may contain fewer than 100 issues because pull requests are excluded. Use Refresh for updates; there is no periodic polling.
IssueView uses VS Code's built-in GitHub authentication provider. Tokens are never written to settings or logs. API requests go only to https://api.github.com; issue links open only on https://github.com.
Sign-in requests only the read:user scope, which is enough for public repositories. Private repositories additionally need GitHub's repo scope; IssueView asks for it only when a repository is not found, or via IssueView: Grant access to private repositories. That scope grants broader permissions, but IssueView only makes read requests. Organization SSO may require additional authorization. Manage sign-in and extension access through VS Code's account menu.
GitLab, Azure DevOps, self-hosted GitHub Enterprise, virtual browser-only workspaces and custom SSH host aliases are not supported.
Requires Node.js 22+ for tests and Python 3 for packaging. No npm install is needed.
npm test
npm run packagePackaging writes dist/issueview-0.3.1.vsix. The VSIX includes source code, translations, documentation, tests and packaging script. Attach the tested build to a GitHub release; publishing the release uploads that VSIX to the VS Code Marketplace. See PUBLISHING.md (German).
Tests cover repository detection, safe API targets, authentication headers, pagination, errors, cancellation, project switches during requests, both UI languages and translation completeness. The actual GitHub OAuth flow requires a manual check with an authorized account.
MIT · Michael Lantzen