Version or commit hash
rolling
Steps to reproduce issue and expected behavior
The stacks repo currently has required checks that don't map accurately to the workflows that are being run:
This blocks PRs from being merged (and so for now they need to be force merged).
We need someone with admin permissions (I believe) to change the branch protections to the new naming scheme.
Alternatively we can also change the moveit2-build.yml and nav2-build.yml workflows to trigger on PR as opposed to being triggered on workflow_call by ci.yml (originally introduced by #263). This would be a bummer however, as I quite like the original change.
Actual behavior
PRs should be able to merge without a force merge if CI passes.
Backtrace or Console output
No response
Version or commit hash
rolling
Steps to reproduce issue and expected behavior
The stacks repo currently has required checks that don't map accurately to the workflows that are being run:
This blocks PRs from being merged (and so for now they need to be force merged).
We need someone with admin permissions (I believe) to change the branch protections to the new naming scheme.
Alternatively we can also change the
moveit2-build.ymlandnav2-build.ymlworkflows to trigger on PR as opposed to being triggered onworkflow_callbyci.yml(originally introduced by #263). This would be a bummer however, as I quite like the original change.Actual behavior
PRs should be able to merge without a force merge if CI passes.
Backtrace or Console output
No response