Skip to content

Improve readability of lowest unmerged pull request condition in stacked PRs CI doc - #45420

Open
ittakato wants to merge 1 commit into
github:mainfrom
ittakato:stacked-prs-lowest-unmerged-wording
Open

Improve readability of lowest unmerged pull request condition in stacked PRs CI doc#45420
ittakato wants to merge 1 commit into
github:mainfrom
ittakato:stacked-prs-lowest-unmerged-wording

Conversation

@ittakato

@ittakato ittakato commented Aug 5, 2026

Copy link
Copy Markdown

Why:

The "Lowest unmerged pull request" bullet in Optimizing CI for stacked pull requests was hard to read: it fronted the reason ("Because it targets the stack base directly, ...") before stating the identifying condition, unlike the sibling "Top pull request" bullet.

Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Restructures the bullet to follow the same sentence pattern as the "Top pull request" bullet in the same list:

Lowest unmerged pull request — the pull request currently at the bottom of the remaining stack, targeting the stack base directly. It is the pull request where github.event.pull_request.stack.base.ref equals github.event.pull_request.base.ref.

Check off the following:

  • A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
  • The changes in this PR meet the docs fundamentals that are required for all content.
  • All CI checks are passing and the changes look good in the review environment.

🤖 Generated with Claude Code

Restructure the "Lowest unmerged pull request" bullet to match the
sentence pattern of the "Top pull request" bullet in the same list.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@github-actions github-actions Bot added the triage Do not begin working on this issue until triaged by the team label Aug 5, 2026
@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source Review Production What Changed
pull-requests/how-tos/merge-and-close-pull-requests/optimizing-ci-for-stacked-pull-requests.md fpt
ghec
fpt
ghec

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

triage Do not begin working on this issue until triaged by the team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant