triggers in git experience
long-term
V
Vanilla Pigeon
Hello, we would like to be able to handle triggers in git experience same as pipelines and input sets.
Currently everything but triggers is able to be maintained by git experience, leading to a situation where you think everything is managed in code, but it really is not and you are missing context as to how things work.
This is especially true when onboarding new engineers onto Harness and causes unnecessary confusion.
Thanks

Sudarshan Purohit
updated the status to
long-term
This may be quite hard to do, given that different branches of the trigger may have different runtime configuration and inputs for the pipeline. The user of the trigger would not be expected to specify the branch details.
Given these, am adding this request into long term planning, and we can revisit if a limited solution is possible.
I
Isolated Cat
Will this be available in SMP?