Support “Move to Git” for Triggers
long-term
W
Welcome Turtle
Currently, Harness does not support “Move to Git” for triggers, unlike pipelines, templates, and input sets. This limits full GitOps adoption.
Without Git versioning, trigger management becomes manual, error-prone, and lacks auditability. It also creates inconsistency across environments.
Request:
Enable triggers to be managed via Git (YAML), including version control, sync, and promotion across environments—aligned with other entities.
Log In
Sudarshan Purohit
updated the status to
long-term
Sudarshan Purohit
Hi Welcome Turtle, moving triggers to Git in the same manner as other entities raises a few concerns like differing behaviour between git branches, caching and versioning of triggers from Git, the possiblility of invalid trigger YAML, and so on. For this reason, this feature has not been picked up so far. We have it in our long term plan to support Gitx with significant constraints in order to keep trigger behaviour predictable and clear. We'll update this ticket once constraints have been worked out out and an ETA assigned.