Requesting support for version-controlled CI/CD pipeline triggers and input sets, including the ability to select and manage specific versions during pipeline execution.

In particular, pipeline triggers should support Git-backed/versioned storage so that trigger definitions can be stored, reviewed, and managed directly from GitHub alongside pipeline code.

Current Limitation

Currently:

Pipelines themselves can be versioned and managed through Git experience.

Triggers and input sets are not fully version-aware in the same way.

Changes to triggers/input sets can overwrite previous configurations without clear version history or rollback capability.

Trigger configurations are not easily reviewable through standard Git workflows (PR review, audit trail, revert, branch-specific behavior, etc.).

This creates operational challenges when managing multiple environments, release workflows, or evolving CI/CD logic.

Requested Enhancement:

Support versioning of CI/CD triggers with:

Git-backed storage of trigger YAML/configuration

Ability to save trigger definitions in GitHub repositories

PR review workflow for trigger changes

Version history and rollback support

Branch-aware trigger configurations

Ability to select or pin a specific trigger version

Support versioning for input sets with:

Full version history

Ability to select specific input set versions during execution

Rollback capability

Git-backed configuration support

Environment/release-specific input set management

Allow users to:

Select which version of a trigger or input set should be used

Associate trigger versions with specific pipeline versions

Promote validated configurations across environments