GitHub — Issue list

Tables & ListsSee it livegithub.com

A searchable issue list combines a readable query, compact filters, and inline labels without losing the hierarchy of each issue title.

GitHub — Issue list — captured interface — Page excerpt · scroll inside to explore

Source capture · 2026-09-04Open full image ↗

Search & discovery Navigation

Why this pattern works

Keep the query visible as editable text, with task-specific filters directly above the results. Pair status icons with labels and reserve the strongest weight for the issue title.

Design notes

Surface: Open issues in a public GitHub repository
Navigation: Global GitHub navigation, repository tabs, and a left sidebar for issue views.
Layout: A narrow left navigation rail and a wide results list, preceded by a query field and a filter toolbar.
Density: Compact metadata below each title; rows expand naturally for long titles and labels.
Color: Neutral white and gray structure with semantic issue icons and colored labels. Status remains legible from text and icons.
Type: Bold issue titles; smaller muted author, time, and issue-number metadata. Query syntax remains readable in the search field.
Pattern: Combine an editable structured query with familiar filters instead of forcing users into one search method.
States: Populated open-issues view. Counts and issue contents are a dated public snapshot, not current operational data.
Don't: Do not communicate state solely through label color. Preserve the current query and filter state when navigating back.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: GitHub — Issue list
Source: https://github.com/withastro/astro/issues
Swipefile reference: https://swipefile.design/ref/github-issues/
Captured: 2026-09-04. This is a dated reference, not a claim about the current live product.
Capture scope: a page excerpt. Do not infer unseen sections or interactions.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Open issues in a public GitHub repository
- nav: Global GitHub navigation, repository tabs, and a left sidebar for issue views.
- layout: A narrow left navigation rail and a wide results list, preceded by a query field and a filter toolbar.
- density: Compact metadata below each title; rows expand naturally for long titles and labels.
- color: Neutral white and gray structure with semantic issue icons and colored labels. Status remains legible from text and icons.
- typography: Bold issue titles; smaller muted author, time, and issue-number metadata. Query syntax remains readable in the search field.
- pattern: Combine an editable structured query with familiar filters instead of forcing users into one search method.
- states: Populated open-issues view. Counts and issue contents are a dated public snapshot, not current operational data.
- dont: Do not communicate state solely through label color. Preserve the current query and filter state when navigating back.

Useful for: Keep the query visible as editable text, with task-specific filters directly above the results. Pair status icons with labels and reserve the strongest weight for the issue title.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Keep the query visible as editable text, with task-specific filters directly above the results. Pair status icons with labels and reserve the strongest weight for the issue title.

GitHub — Issue list

Make it your own

Keep exploring