Closed Kleist47 closed 5 years ago
Nice job!
In the last pull request, we learned about webhooks and how the WIP and Request Info apps only respond to specific events. Webhooks allow you to build or set up GitHub Apps which subscribe to certain events on GitHub. When one of those events is triggered, an HTTP POST payload response is sent to the webhook's configured URL. We saw this with our smee.io webhook.
But webhooks are only one side to this story. To see the other side, meet API endpoints. :wave:
API stands for Application Programming Interface. APIs are used to share data or functionality. This is done by making an HTTP request to an API using an endpoint, and then receiving a reponse back.
For example, this is the endpoint to create a new pull request; POST /repos/:owner/:repo/pulls
When an event is triggered, the vastly more detailed GitHub API gives the bot an excessive amount of information (as a payload). The bot takes this payload, alters it slightly, and hands it back to GitHub's API, which delivers the change back to your repository.
application/vnd.github.machine-man-preview+json
Nice try! The label creation endpoint, found here, looks like this: POST /repos/:owner/:repo/labels
.
APIs and Webhooks go hand in hand, but the distinction between them is important.
Now that you've made the change to your config.yml
file, try to trigger that event to see the changes as a user.
config.yml
took effect!
We would appreciate it if you could provide us with more info about this issue/pr!