2026-10-10T06:59:48Z

2026-10-10T06:59:48Z

blog/changelog/2026-10-08-triage-role-users-or-higher-can-now-archive-pull-requests">Triage role users or higher can now archive pull requests</a> appeared first on <a href="https://github.

Triage role users or higher can now archive pull requests <p>Users with the triage role or higher in a repository can now archive and unarchive pull requests. Previously, archiving was limited to repository administrators, requiring trusted triagers to hand routine…</p>

Archiving—often used for spam, duplicate, or abandoned pull requests—is a common moderation action, and restricting it to administrators created unnecessary friction for projects that delegate this work. Repository: Admins can turn approvals on or off, and choose which file paths Copilot is allowed to approve. View events in the timeline for when a pull request was added or removed from a stack. blog/changelog/2026-10-08-triage-role-users-or-higher-can-now-archive-pull-requests">Triage role users or higher can now archive pull requests</a> appeared first on <a href="https://github. Previously, archiving was limited to repository administrators, requiring trusted triagers to hand routine…</p> <p>The post <a href="https://github. The post Triage role users or higher can now archive pull requests appeared first on The GitHub Blog. Previously, archiving was limited to repository administrators, requiring trusted triagers to hand routine moderation work to someone with higher permissions. blog/changelog/2026-09-01-copilot-code-review-can-now-approve-pull-requests">Copilot code review can now approve pull requests</a> appeared first on <a href="https://github. <p>Users with the triage role or higher in a repository can now archive and unarchive pull requests. Users with the triage role or higher in a repository can now archive and unarchive pull requests. blog/changelog/2026-09-01-github-cli-media-in-issues-pull-requests-and-comments">GitHub CLI: Media in issues, pull requests, and comments</a> appeared first on <a href="https://github. blog/changelog/2026-10-08-draft-pull-requests-count-toward-pull-request-limits">Draft pull requests count toward pull request limits</a> appeared first on <a href="https://github. blog/changelog/2026-10-06-stacked-pull-requests-generally-available">Stacked pull requests generally available</a> appeared first on <a href="https://github. The post Copilot code review can now approve pull requests appeared first on The GitHub Blog. With these changes: Users with the triage, write, maintain, or admin role can archive and unarchive pull requests. The post GitHub CLI: Media in issues, pull requests, and comments appeared first on The GitHub Blog. Stacked pull requests are now in public preview - GitHub Changelog Skip to content Skip to sidebar / Blog Try GitHub Copilot app Attend GitHub Universe Back to changelog Release July 30, 2026 • 3 minute read Stacked pull requests are now in public preview Stacked pull requests break large changes into small, reviewable pull requests. The post Draft pull requests count toward pull request limits appeared first on The GitHub Blog. The post Stacked pull requests generally available appeared first on The GitHub Blog. This is now…</p> <p>The post <a href="https://github. Previously,…</p> <p>The post <a href="https://github. Archived pull requests are hidden from public view and remain visible to users with the triage, write, maintain, or admin role. The ability for Copilot to approve is off…</p> <p>The post <a href="https://github. Since the feature went into public…</p> <p>The post <a href="https://github. This keeps archived pull requests read-only without granting triage users the ability to manipulate a conversation’s locked state, which requires write access. 16 Release Repository admins can archive pull requests collaboration tools Jul. <p>GitHub stacked pull requests are now generally available. GitHub stacked pull requests are now generally available. Editor’s note (October 9th, 2026): Clarified who will still be able to see archived pull requests. <p>GitHub CLI now has a repeatable --attach flag that uploads a local image or video and references it inline in an issue, pull request, or comment body. GitHub CLI now has a repeatable --attach flag that uploads a local image or video and references it inline in an issue, pull request, or comment body. This is now generally available to all users on GitHub across all plans. And because stacked pull requests are built into GitHub, your existing reviews, checks, and merge requirements all work out of the box. 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. Over two-thirds of the top 1% of repos now use stacked pull requests and have seen a 5% improvement in time-to-merge. Stacked pull requests can be set to merge automatically once the repository’s merge requirements are met. ” David Mostoller, software engineer, Comcast Get started Stacked pull requests are available on all github. We’ve also improved how archived pull requests become read-only. ⚙️ Turning on approvals By default, Copilot will not approve pull requests. Previously, gh only wrote

Key findings

text, so adding an image or video to an issue or pull request meant stopping to open the browser, drag the file into the comment box, and copy the result back. --attach is generally available to all users on GitHub across all plans, with no preview period. Stacked pull requests break large changes into small, reviewable pull requests. js lead, Vercel” With stacked pull requests, teams can: Keep large changes moving by reviewing short, narrowly scoped pull requests in parallel. Then add branches and pull requests on top of it; each pull request targets the layer below it. ” – Mayank Saini, connectivity engineer, WHOOP Find out more and share your feedback Stacked pull requests are rolling out in public preview to all repositories over the coming days. Merge queue support for stacked pull requests is rolling out progressively over the coming weeks. 03 Improvement Triage role can bypass issue creation restrictions collaboration tools Jul. Break large changes into smaller, focused pull requests that you can review independently and merge together. Select a group of pull requests and they will all merge together once all the pull requests are ready to merge. View details about the stack that a pull request belongs to from the pull requests list view. Check out the stacked pull requests documentation to learn more about the feature and how to get started. Close all open contributions authored by a blocked user - GitHub Changelog Skip to content Skip to sidebar / Blog Try GitHub Copilot app Attend GitHub Universe Back to changelog Improvement August 27, 2026 • 1 minute read Close all open contributions authored by a blocked user You can now automatically close all open issues, discussions, and pull requests authored by a user when you block them from your personal account or organization. You can now automatically close all open issues, discussions, and pull requests authored by a user when you block them from your personal account or organization. You’ll see it whenever you block a user, including from an issue or pull request comment, or from Settings → Moderation → Blocked users. The ability for Copilot to approve is off by default and configurable at the enterprise, organization, and repository level. The approval assessments will now appear as a part of the overview comment in every Copilot review. This feature is available in public preview to GitHub Copilot Pro, Pro+, Max, Business, and Enterprise plans. ✅ Approval assessments Every Copilot code review now includes an approval assessment in the overview comment. To learn more about configuring approvals for your enterprise, organization, or repository, see the Copilot code review documentation. Editor’s note (September 1, 2026): Updated the doc link. Use the stack map at the top of the pull request to see how the change you’re reviewing fits into the larger work. 13 Improvement Block users from comments in personal repositories collaboration tools Aug. 06 Improvement Set pull request limits at the organization level collaboration tools Aug. 25 Improvement Block users directly from security advisories collaboration tools Aug. 21 Improvement Better tools for managing blocked users collaboration tools Aug. With stacks, you can independently review and check each pull request, then merge everything together in one click. ” – Andy Merryman, CTO, TED Merge everything in a single click Merge the latest ready pull request to land it and every unmerged layer below it in one single operation. Use Shift+J and Shift+K shortcuts to navigate between pull requests in a stack. Now, we’re preventing any new activity on the pull request once it’s been archived. New comments, reactions, and automated comments are blocked while a pull request is archived. Stack information is now always visible in the pull request page’s persistent header. The pull_request webhook now includes a stacked action when a pull request joins a stack. Users with permission to bypass repository rules can now use those permissions to merge the lowest unmerged pull request in a stack. Review each layer independently Open any

Operational implications

pull request in the stack to review only the diff for that specific layer. 23 Release Agent automation controls in GitHub Issues in public preview collaboration tools copilot projects & issues . 21 Release The new GitHub Copilot experience in Slack collaboration tools copilot . 21 Release Shared agentic work with GitHub Copilot in Microsoft Teams collaboration tools copilot . <p>Copilot now tells you when a pull request is ready to approve, and admins can authorize it to sign off on approval. Copilot now tells you when a pull request is ready to approve, and admins can authorize it to sign off on approval. The assessment signals whether Copilot considers the pull request ready to approve, giving you an at-a-glance read on its judgment alongside its detailed comments. That meant someone could open any number of drafts, even when you’d set a limit for other pull requests. GitHub Enterprise Server is not supported in this release. 11 Release GitHub Enterprise Server 3. com plans and will be included in an upcoming GitHub Enterprise Server release. Start with a branch and pull request for your first change. Open the pull request with a before and after, and the reviewer sees the change instead of pulling the branch to check. When a stack’s base branch is deleted, GitHub automatically retargets the stack instead of closing its bottom pull request. Previously, archiving would lock the pull request, but admins were still able to leave comments. Archiving automatically closes the pull request and makes its conversation read-only. com Work with stacks on github. They’re an ordered series of pull requests that each represent focused layers of your change. To land part of a stack, merge one or more lower layers—the pull requests above it stay open and automatically rebase and retarget. “We’ve been using GitHub stacked PRs for Next. “The new Github Stacked PRs preview is incredible. “It took one merge with GitHub’s Stacked PRs for me to conclude that it’s amazing. “Seeing every branch in the stack right in the GitHub PR UI, checking each one’s status, and navigating between them makes managing and reviewing many dependent PRs far easier. When using the merge commit method, GitHub now creates one merge commit per pull request instead of one for the entire merged group. No more opening a single large pull request that takes forever to review, or splitting work across multiple branches you have to keep manually rebasing. A stack now enters and lands through the merge queue as a single merge group. Maintainers increasingly rely on triagers to keep pull request queues healthy without granting them permission to change code. com, the GitHub CLI, the GitHub mobile app, or with a coding agent such as GitHub Copilot using the gh-stack skill. Unarchiving restores the ability to comment and react, but does not reopen the pull request. This removes so much friction (and the gh cli tools + agent skill help a ton)” – John Resig, creator, jQuery Get started with the CLI extension Install the CLI extension and create your first stack in under a minute: gh extension install github/gh-stack Create stacks from your terminal or github. Maintain quality across every layer by using focused pull request reviews alongside existing branch protections to protect main. Now it’s a stack of small ones reviewers can actually follow, and the whole stack merges in one shot. When enabled, Copilot can submit an approval that counts toward the repository’s required-approvals rule. Counting drafts toward the limit helps you curb that loophole and reduce the clutter, notifications, and CI runs that can come with repository spam. Write access to the repository you are attaching to is required for image uploading. It stopped feeling like a tool on top of GitHub and started feeling like GitHub. Join the discussion on the GitHub Community and read the docs to learn more about attaching files from the command line. Now, gh can attach images and videos directly from the command line.

21 Release Shared agentic work with GitHub Copilot in Microsoft Teams collaboration tools copilot .

Read the original sources cited in the article for the full material.

Frequently asked questions

**What does the collected research say about Triage role users or higher can now archive pull requests <p>Users with the triage role or higher in a repository can now archive and unarchive pull requests. Previously, archiving was limited to repository administrators, requiring trusted triagers to hand routine…</p>

What are the key details from GitHub Changelog?

Stacked pull requests break large changes into small, reviewable pull requests.