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.
Currently, the existing github workflows are only triggered by pull request and push events. However, many of them use external workflows, mainly those defined in nasa/cFS bundle repo, and some 3rd party ones.
Problem is, when merging new code to the cFS bundle repo main branch, there is no way to re-run the cFE workflows against the updated main branch of cFS. Clicking the "Re-Run" button on the previous run doesn't work; it runs with the same bundle commitID as the original did. We need a way to run against the updated main branch of the cFS repo, even when the cFE repo may not have changed at all.
Currently the only way to trigger this is to make a bogus push to a fork, which will trigger the actions to run and will use the latest version.
Describe the solution you'd like
Add "workflow_dispatch" as an option to workflows - especially for anything that references an external workflow or action in the main branch that can in turn be updated outside the merge cycle of the local repo.
Additional context
This provides a simpler, cleaner method to re-validate the cFE workflows are still functioning after a change to the cFS repo.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, the existing github workflows are only triggered by pull request and push events. However, many of them use external workflows, mainly those defined in
nasa/cFS
bundle repo, and some 3rd party ones.Problem is, when merging new code to the cFS bundle repo main branch, there is no way to re-run the cFE workflows against the updated main branch of cFS. Clicking the "Re-Run" button on the previous run doesn't work; it runs with the same bundle commitID as the original did. We need a way to run against the updated
main
branch of the cFS repo, even when the cFE repo may not have changed at all.Currently the only way to trigger this is to make a bogus push to a fork, which will trigger the actions to run and will use the latest version.
Describe the solution you'd like
Add "workflow_dispatch" as an option to workflows - especially for anything that references an external workflow or action in the
main
branch that can in turn be updated outside the merge cycle of the local repo.Additional context
This provides a simpler, cleaner method to re-validate the cFE workflows are still functioning after a change to the cFS repo.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: