Support “Move to Git” for Triggers
complete
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
complete
Closing this as a duplicate