-
Notifications
You must be signed in to change notification settings - Fork 160
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
Help me identify which forks/PRs are worth merging #525
Labels
Comments
Evening! I had a look into #416 and the associated PR: #497. As far as I can tell, it's safe to merge. It's already being used in a separate npm package (2k weekly downloads), and the travis errors are the same as all the other PRs. I put a little more detail in a comment on the PR as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey all! I'm an old colleague of @mzgoddard's, and he was kind enough to grant me maintainer rights on this repo to help clean up some of the backlog. Unfortunately I'm juggling a lot of projects, and do not have the time or background to thoroughly triage the issues and PRs open here.
Asking for help: If we can get consensus about which PRs or forks are commonly in use to work around issues, that'll give me the clarity I need to test and merge / release those PRs in the time I have available.
I'm also looking for other folks who have been iterating on this code who would be interested in helping to maintain it to clear out the issue backlog.
Thanks, 🙏
The text was updated successfully, but these errors were encountered: