New Blank

[request-info[bot]]

The maintainers of this repository would appreciate it if you could provide more information.

[github-learning-lab[bot]]

Nice try! The label creation endpoint, found here, looks like this: POST /repos/:owner/:repo/labels.

APIs and Webhooks

APIs and Webhooks go hand in hand, but the distinction between them is important.

• Webhooks are specific "noise" interpreters. They listen for specific events to occur as their trigger.
• 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.
• The GitHub API can send information that makes changes to the platform, but only when prompted via webhook.
• The GitHub API and GitHub's webhooks are both key components of GitHub Apps.

Step 10: See your changes in action

Now that you've made the change to your config.yml file, try to trigger that event to see the changes as a user.

:keyboard: Activity: Test out your original changes to the config.yml

1. Go open a blank issue to see if the changes you made in your config.yml took effect!

[rohangupta8756]

@needs-more-info #8

[github-learning-lab[bot]]

Nice try! The label creation endpoint, found here, looks like this: POST /repos/:owner/:repo/labels.

APIs and Webhooks

APIs and Webhooks go hand in hand, but the distinction between them is important.

• Webhooks are specific "noise" interpreters. They listen for specific events to occur as their trigger.
• 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.
• The GitHub API can send information that makes changes to the platform, but only when prompted via webhook.
• The GitHub API and GitHub's webhooks are both key components of GitHub Apps.

Step 10: See your changes in action

Now that you've made the change to your config.yml file, try to trigger that event to see the changes as a user.

:keyboard: Activity: Test out your original changes to the config.yml

1. Go open a blank issue to see if the changes you made in your config.yml took effect!

[rohangupta8756]

67e07540-d887-11eb-9cd1-4c7c07fb5f14

[github-learning-lab[bot]]

Nice try! The label creation endpoint, found here, looks like this: POST /repos/:owner/:repo/labels.

APIs and Webhooks

APIs and Webhooks go hand in hand, but the distinction between them is important.

• Webhooks are specific "noise" interpreters. They listen for specific events to occur as their trigger.
• 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.
• The GitHub API can send information that makes changes to the platform, but only when prompted via webhook.
• The GitHub API and GitHub's webhooks are both key components of GitHub Apps.

Step 10: See your changes in action

Now that you've made the change to your config.yml file, try to trigger that event to see the changes as a user.

:keyboard: Activity: Test out your original changes to the config.yml

1. Go open a blank issue to see if the changes you made in your config.yml took effect!

[rohangupta8756]

[ { "id": 208045946, "node_id": "MDU6TGFiZWwyMDgwNDU5NDY=", "url": "https://api.github.com/repos/octocat/Hello-World/labels/bug", "name": "bug", "description": "Something isn't working", "color": "f29513", "default": true }, { "id": 208045947, "node_id": "MDU6TGFiZWwyMDgwNDU5NDc=", "url": "https://api.github.com/repos/octocat/Hello-World/labels/enhancement", "name": "enhancement", "description": "New feature or request", "color": "a2eeef", "default": false } ]

[github-learning-lab[bot]]

Nice try! The label creation endpoint, found here, looks like this: POST /repos/:owner/:repo/labels.

APIs and Webhooks

APIs and Webhooks go hand in hand, but the distinction between them is important.

• Webhooks are specific "noise" interpreters. They listen for specific events to occur as their trigger.
• 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.
• The GitHub API can send information that makes changes to the platform, but only when prompted via webhook.
• The GitHub API and GitHub's webhooks are both key components of GitHub Apps.

Step 10: See your changes in action

Now that you've made the change to your config.yml file, try to trigger that event to see the changes as a user.

:keyboard: Activity: Test out your original changes to the config.yml

1. Go open a blank issue to see if the changes you made in your config.yml took effect!