secret scanning webhook test token #106640
Replies: 1 comment
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
Hello, I am working on a webhook receiver to audit secrets found from the "secret scanning" functionality. I have created a sandbox repo whereby I can checkin dummy secrets to trigger the webhooks. I've configured the webhooks for the sandbox repo to send everything, and the endpoint is just logging everything.
Problem statement:
When I commit/push a secret to my sandbox repo, the "push" event is received, but, I do not see any events coming from the "secret scanning" scanner.
Is there a test token, or test string that I can add to my sandbox content to trigger the security scanning event? Or, is there a different way to test the security scanning webhook event?
Thank you,
David
Beta Was this translation helpful? Give feedback.
All reactions