-
Notifications
You must be signed in to change notification settings - Fork 1.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
feat(internal/gapicgen): change commit formatting to match standard #3500
Conversation
Changing the commit formatting so that it can be parsed as a footer with a conventional commits parser. Here is an example of what a commit looked like previously: - docs(dialogflow): update comments on parameters and validation result. PiperOrigin-RevId: 348673154 Source-Link: googleapis/googleapis@0795e3f And what it will look like now: docs(dialogflow): update comments on parameters and validation result. PiperOrigin-RevId: 348673154 Source-Link: googleapis/googleapis@0795e3f
cc @bcoe . Will wait to merge this until the parser work is done. |
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.
High level question: looking at https://www.conventionalcommits.org/en/v1.0.0/, it seems like there should be an empty line between the first line and the next?
Related PR googleapis/release-please#686 |
@tbpg as we formalize the grammar, I've been advocating that we allow single |
Changing the commit formatting so that it can be parsed as a footer
with a conventional commits parser. Here is an example of what a
commit looked like previously:
docs(dialogflow): update comments on parameters and validation result.
PiperOrigin-RevId: 348673154
Source-Link: googleapis/googleapis@0795e3f
And what it will look like now:
docs(dialogflow): update comments on parameters and validation result.
PiperOrigin-RevId: 348673154
Source-Link: googleapis/googleapis@0795e3f