Skip to content
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

Closed
mourner opened this issue Dec 14, 2016 · 6 comments
Closed

Circle no longer runs on external contributor PRs #3802

mourner opened this issue Dec 14, 2016 · 6 comments
Assignees

Comments

@mourner
Copy link
Member

mourner commented Dec 14, 2016

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

@lennerd
Copy link
Contributor

lennerd commented Dec 14, 2016

I assume this is blocking for my PR right? Are there any schedules for the next release?

@mourner
Copy link
Member Author

mourner commented Dec 14, 2016

@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.

@lucaswoj
Copy link
Contributor

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.

@lucaswoj lucaswoj self-assigned this Dec 14, 2016
@mollymerp
Copy link
Contributor

I was wondering about that... thanks @lucaswoj!

@lennerd no finite schedule for the next release but we should have one out before the holidays 🎄. thanks again for your awesome contribution!

@lennerd
Copy link
Contributor

lennerd commented Dec 15, 2016

Thank you for your awesome peace of software and services! We enjoy using it! :)

@lucaswoj
Copy link
Contributor

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.

screen shot 2016-12-15 at 2 43 17 pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants