Repository navigation
docs: the subject to land is pull request 4 - #6
Closed
juliantellez wants to merge 1 commit into
Closed
juliantellez wants to merge 1 commit into
juliantellez wants to merge 1 commit into
Conversation
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
1 participant
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 next, with its head commit, its merge state, and the name of the check that is not passing.
Why. The next step runs in a new session and reads nothing from this one, so the choice has to sit in a file rather than in a conversation.
Pull request 4 is the older of the two that are open and it qualifies on a failing check. It does not conflict. The failing check is
plan and apply, which does not appear ingh pr checks 4because it came from a manual dispatch. It is visible only on the head commit. That failure is older than the branch: the deploy job never passed in this repository, including on main.Note that pull request 5 adds a file of the same name, so these two conflict with each other while neither conflicts with main.