Repository navigation
Remove the PR readiness checklist workflow - #708
Merged
Merged
Conversation
The workflow failed PRs whose body didn't tick a fixed checklist, which added friction without catching real problems. It was not a required status check. Drop the matching mandatory section from the PR template; the local toolchain checklist still covers game testing and hardcoded paths.
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.
Summary
.github/workflows/pr-readiness-check.yml. It failed any non-draft PR whose body didn't tick a fixed set of checklist items, unless thechecklist-exceptionlabel was applied.The workflow was not a required status check (
mainhas no required checks or rulesets), so nothing else depends on it. Thechecklist-exceptionlabel can be deleted from the repo settings if you want; nothing references it anymore.The template edit sits a few lines away from the hooks-link change in #707, so whichever merges second may need a trivial rebase.