General webhook setup

docs/setup.md

@@ -257,3 +257,24 @@ Once all the repository entries have been added to Private Packagist the setup i
     }
 }
 ```
+
+## General webhook setup
+
+Webhooks are automatically configured for packages from GitHub, GitLab, and Bitbucket when added through synchronization. 
+
+See integration specific information on webhooks here: [Integrations](http://packagist.com.lo/features/integration-github-bitbucket-gitlab)
+
+For other code-hosting platforms or custom setups, you can also configure the webhook manually.
+
+Find your unique webhook URL on the package details page:
+
+![Webhook Setup](/Resources/public/img/docs/integration-setup/webhook-setup.png)
+
+Configure your webhook to trigger on the following repository events:
+- On each push
+- When a branch is created
+- When a branch is deleted
+- When a tag is created
+- When a tag is deleted
+
+These events ensure your package metadata stays synchronized with your repository changes, enabling automatic updates when you publish new versions or modify your codebase.

features/integration-github-bitbucket-gitlab.md

@@ -68,3 +68,10 @@ Private Packagist integrates with the following systems:
 * Webhooks:
     * 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
     * Select the "Code pushed" event (includes commits and tags) and the repository that matches the package. No authentication or additional configuration is necessary.
+
+#### Beanstalk 
+* Code Credentials: Grant us access via SSH key
+* Webhooks:
+  * Users need to [create a Modular Webhooks Integration](https://support.beanstalkapp.com/article/56-modular-webhooks-integration) using the generic hook URL from the package page
+  * Following events need to be selected: `push`, `create_branch`, `delete_branch`, `create_tag`, `delete_tag`
+