docs: name pull request 4 as the subject to land - #13
Closed
juliantellez wants to merge 1 commit into
Closed
juliantellez wants to merge 1 commit into
juliantellez wants to merge 1 commit into
Conversation
juliantellez
deleted the
docs-subject-pull-request-4-fails-plan-and-apply
branch
September 1, 2026 09:41
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What. Records pull request 4 as the one to land, with its head branch, its head commit, its merge state and the one check that is not passing.
Why. The next step runs in a new session and reads nothing from this one. It needs the pick written down. Pull request 4 is the oldest of the nine open ones, it does not conflict, and
plan and applyfailed on its head commit. That check does not appear ingh pr checks 4, because thedeployworkflow does not start on a pull request, so the file says how to read it from the commit instead.The file lands at
docs/subject-pull-request-4.md, which no other open pull request touches.