Repository navigation
docs: record pull request 4 as the subject to land - #9
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
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 the pull request to land next, in
docs/subject.md. It is pull request 4,#4. No code changes.
Why. The next step runs in a new session and reads nothing from this one. The file names the
number, the title, the head branch, the head commit, the conflict state and every check that is not
passing.
Pull request 4 is the oldest of the five open pull requests and the only one carrying a failing
check. That check is
plan and apply.gh pr checks 4does not show it, because thedeployworkflow does not start on a pull request, so read the check runs on the commit instead.
No check is required in this repository.
mainis not protected and the ruleset list is empty. Thefile states that judgement rather than hiding it.
Pull requests 5, 6 and 7 each add a file called
subject.mdat the root. The first to merge makesthe other two conflict on add over add. This pull request writes to
docs/subject.mdso it does notjoin that pile.
Gates run locally on this branch: typecheck, lint, 75 of 75 tests, build, the package start, and
terraform fmtplusvalidate. All pass.