feat: add validate-event-name #1161
Merged
+259
−29
Conversation
This file contains hidden or 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
Contributor
|
👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with |
wolfy1339
reviewed
Jun 29, 2025
Co-authored-by: wolfy1339 <4595477+wolfy1339@users.noreply.github.com>
wolfy1339
approved these changes
Jun 29, 2025
Contributor
|
🎉 This PR is included in version 14.1.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
2 participants
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.
Migrating a modified validateEventName typeguard/typeassertion from Probot to webhooks.js
Resolves #ISSUE_NUMBER
Before the change?
Currently the logic to validate the input of the eventName is in
.on()method. It is impossible to reuse it.After the change?
There are no behavioral changes. I just extracted the logic into the new validateEventName. I added a onUnkownEventName and logger option, to make it possible to use it as a stricter typeguard/typeassertion in other projects.
Pull request checklist
Does this introduce a breaking change?
Please see our docs on breaking changes to help!