66 releases · 2 this month
GitHub introduced an opt-in overview page for pull requests that displays merge status and next actions in a compact summary at the top of the page. This feature aims to reduce scrolling and clarify the state of pull requests.
You can now use the GitHub REST API to find which cost center a user, organization, repository, or enterprise team belongs to. Previously, you had to list every cost center and scan its resources. Pass the resource type and name to the new endpoint. The response includes the cost center’s ID and name.
GitHub added new webhook delivery IP ranges to the Meta API hooks field for github.com and GitHub Enterprise Cloud.
GitHub Apps can now be installed at the enterprise level, providing expanded API support for governance, security, and administrative tasks.
GitHub pull requests now support saving personal whitespace visibility preferences and feature an improved split view that spans the full width for new and deleted files.
You can now convert all branch protection rules of a repository to rulesets in a single action. This is an extension of the ability to convert a single branch protection rule to a ruleset that we released previously, now allowing for at-scale conversions.
During periods of unusual traffic, GitHub may temporarily require authentication for some clones and fetches of public repositories over HTTPS to help protect github.com’s availability. If an operation is affected, it will fail with a message indicating that authentication is required. To continue, authenticate and retry the operation.
As of October 15, 2026, email notifications for repository push events have been retired and are no longer sent. We shut down this feature to help prevent spam and abuse. Because recipients didn’t have to consent before receiving these emails, the feature could be misused to send unwanted messages through GitHub’s email infrastructure.
The “Budgets and alerts” page in your GitHub billing settings now shows all of your budgets in one list that you can search and filter. Whether you manage budgets for a personal account, enterprise or organization, you can find a specific budget without paginating through the full list.
Maintainers are seeing more low-quality contributions in their repositories and need better ways to manage them. You can now configure pull request limits to also include draft pull requests. Previously, draft pull requests didn’t count toward a user’s limit.
GitHub stacked pull requests are now generally available. Break large changes into smaller, focused pull requests that you can review independently and merge together. Since the feature went into public preview , repositories using stacks have seen a 9% increase in merged code compared to peers.
You can now find an ACCESSIBILITY.md file in your repository’s root, the .github/ directory, or the docs/ directory highlighted on the repository overview. You can also add or propose an accessibility statement from a public repository’s Community Standards page.
Private saved views for repository issues Repository issues pages now support private saved views, making it easier to create and save personalized views of your issues. “Relates to” issue relationship The “Relates to” issue relationship now works across the REST API, GraphQL API, webhooks, timeline events, issues search, and projects search.
The new repository pull requests page is now generally available to all GitHub users. Highlights The new page makes it easier to find and act on pull requests in a repository, with new filtering and search options to help you find exactly what you’re looking for: Content assist helps you easily find and apply the correct filters.
Enterprise admins can now automate SSO authorization for existing classic personal access tokens (PATs) and SSH keys for organizations in GitHub Enterprise Cloud, replacing manual per-organization authorization by your developers.
Previously we announced we would be disabling SHA-1 in HTTPS for GitHub on September 15th, 2026. Following the planned schedule, GitHub has disabled SHA-1 in HTTPS for github.com and partner CDNs, including GitHub Enterprise Cloud and GitHub Enterprise Cloud with Data Residency. GitHub Enterprise Server is unaffected.
Your GitHub profile now displays the highest tier you’ve earned for achievements with multiple levels. Previously, profiles could display the first tier earned, even after you had progressed to a higher level. Now, your profile better reflects your latest achievement and the progress you’ve made on GitHub.
A refreshed repository-level pull request listing page is now in public preview for all GitHub users. It brings powerful filtering, compact presentation mode, and more.
GitHub Enterprise Server (GHES) 3.22 is now available and introduces new capabilities across the platform. Here are a few highlights in the 3.22 release: Administrators can configure Copilot CLI to work with GHES for enterprises that operate in disconnected or air-gapped environments without connectivity to GitHub Cloud.
Track repository star growth over time with the new star history REST API endpoint without exposing stargazer identities. Earlier this year, stargazer listing endpoints were restricted to admins and collaborators to protect user privacy. Now you can get the insights you need with a privacy-safe alternative.
The current PGP key for the GitHub CLI Linux package repositories expires on Saturday, September 5, 2026. Beginning with the first release after that date, APT and RPM repository metadata and newly published RPM packages will be signed with just the replacement key. In April, we published a keyring containing both the current and replacement keys.
Enterprise Live Migrations (ELM) is now generally available, enabling near-zero-downtime repository migrations from GitHub Enterprise Server (GHES) to GitHub Enterprise Cloud with Data Residency (GHEC DR), so you can move even your largest, most active repositories while the contributions keep flowing.
We’re making it easier to keep labels organized and find the right one, especially in repositories with long and growing label lists. Suggested Labels You can now find the right label faster with suggestions based on what a repository has been using recently.
Enterprise owners can now grant a GitHub App access to enterprise billing data. When you create or configure a GitHub App, you can select the enterprise billing permission and choose one of two levels: read or read and write.
You can now configure push rules more granularly by exempting specific file paths, so a rule applies everywhere in scope except the paths you choose. Path exceptions are in public preview. Push rules give you strong control over what enters a repository.
Managing blocked users is now faster and clearer for personal accounts and organizations. With this update, you can: Search by username, full name, or email. Sort and paginate long lists. Filter by block reason (e.g., Spam , Misconduct , or Harassment ). Add private notes to preserve moderation context. View and edit block settings.
Pinning saved views to the repository issues sidebar You can now pin saved views to the repository issues sidebar, making the views you use most just one click away, even when the sidebar is collapsed. Other Improvements You can now see profile avatars for reactions on issues.
We’ve released multiple updates to the OAuth app and GitHub App platforms to support more secure app development: OAuth apps can opt in to expiring access tokens and refresh tokens. OAuth apps can have multiple redirect URIs. Both GitHub Apps and OAuth apps can enable wildcard matching for redirect URIs if needed.
You can now block or unblock users directly from comments on pull requests and issues in repositories owned by personal GitHub accounts. To block or unblock a user: Open the More menu on their comment. Select Block user or Unblock user . Optionally add a private note explaining why you’re blocking the user. Confirm your selection.
The rule insights dashboard is now in public preview at the organization level. You get a visual, high-level view of how GitHub evaluates and enforces your GitHub repository rulesets, so you can spot trends and report on governance without stitching data together by hand.
GitHub Enterprise Server (GHES) 3.22 is now available and introduces new capabilities across the platform. Here are a few highlights in the 3.22 release: Administrators can configure Copilot CLI to work with GHES for enterprises that operate in disconnected or air-gapped environments without connectivity to GitHub Cloud.
Update (August 14, 2026): Pausing the custom thread subscriptions deprecation We’re pausing the planned deprecation of custom thread subscriptions. Your feedback highlighted how integral this feature is to many developers’ notification workflows.
GitHub is making it easier to connect related work and manage multiple field values across issues and projects. Connect related issues The new “Relates to” issue relationship is available in public preview. You can connect two issues without implying that one blocks, duplicates, contains, or closes the other.
You can now set pull request limits at the organization level. Pull request limits let you define how many open pull requests a user without write access can have at one time. If a user reaches that limit, they must close or merge an existing pull request before opening another.
Migrations from gitlab.com and GitLab Self-Managed to GitHub Enterprise Cloud with GitHub Enterprise Importer (GEI) are now generally available. You can now self-serve these migrations using GEI and the gh gl2gh command-line extension.
Stacked pull requests break large changes into small, reviewable pull requests. They’re an ordered series of pull requests that each represent focused layers of your change. With stacks, you can independently review and check each pull request, then merge everything together in one click.
You can now create multi-select fields in Projects and Issue fields so a single field can hold more than one value. Tag an item with everything it relates to (e.g., multiple teams, modules, or categories) instead of picking just one. Issue Fields Projects Fields To try it, create or edit a field and choose the multi-select type.
We want to give you advance notice of an upcoming security change that may affect GitHub Enterprise Server (GHES) support bundle uploads. Beginning August 18, 2026, GitHub will start rejecting command-line support bundle uploads from older GHES appliances that have not been updated with the required security patches.
The filter bar in GitHub Projects views now supports advanced search, so you can build the exact view you need with logical AND and OR instead of maintaining a separate view for every question. Just type an expression using OR , AND in the filter bar of any project view.
We’ve separated the combined SSO & Organizations page in your user settings into two distinct pages: SSO and Organizations . This update makes it easier to find and manage these settings independently, with a clearer experience in your account settings.
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.
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.
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.
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.
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.
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.
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.
Saved views for repository issues Repository Issues pages now support saved views, making it easier for teams to create and share filtered views of their issues. With saved views, anyone with triage access or above can create shared views like “Unassigned bugs”, “Needs triage”, or “Customer-reported issues”.
Repositories, pull requests, issues, projects and administration.
Other GitHub products: GitHub Actions, GitHub Advanced Security, GitHub CLI, GitHub Copilot
| Release-notes page | Site | Feed |
|---|---|---|
| Actions changelog github.blog | github.blog | RSS |
| Changelog github.blog | github.blog | RSS |
| Copilot changelog github.blog | github.blog | RSS |
| Copilot CLI releases github.com | github.com | RSS |
| Desktop release notes desktop.github.com | desktop.github.com | None |
| Enterprise Server release notes docs.github.com | docs.github.com | None |
| GitHub CLI releases github.com | github.com | RSS |
| Security changelog github.blog | github.blog | RSS |
Releasesby Glyph