[GH-ISSUE #422] Trigger GitHub App deployment on fork-sync event #279

New issue

Open

opened 2026-03-03 11:14:28 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 11:14:28 +03:00

Owner

Originally created by @pavanbhaskardev on GitHub (Aug 20, 2025).
Original GitHub issue: https://github.com/dflow-sh/dflow/issues/422

Currently, the GitHub App deployment is triggered for the x-github-event: push. To improve deployment automation, we need to also trigger deployments when a fork-sync event occurs.

Proposed Solution:

Update the event handler to check for the fork-sync event.
Ensure deployment is triggered when a fork-sync is received, similar to how it works for push events.
Test that deployments occur successfully for both event types.

Motivation:

Automatically deploying on fork-sync keeps forked repositories up-to-date and consistent with the main branch.

Additional Context:

This will help maintain parity between forks and the source repo, improving developer experience and CI workflows.

Originally created by @pavanbhaskardev on GitHub (Aug 20, 2025). Original GitHub issue: https://github.com/dflow-sh/dflow/issues/422 Currently, the GitHub App deployment is triggered for the `x-github-event: push`. To improve deployment automation, we need to also trigger deployments when a `fork-sync` event occurs. **Proposed Solution:** - Update the event handler to check for the `fork-sync` event. - Ensure deployment is triggered when a `fork-sync` is received, similar to how it works for `push` events. - Test that deployments occur successfully for both event types. **Motivation:** - Automatically deploying on fork-sync keeps forked repositories up-to-date and consistent with the main branch. **Additional Context:** - This will help maintain parity between forks and the source repo, improving developer experience and CI workflows.