Data and AI releases

548 this month · 176 companies

Restrict issue creation to collaborators only

UpdateVerified

Repository admins can now restrict issue creation to collaborators with write access. This gives you more control over who can open issues and helps reduce unwanted issue creation, while keeping issue workflows available to the people who actively maintain and contribute to the project.

SecurityObservabilityCoding agents

Read on github.blog

Also shipped Jun 29, 2026GitHub in June 2026 →

More from GitHub platformEvery GitHub platform release →

Releases: Sidebar navigation and per-asset download counts

You can now scan and navigate release pages more easily with a dedicated sidebar table of contents. We also updated release metadata placement for a more consistent layout so it’s easier to move between entries on long pages. Users with write access can also now see download counts per release asset directly in the Releases UI.

Update
Source ↗

Issue fields are now generally available

Issue fields are now generally available for all GitHub organizations on Free, Team, Enterprise, and GitHub Enterprise Cloud with data residency plans and will ship in GitHub Enterprise Server 3.23.

GA
Source ↗

Cost center limit increased to 1,000 per enterprise

You can now create up to 1,000 cost centers per enterprise, up from 500. Enterprises that model hundreds or thousands of business units, departments, or product groups can now represent that full structure in GitHub, instead of exporting usage data into a homegrown system to fill the gap.

Update
Source ↗

Cost centers now support enterprise teams

Cost attribution across your enterprise can now follow your team structure. You can add enterprise teams as resources in a cost center, and all usage incurred by team members is attributed to that cost center.

Update
Source ↗

Restrict who can dismiss reviews in rulesets

You can now restrict who can dismiss pull request reviews directly in GitHub repository rulesets. This capability is generally available and gives you precise control over who can clear an approval before changes merge. The setting lives alongside the other review options in the Require a pull request before merging rule.

GA
Source ↗

New pull requests dashboard is now generally available

The refreshed pull requests dashboard is now generally available at github.com/pulls . It gives you a single home to track, prioritize, and act on the pull requests that need your attention, whether you’re an individual contributor or a manager working across many teams and projects. This experience was previously in public preview.

GA
Source ↗

Per-user states for multi-user budgets in the REST API

You can now retrieve every user’s progress against a multi-user budget from a single REST API endpoint. This makes it much faster to find who is close to their limit across a large enterprise. Previously, you had to make one API call per user to check per-user consumption, and you couldn’t filter by how much of the budget someone had used.

Update
Source ↗