-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Auto changelog - force group all docs tasks under Documentation
#34042
Conversation
Size Change: 0 B Total Size: 1.03 MB ℹ️ View Unchanged
|
I'm tempted to add unit tests so we don't have to test changes manually for every simple modification that CI can verify. From what I see, we can extract everything after |
Yeh that's probably a good idea. But if you want to replace human review then we're going to have to assert on the final changelog output. It might be tricky to make assertions on the generated markdown. Also we'd need a large piece of fixture data. Alternatively you can assert on all the low level functions which might encourage us to break down the large functions into easily testable components. We could also weight the effort against how often we change these functions. |
Forgot to say you don't have to have a GH token to run the test. So verifying this PR becomes
|
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.
Works like a charm.
Bonus: We could also remove the Docs:
shorthand that is used sometimes, example:
- Docs: Add more details about block attributes. (33880)
I have a prototype for the unit test ready at #34049 😄 |
8015a68
to
9483157
Compare
Description
In #33719 we decided we should force all docs tasks to appear under the main "Documentation" section.
That's what this PR does. It does is very manually but that's ok as it's an exception.
How has this been tested?
Run
npm run changelog -- --milestone="Gutenberg 11.3"
Documentation
section.Screenshots
Types of changes
Bug fix (non-breaking change which fixes an issue)
Checklist:
*.native.js
files for terms that need renaming or removal).