Repository navigation
Skip running CI jobs from on-pr.yml if PR is draft - #773
Conversation
- Inspired by changes from tt-mlir deployed in Feb - Allows us to iterate on changes without CI being triggered
2eae2d4 to
d9ab422
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #773 +/- ##
==========================================
+ Coverage 71.66% 71.76% +0.09%
==========================================
Files 18 18
Lines 2580 2603 +23
==========================================
+ Hits 1849 1868 +19
- Misses 731 735 +4 ☔ View full report in Codecov by Sentry. |
nsumrakTT
left a comment
There was a problem hiding this comment.
I don't think this is necessary.
"Normal" development workflow is to open a draft, check if everything is ok, and then upgrade PR to ready to review.
If for any reason you want to iterate without CI just add:
skip-checks:true
to the end of your commit message. Here is doc how to skip CI with several variants:
https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/skipping-workflow-runs
|
Alternatively, for contractors we can use same workflow as for community members: CI will not run until someone from the team pushes a button allowing normal PR run. |

Ticket
None
Problem
What's changed
Verification