-
Notifications
You must be signed in to change notification settings - Fork 4.6k
GitHub Actions: fix components changelog CI check #70034
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
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Mamaduka
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for investigating this, @t-hamano!
The changes here make sense and seem to match previous logic, but I would defer to @johnbillion and @desrosj for final approval.
| runs-on: ubuntu-latest | ||
| permissions: | ||
| contents: read | ||
| contents: read |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My editor did the same correction yesterday, which I had to revert manually. Only happened once, so not sure what the problem is.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe this is the result of wp-scripts format being run through lint-staged. Perhaps @wordpress/prettier-config is enforcing such rules?
johnbillion
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good spot, thanks @t-hamano.
Co-authored-by: t-hamano <wildworks@git.wordpress.org> Co-authored-by: Mamaduka <mamaduka@git.wordpress.org> Co-authored-by: johnbillion <johnbillion@git.wordpress.org>
What?
There is CI that checks whether PRs that make changes to
@wordpress/componentspackage have updated CHANGELOG file.We noticed that this CI isn't working even though we have added a correct changelog entry (Example: #69969 (comment)).
This PR fixes the problem.
Why?
As far as I know, this problem occurred as a result of #69126. We should check the diff against the base branch, but I think
github.event.pull_request.base.shawas unexpectedly replaced withgithub.event.pull_request.head.sha.https://github.com/WordPress/gutenberg/pull/69126/files#diff-7077ded14418b5bee6455b705ec9de4d9420d58c999f5b5e2fb66848f391a87cR46-R52
Testing Instructions
We currently have no way to test this, but it should work.