Per-environment GitHub branch at the environment level
kostaslampropoulos
HOBBYOP
2 days ago
Branch is configured per-service, per-environment. For a project with many services (frontend, backend, workers, crons, queue) this means clicking into every service and changing the branch whenever I want staging to track a different feature branch.
Would love a single branch setting at the environment level that all GitHub-connected services inherit, with per-service override if needed. Flightcontrol does this: one config maps an env to a branch and every service follows.
for example:
main -> production, develop -> staging, feat/* -> preview
quickly point staging at a feature branch for QA without touching N services
monorepo projects where all services deploy from the same branch anyway
0 Threads mention this feature
0 Replies