-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Moving spelling file to its own directory (for vscode integration) and skipping draft PRs #3280
Conversation
…d skipping draft PRs on CI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've not seen any discussion about skipping draft PRs. What's the thinking behind that? I would prefer they run in CI.
Our build pipeline often takes 10 minutes+ to run. If a PR is in draft, why would we want it to run? The developer of the PR is saying it's not ready for review. |
Generally the developer should wait for the CI checks to pass before publishing the PR and marking it ready for review |
I guess my issue is that if draft PRs are slowing actual ready to ship PRs, that seems not ideal. |
…nto 3279-only-run-ci-on-non-draft
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This has been removed - it's now label based.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. Might add a note in the CONTRIBUTING.md stating PR's labeled wit 'do-not-merge' or 'wip' will not trigger CI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
…d skipping draft PRs on CI