Developer Tools
GitHub Projects Adds General-Availability Boolean Search
GitHub made advanced search in Projects generally available on July 16. Project views can combine filters with AND and OR, filter pull requests by review state and rely on a Reviewers field; deployment statuses older than 90 days are now automatically deleted without changing a deployment's current state.
What happened and why it matters
The useful change is operational: teams can express compound review and delivery queues without maintaining a separate Project view for each question.
Primary source
Primary reference: GitHub: Advanced Search for Projects Is Generally Available. Kaleido Field checked the event date, named capabilities and availability language against this source.
| Source date | July 16, 2026 |
|---|---|
| Checked by Kaleido Field | July 17, 2026, 09:10 CST |
| What this source supports | developer-workflow product update for GitHub Projects advanced search AND OR reviews filter 90 day deployment status retention |
| What it does not prove | It does not prove a universal product ranking, full regional availability, or performance on every visual intelligence task. |
What reached general availability
The Projects filter bar now accepts logical AND and OR expressions. GitHub says teams can build more precise views without preserving a separate view for every combination of conditions.
Pull request items can also be filtered with the reviews: qualifier, backed by a Reviewers field that tracks requested reviewers and their latest submitted reviews.
The retention change
GitHub also introduced a 90-day retention policy for deployment statuses. Status records older than 90 days are automatically deleted from REST and GraphQL API results.
GitHub says a deployment's current state is unaffected, but integrations that read historical status records may need their own archive if they depend on longer windows.
Why agent teams should care
Coding agents increasingly update issues, pull requests and deployment workflows. Better filters can narrow the items an agent or operator should inspect, while the retention rule changes what historical evidence remains available through the platform API.
The release documents feature availability, not productivity gains. Teams should test saved expressions and audit any automation that assumes indefinite deployment-status history.
Evidence boundary
This page reports a dated event from a named primary source. Company specifications and adoption statements remain attributed claims unless independent evidence is cited above.
FAQ
What is the practical answer?
GitHub made advanced search in Projects generally available on July 16. Project views can combine filters with AND and OR, filter pull requests by review state and rely on a Reviewers field; deployment statuses older than 90 days are now automatically deleted without changing a deployment's current state.
What source does this article use?
The primary source is GitHub: Advanced Search for Projects Is Generally Available. Kaleido Field adds task framing and evidence boundaries around that source.
Where should the user verify the answer?
Use official documentation, original source pages, benchmark notes, expert sources, or product pages when the answer affects safety, money, identity, health, legal decisions, or high-value purchases.