This is not needed as workflows that are run manually (via the workflow_dispatch trigger) already offer a way to select the branch from which they should run:
Value and/or benefit
Not having duplicate UI items to specify a branch from which to run the workflow (i.e., a dropdown and a textbox) will make things more intuitive for developers triggering the workflows manually.
Feature description
We are currently adding
branchas an input for our cloud provider workflows as a way to specify the Nebari branch to deploy, test, destroy. For example: https://github.com/nebari-dev/nebari/blob/855aa14ecc32625a98ec01b017acfc8a4af3c017/.github/workflows/test_aws_integration.yaml#L6-L12This is not needed as workflows that are run manually (via the
workflow_dispatchtrigger) already offer a way to select the branch from which they should run:Value and/or benefit
Not having duplicate UI items to specify a branch from which to run the workflow (i.e., a dropdown and a textbox) will make things more intuitive for developers triggering the workflows manually.
Anything else?
No response