Forges
Supported features
| Feature | GitHub | Gitea | Forgejo | Gitlab | Bitbucket | Bitbucket Datacenter |
|---|---|---|---|---|---|---|
| Event: Push | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Event: Tag | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Event: Pull-Request | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Event: Release | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ |
| Event: Deploy¹ | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ |
| Event: Pull-Request-Metadata | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ |
| Multiple workflows | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| when.path filter | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ |
¹ The deployment event can be triggered for all forges from Woodpecker directly. However, only GitHub can trigger them using webhooks.
In addition to this, Woodpecker supports addon forges if the forge you are using does not meet the Woodpecker requirements or your setup is too specific to be included in the Woodpecker core.