-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
The status of pull requests #220
Comments
Hi, yes this is on me. I don't have a great excuse other than that I've taken on quite a bit more work than I've been able to keep up with. You've prompted me to actively start reaching out to a few people and see if I can get some more hands on deck here to help keep Jest moving forward...so hopefully we can make that happen very soon. In the meantime: I'm on a plane all day tomorrow -- so barring plane wifi issues, I will try to go through all of the pending PRs and hopefully we can get them sorted out as soon as possible. |
Thanks. This is for you. 🍺 |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
There are about 15 open pull requests waiting a response right now –– some of them are very essential to make Jest useful for us, like making jest aware of NODE_PATH, and some have been waiting for months for an official response. Are there any plans to formally review and maybe integrate these requests into the master branch? Please?
The text was updated successfully, but these errors were encountered: