You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
This request is related to the problem of triggering workflows from another workflow. I Don't like the solution of using PAT of some user that then gets the responsibility and ownership over the comments and the generated PRs.
In my case, the workflow I need to trigger can be triggered by un-drafting the PR. So the solution I'm thinking about is to have the following steps for the backporting job:
convert the PRs back to "ready for review" using the gh CLI using a PAT again
This way I get the default behavior of the action-bot commenting and opening the PRs, but also triggering the workloads I need. One link is missing though...
Describe the solution you'd like
There is no simple way of getting the PRs that the action generated at the moment. I wish the action could output the new PR numbers as an output, so I could go over them and perform this additional steps.
I believe this could be a useful output for other users with other scenarios as well.
Additional option is to enable the PRs to be created as draft by the action. Will save me an API call but not much more :)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
This request is related to the problem of triggering workflows from another workflow. I Don't like the solution of using PAT of some user that then gets the responsibility and ownership over the comments and the generated PRs.
In my case, the workflow I need to trigger can be triggered by un-drafting the PR. So the solution I'm thinking about is to have the following steps for the backporting job:
GITHUB_TOKEN
gh
CLI using a PATgh
CLI using a PAT againThis way I get the default behavior of the action-bot commenting and opening the PRs, but also triggering the workloads I need. One link is missing though...
Describe the solution you'd like
There is no simple way of getting the PRs that the action generated at the moment. I wish the action could output the new PR numbers as an output, so I could go over them and perform this additional steps.
I believe this could be a useful output for other users with other scenarios as well.
Additional option is to enable the PRs to be created as draft by the action. Will save me an API call but not much more :)
The text was updated successfully, but these errors were encountered: