-
Notifications
You must be signed in to change notification settings - Fork 2
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
Sync PRs on orignal repo #3
Comments
Yep, i'm doing it, like right now... I have some questions about some of the PRs, and legitly about 1/3 of the PRs seem to be dupes of one another. Seriously, the 500 on huge chrome buffer is like 3 or 4 of the existing PRs. |
@hopeseekr, thank you for your explanation. I just note that we have to update PR status on the original repository and it can notify original PR authors. |
You can @ notify them. I think that's what's needed most at this point... |
@hopeseekr can you add this updated repo to packagist? I would like to use it with composer. The original code of ccampbell is outdated and gives issues which are solved in this repo. |
So did I effectively fork this project but forget to publish??? |
I don't find this forked package on the packagist. Perhaps you should check that. |
As title, I create the issue on issue #71 in original repo.
Because original repo seems to be inactive/unmaintained by @ccampbell, I try think about the PR synchronization.
I think we should move all PRs on original repos to this forked repos and keep this forked repos be maintained.
@hopeseekr , What do you think about this?
The text was updated successfully, but these errors were encountered: