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
{{ message }}
Repository navigation
GitHub auto-deploy does not trigger when webhook owner name is missing #4675
Configure an application or Docker Compose project with the GitHub provider.
Enable auto-deploy for GitHub push or tag events.
Select a repository through the GitHub provider UI. Dokploy stores the
repository owner from repo.owner.login.
Push a commit to the configured branch, or push a configured tag, with a
GitHub webhook payload where repository.owner.login is present but repository.owner.name is missing or null.
Observe the GitHub webhook handler processing the event without finding the
configured application or compose project.
Current vs. Expected behavior
Current behavior:
GitHub push/tag webhooks can be received and verified, but auto-deploy does
not start.
The webhook handler matches configured applications and compose projects
using repository.owner.name.
The GitHub provider UI stores the owner using repo.owner.login.
When the webhook payload does not include owner.name, the query uses the
wrong owner value and returns no deployable resources.
Expected behavior:
Dokploy should match GitHub webhook repositories using the same owner value
saved by the GitHub provider UI.
Push/tag webhooks with repository.owner.login should find the configured
application or compose project and enqueue the deployment.
Provide environment information
Dokploy version: current canary before PR #4674
Affected source: GitHub App provider webhook
Affected trigger types: push, tag
Affected deployment types: application, Docker Compose
Environment-specific: no; this depends on GitHub webhook payload shape and stored provider metadata
Which area(s) are affected? (Select all that apply)
Application
Docker Compose
Are you deploying the applications where Dokploy is installed or on a remote server?
Both. The bug happens before the deployment target is selected because no
matching deployable resource is found.
The PR changes the GitHub webhook handler to resolve the repository owner as repository.owner.login ?? repository.owner.name and adds regression coverage
for push application, push compose, tag deploy, and branch mismatch behavior.
Activity