product-example 2 linked patterns checked
GitHub Issues and Pull Requests Saved Views
Documents saved views for monitoring issues and pull requests across repositories, including titles, descriptions, custom icons, advanced-filter queries, edit, duplicate, delete, and saved-view limits.
Read with a purpose
What this source can teach
Use this source to inspect a concrete implementation and the decisions visible in its context.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Saved search | Choose saved search when users need to store and rerun a named query or criteria set across sessions. | Saving stores query criteria, filters, sort, and scope as a reusable definition, not just the current result IDs. | GitHub documents saved views with titles, descriptions, custom icons, query criteria, and edit, duplicate, delete lifecycle. |
| Saved view | Choose saved view when users need to persist a named combination of layout, columns, grouping, filters, sort, density, and other display preferences for a data surface. | Saving stores a canonical view definition, not a static list of current row IDs. | GitHub documents saved views with title, description, custom icon, query criteria, edit, duplicate, delete, and limits. |
Comparisons supported by this source
- Saved search vs basic search vs filter panel vs recently viewed
GitHub documents saved views with query criteria, title, description, custom icon, and edit, duplicate, delete lifecycle.
- Saved view vs saved search vs saved filter vs table
GitHub documents saved views with query criteria, title, description, custom icon, edit, duplicate, delete, and saved-view limits.
Evidence Role
This source is treated as product-example evidence. Its value comes from the specific claims and setting described above.
Publisher: GitHub Docs. Last checked: .