Allow actions to trigger from a branch | Voters

Allow actions to trigger from a branch

complete

Mark Cox

Currently when developing a new action it can only trigger a workflow that is on the default branch of a repository.

It would be useful if a branch could be specified so that when a workflow is being amended it can be tested through Port before being merged.

April 11, 2024

Matan Grady

marked this post as

complete

Gur Shafriri

Mark Cox As Julien Carsique mentioned, you can pass the branch name as "ref", as well as adding a user input to define the branch you want to use.

Does this solves your need?

Mark Cox

Gur Shafriri really sorry to take so long to come back to this, do you mean I need to add it as a user input? What I was hoping for is that ref would be an option under invocationMethod e.g.
"invocationMethod": {
"omitPayload": false,
"omitUserInputs": true,
"org": "my-org",
"repo": "my-repo",
"ref": "my-branch",
"reportWorkflowStatus": true,
"type": "GITHUB",
"workflow": "my-workflow.yml"
},

Mark Cox

Did you mean as part of the workflowInputs object? as per https://docs.port.io/actions-and-automations/setup-backend/github-workflow/#specify-a-branch

Doesn't this mean that it runs the workflow from the main branch but then the workflow has to utilise the input to checkout the workflow on that ref?

Julien Carsique

You can use a "ref" string in the action, that will use the corresponding branch or commit SHA