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
This repo has been configured to require the build workflow to pass for any PR before it can be merged. The build workflow ignores changes that only modify .md files:
That also applies to auto-merge; it can be activated, but will never happen due to the pending "required" checks (eg #1379)
Hopefully the "required checks" system will be improved to handle this case, but in the meantime perhaps it's worth investigating one of the workarounds from this thread:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This repo has been configured to require the build workflow to pass for any PR before it can be merged. The build workflow ignores changes that only modify .md files:
runner/.github/workflows/build.yml
Lines 14 to 15 in b6dbf42
Skipped workflows are treated as "not succeeded", which means PRs that only update documentation are blocked from merging:
https://github.community/t/unable-to-merge-pull-request-due-to-branch-protection-rules-since-github-actions-check-doesnt-trigger/126250
That also applies to auto-merge; it can be activated, but will never happen due to the pending "required" checks (eg #1379)
Hopefully the "required checks" system will be improved to handle this case, but in the meantime perhaps it's worth investigating one of the workarounds from this thread:
https://github.community/t/feature-request-conditional-required-checks/16761
That way the workflow would always succeed for docs-only PRs due to the build steps/jobs being skipped.
Beta Was this translation helpful? Give feedback.
All reactions