-
Notifications
You must be signed in to change notification settings - Fork 41
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
fix: update push
payload descriptions
#691
Conversation
push
payload descriptions
🎉 This PR is included in version 6.3.3 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Whenever there's description updates from the docs, don't forget to add them to the relevant schemas as they don't get automatically updated by the automation. |
Ah, I forgot that there was the schema files too 🙈 Shall I create a PR to do that? Reckon it's worth adding something to the PR body too to explain what you need to do? |
Yes, please do.
That would probably be good |
… files in `commits` This PR applies the changes detected in #691 to the schemas. They were automatically applied to the examples, but I forgot to make the manual schema changes.
… files in `commits` (#695) * fix: update schema descriptions for `added`, `removed` and `modified` files in `commits` This PR applies the changes detected in #691 to the schemas. They were automatically applied to the examples, but I forgot to make the manual schema changes. * fix: update type descriptions for `added`, `removed` and `modified` files in `commits`
… files in `commits` (#695) * fix: update schema descriptions for `added`, `removed` and `modified` files in `commits` This PR applies the changes detected in #691 to the schemas. They were automatically applied to the examples, but I forgot to make the manual schema changes. * fix: update type descriptions for `added`, `removed` and `modified` files in `commits`
I found new changes on GitHub’s Webhooks Event Types & Payloads and want to let you know about it 👋🤖
I can't tell if the changes are fixes, features or breaking changes. You'll have to figure that out on yourself and adapt the commit messages accordingly to trigger the right release, see our commit message conventions.