-
-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Actions: attempt to validate PR description tests #2810
Conversation
We're now validating in #2810 that it is removed, so we should tell the person to remove it
A few follow up changes were required for this to work:
... Otherwise, if you pushed a change but did not edit the description or attributes of the pull request, the status would be missing on the most recent commit. Because it's a required status, it needs to be present on the latest commit before you can queue to merge. The synchronize event runs after new commits are pushed to the pull request branch.
.. Otherwise the job wouldn't be retriggered after the change is added to the merge queue |
Tested with #2809 that it won't be queued to automatically merge until the check passes |
GitHub includes the description comment when it formulates the commit message, which we don't want as it's pretty messy. We will ask users to remove the comment but we need to validate it before allowing merging.
Stolen from https://github.com/orgs/community/discussions/84771#discussioncomment-8039595.