-
Notifications
You must be signed in to change notification settings - Fork 4k
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
chore(prlinter): added commit message validation #6573
Conversation
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Blocking the merge of this PR until we verify the duplicate checks don't mess with mergify. |
@eladb The action causes mergify to break because mergify doesn't look for the last check, but instead looks for any check. I would still like to merge this PR just for the sake of the PR template, leave the validation code in there but simply not invoke the action until we sort through the mergify problems. thoughts? |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
This PR (hopefully) standardizes the commit messages that end up on master when mergify squash merges our PR's.
What we have know
Currently, the commit message that mergify uses is simply the default squash message provided by GitHub. That has the following heuristic:
This is problematic:
What will change
Instead of relying on GitHub, we can force mergify to use a section in the PR description called
Commit Message
.See https://doc.mergify.io/actions.html#commit-message-and-squash-method.
This means that all we need to do is validate that the section contains the content we want it to contain, which is what the github action in this PR does.
Here is an example of what the PR should look like: #6553
Caveat
Apparently, GitHub doesn't group check runs for the same commit hash. That means that every time a non commit event triggers an action, it will add a duplicate. This means we will have as many duplicates as the amount of changes done to the PR title/description.
You can see this PR as an example.
And the GitHub issue: https://github.saobby.my.eu.orgmunity/t5/GitHub-Actions/duplicate-checks-on-pull-request-event/td-p/33157
Commit Message
chore(prlinter): added commit message validation (#6573)
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license