-
Notifications
You must be signed in to change notification settings - Fork 18
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(ci): display skipped commits in release issue #434
Conversation
✅ Deploy Preview for api-clients-automation canceled.
|
✗ The generated branch has been deleted.If the PR has been merged, you can check the generated code on the |
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.
That's good! So if we have commits in one of those two list, and we remove it from the issue to put it under a language, will it be included in the changelog?
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.
oops, meant to approve, my comment isn't blocking
Actually you can directly modify the changelog section, and the release process will parse it. No need to modify this list for that. |
Yep that's what I meant, is picking a commit from the but I guess you answered yes |
algolia/api-clients-automation#434 Co-authored-by: Eunjae Lee <[email protected]>
🧭 What and Why
🎟 JIRA Ticket: https://algolia.atlassian.net/browse/APIC-372
Changes included:
It updates the release issue to display skipped commits.
example1.
![ScreenShot 2022-04-26 at 16 04 42@2x](https://user-images.githubusercontent.com/499898/165319142-50ff69e5-04b6-4c67-aa75-fcb4240d9c08.png)
example2.
![ScreenShot 2022-04-26 at 16 04 27@2x](https://user-images.githubusercontent.com/499898/165319153-f7be056c-e424-494f-9c6a-196c9f73146b.png)
🧪 Test