You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: features/integration-github-bitbucket-gitlab.md
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,3 +68,20 @@ Private Packagist integrates with the following systems:
68
68
* Webhooks:
69
69
* Users need to [create a Service Hook](https://docs.microsoft.com/en-us/azure/devops/service-hooks/services/webhooks?view=azure-devops) using the generic hook URL from the package page
70
70
* Select the "Code pushed" event (includes commits and tags) and the repository that matches the package. No authentication or additional configuration is necessary.
71
+
72
+
## General webhook setup
73
+
74
+
If automatic webhook configuration isn't available for your repository, you'll need to set up webhooks manually.
75
+
76
+
Find your unique webhook URL on the package details page. It will look like this:
77
+
78
+
`Hook URL: POST https://packagist.com/hooks/generic/1234567/a1b2c3d4e5f6g7h8i9a1b2c3d4e5f6g7h8i9`
79
+
80
+
Configure your webhook to trigger on the following repository events:
81
+
- On each push
82
+
- When a branch is created
83
+
- When a branch is deleted
84
+
- When a tag is created
85
+
- When a tag is deleted
86
+
87
+
These events ensure your package metadata stays synchronized with your repository changes, enabling automatic updates when you publish new versions or modify your codebase.
0 commit comments