-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Circle no longer runs on external contributor PRs #3802
Comments
I assume this is blocking for my PR right? Are there any schedules for the next release? |
@lennerd don't worry about it, it's just an inconvenience on the maintainer side since we have to run the tests manually to verify that they pass. It's not blocking your PR. |
I was poking around in CircleCI recently in an attempt to resolve #3603 more elegantly. It's possible I triggered this regression. I will take a look today. |
Thank you for your awesome peace of software and services! We enjoy using it! :) |
This regression is due to a breaking change made by CircleCI in which forked PRs do not trigger builds by default. See https://discuss.circleci.com/t/pull-request-from-forked-repos-are-not-being-tested/8588/3 I have resolved the issue by enabling the "build forked pull requests" setting. |
I noticed that since a few days ago, Circle is no longer running on external PR commits. Examples: #3783 #3781. This makes reviewing PRs much harder, so we should investigate what happened.
cc @lucaswoj @jfirebaugh
The text was updated successfully, but these errors were encountered: