Repository navigation
fix(release-notes): record its own checks as the required status - #8
Merged
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
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.
The first real run (v0.4.1) opened PR #7 and the dispatched docs check passed, but a
workflow_dispatchrun does not count toward a PR's required checks, so the merge was refused. The job already runsmint validateandmint broken-linkson the exact tree it pushes. It now records that result as the required Build and check commit status on the PR head, waits for the PR to become mergeable, merges it and deploys. Addsstatuses: write.https://claude.ai/code/session_01YGAGXFNiYwvqiuiRKg25y2