test: Add fuzz test for ParseWebHook

[YooLCD]

Add a native Go fuzz target for ParseWebHook to improve robustness
and support future OSS-Fuzz integration.

Seeds all known event types via MessageTypes() and EventForType()
to maximize coverage of valid JSON decoding paths.
The fuzzer verifies that no input triggers a panic or nil pointer dereference.

To run:

go test -fuzz=^FuzzParseWebHook$ -fuzztime=30s .

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.67%. Comparing base (3117b62) to head (9aa8f50).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #4076   +/-   ##
=======================================
  Coverage   93.67%   93.67%           
=======================================
  Files         211      211           
  Lines       19478    19478           
=======================================
  Hits        18246    18246           
  Misses       1034     1034           
  Partials      198      198           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[gmlewis]

Thank you, @YooLCD!

Quick question: Is the intention to run this fuzz test manually periodically, or were you thinking of integrating this into the CI/CD pipeline?
Also, what do you think about adding the go test ... command line example from the PR description to the comment on lines 14-15 for easy reference?

LGTM.
Awaiting second LGTM+Approval from any other contributor to this repo before merging.

cc: @stevehipwell - @alexandear - @zyfy29 - @Not-Dhananjay-Mishra - @munlicode

[YooLCD]

Thank you for the review, @gmlewis!

1. The intention is to integrate this into OSS-Fuzz so it runs continuously in the cloud.

2. Good idea — I'll add the command to the comment.

[gmlewis]

Thank you for the review, @gmlewis!

1. The intention is to integrate this into OSS-Fuzz so it runs continuously in the cloud.
2. Good idea — I'll add the command to the comment.

OK, great! What do you think about adding the link https://google.github.io/oss-fuzz/ to the comment as well so other people can easily find OSS-Fuzz ?

[YooLCD]

Done! I've added the OSS-Fuzz link and fixed the formatting in the latest commit.

[munlicode]

LGTM

[gmlewis]

Thank you, @munlicode!
Merging.

[YooLCD]

@gmlewis Hi, I'm working on integrating go-github into OSS-Fuzz.
The reviewer is requesting maintainer approval and a maintainer email address
for project.yaml. Could you provide these if possible?

[gmlewis]

@gmlewis Hi, I'm working on integrating go-github into OSS-Fuzz. The reviewer is requesting maintainer approval and a maintainer email address for project.yaml. Could you provide these if possible?

I would prefer to be contacted either through a GitHub issue as @gmlewis or contacted via Keybase.io as @gmlewis as can be viewed in my GitHub bio.

[YooLCD]

Sorry for the inappropriate place to contact you. I'll reach out via Keybase.