Any time a push event occurs on a repo that you're tracking (for GitHub), a
webhook will fire to a URL that you specify. In this case, we have the
root URL looking for a POST request.
What's involved in getting a webhook through to your application? You
just need to pull the data out of the request object that hits the
POST action in the specified route inside your application. For
example, if you're listening for a push event on the /push URL, then
you should expect a request object when the POST request comes in from
the GitHub webhook.
Once you parse the request object properly, you're able to obtain all the necessary data of that push event.
With a secure webhook, however, you set the key in the Webhook configurations on the GitHub repo settings. What this does is that it will somehow encrypt the webhook, and it's much harder to parse through the request data.
Oh, now I get it. It's up to me to secure the webhook - GitHub just simply attaches the secret token onto the webhook object itself. Whoop de doo. Let's try this. Another try. ARgh, another try. Yet another try. This time I added a bunch of print statements to help debug. Welp. Come on now. Trying to make sure that hexdigest is the same type now.