Skip to content
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

Merged
merged 2 commits into from
Aug 10, 2022
Merged

fix: update push payload descriptions #691

merged 2 commits into from
Aug 10, 2022

Conversation

octokitbot
Copy link
Collaborator

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.

@octokitbot octokitbot added the Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR label Aug 10, 2022
@ghost ghost added this to Inbox in JS Aug 10, 2022
@ghost ghost moved this from Inbox to Maintenance in JS Aug 10, 2022
@timrogers timrogers changed the title 🤖📯 Octokit webhooks changed fix: update push payload descriptions Aug 10, 2022
@timrogers timrogers merged commit 5d5bb3c into master Aug 10, 2022
@timrogers timrogers deleted the webhooks-update branch August 10, 2022 17:14
JS automation moved this from Maintenance to Done Aug 10, 2022
@octokitbot
Copy link
Collaborator Author

🎉 This PR is included in version 6.3.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

@wolfy1339
Copy link
Member

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.

@timrogers
Copy link
Contributor

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?

@wolfy1339
Copy link
Member

Ah, I forgot that there was the schema files too see_no_evil Shall I create a PR to do that?

Yes, please do.

Reckon it's worth adding something to the PR body too to explain what you need to do?

That would probably be good
I did recently update the CONTRIBUTING.md with some information

@wolfy1339 wolfy1339 mentioned this pull request Aug 10, 2022
timrogers added a commit that referenced this pull request Aug 11, 2022
… 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.
wolfy1339 pushed a commit that referenced this pull request Aug 11, 2022
… 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`
wolfy1339 pushed a commit that referenced this pull request Aug 25, 2022
… 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`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR
Projects
No open projects
JS
  
Done
Development

Successfully merging this pull request may close these issues.

None yet

3 participants