Skip to content

Commit 81e7e46

Browse files
author
Jie Min Wong
committed
re-add section on adding web hook
1 parent 47084cb commit 81e7e46

File tree

1 file changed

+31
-0
lines changed

1 file changed

+31
-0
lines changed

docker-hub/builds/classic.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,37 @@ Likewise, you can switch back to new Automated Build by clicking on this link at
3838
![Switching to new Automated Build](images/classic-vs-new-switch-to-new.png)
3939

4040

41+
42+
## Adding Github web hook manually
43+
44+
A GitHub webhook allows GitHub to notify Docker Hub when something has
45+
been committed to a given Git repository.
46+
47+
When you create a Classic Automated Build, a webhook should get automatically added to your GitHub
48+
repository.
49+
50+
To add, confirm, or modify the webhook, log in to GitHub, then navigate to
51+
the repository. Within the repository, select **Settings > Webhooks**.
52+
You must have admin privileges on the repository to view or modify
53+
this setting. Click **Add webhook**, and use the following settings:
54+
55+
56+
| Field | Value |
57+
| ------|------ |
58+
| Payload URL | https://registry.hub.docker.com/hooks/github |
59+
| Content type | application/json |
60+
| Which events would you like to trigger this webhook? | Just the push event |
61+
| Active | checked |
62+
63+
The image below shows the **Webhooks/Add webhook** form with the above settings reflected:
64+
65+
![github-webhook-add](images/github-webhook-add.png)
66+
67+
If configured correctly, you'll see this in the **Webhooks** view
68+
![github-webhook](images/github-webhook.png)
69+
70+
71+
4172
## Frequently Asked Questions
4273

4374

0 commit comments

Comments
 (0)