manual gitops should be blocked if deployment_branch is defined
Open
- Dominant language
- Starlark
- Stars
- 208
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
using both manually run gitops with `bazel run //pkg:target.gitops` and automating by defining the `deployment_branch` parameter causes merge conflicts, confusion and a state of deployments hard to reproduce and track.
Generally, canary/production deployments should only use `deployment_branch` so we need to disable the manual gitops option if `deployment_branch` is defined.
Contributor guide
Assessment
This issue has not been assessed yet.