🤖📯 Octokit webhooks changed #596
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
octokitbot
added
the
Type: Maintenance
added 3 commits
December 1, 2021 22:08
|
GitHub removed the |
added 21 commits
December 7, 2021 10:09
added 13 commits
December 22, 2021 01:31
|
@wolfy1339 what do we need to do to land this? |
BREAKING CHANGE: remove `content_reference` event
|
Should be ready to go now |
|
On a side note, maybe we should lower the frequency the script runs at. It seems to catch re-renderings that don't affect content a lot of the time |
G-Rath
approved these changes
Dec 22, 2021
|
🎉 This PR is included in version 5.0.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.