Skip to content
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

Merged
merged 6 commits into from
Feb 1, 2025
Merged

Conversation

phillco
Copy link
Member

@phillco phillco commented Feb 1, 2025

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.

@phillco phillco requested a review from a team as a code owner February 1, 2025 18:46
@phillco phillco added this pull request to the merge queue Feb 1, 2025
phillco added a commit that referenced this pull request Feb 1, 2025
We're now validating in #2810 that it is removed, so we should tell the person to remove it
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Feb 1, 2025
@phillco phillco added this pull request to the merge queue Feb 1, 2025
@phillco phillco removed this pull request from the merge queue due to a manual request Feb 1, 2025
@phillco phillco enabled auto-merge February 1, 2025 21:22
@phillco phillco added this pull request to the merge queue Feb 1, 2025
Merged via the queue into main with commit 2d9f784 Feb 1, 2025
16 checks passed
@phillco phillco deleted the pr-description branch February 1, 2025 22:31
@phillco
Copy link
Member Author

phillco commented Feb 1, 2025

A few follow up changes were required for this to work:

  pull_request:
    types: [synchronize]

... 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.

  merge_group:
    branches: [main]

.. Otherwise the job wouldn't be retriggered after the change is added to the merge queue

@phillco
Copy link
Member Author

phillco commented Feb 2, 2025

Tested with #2809 that it won't be queued to automatically merge until the check passes

github-merge-queue bot pushed a commit that referenced this pull request Feb 4, 2025
…#2811)

We're now validating in
#2810 that it is
removed, so we should tell the person to remove it


## Release notes

Co-authored-by: Andreas Arvidsson <andreas.arvidsson87@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants