-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
Only run on pull requests that are "ready for review" not "draft" pull request. #29
Comments
There is if expression in GitHub Actions, so you can implement filtering outside action-eslint. |
Thanks for the pointer, ill look into it 👍 |
but how would you check if a PR is ready for review @haya14busa ? that page just introduces if-statements, but not an actually expression to do so. any hints? :) |
In your job, you can use the statement:
To ensure the job will not run against PR drafts. But, you probably also want the job to run when the PR status changes from draft to 'ready for review' As per the docs, the default 'types' of pull-request that trigger your CI are
|
To reduce the number of chromatic runs we are going to not run chromatic until the PR is marked as ready. Reference reviewdog/action-eslint#29 (comment)
To reduce the number of chromatic runs we are going to not run chromatic until the PR is marked as ready. Reference reviewdog/action-eslint#29 (comment)
See reviewdog/action-eslint#29 (comment) for an explanation on how to filter out draft PRs.
See reviewdog/action-eslint#29 (comment) for an explanation on how to filter out draft PRs. Co-authored-by: hello-vinitha <[email protected]>
Hello,
Is there a way to make this only run on pull requests which are ready for review instead of draft pull requests.
I tried adding the following type to "ready_for_review" which only gets run when marking the PR ready for review, but not on code changes then. So i added
synchronize
to make it work on code changes, but it runs on code changes even in draft pull requests.I want it to only run on code changes on pull request which are ready for review.
The text was updated successfully, but these errors were encountered: