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

Find some help to deal with pull requests and issues #420

Closed
marclaporte opened this issue Sep 3, 2022 · 3 comments
Closed

Find some help to deal with pull requests and issues #420

marclaporte opened this issue Sep 3, 2022 · 3 comments

Comments

@marclaporte
Copy link

The number of contributions is quite high here: https://github.com/cweagans/composer-patches/pulls but the number of commits is quite low: https://github.com/cweagans/composer-patches/commits/master

I wonder if it would be a good idea to ask all previous contributors if someone would be interested in helping with the project?

@cweagans
Copy link
Owner

cweagans commented Sep 3, 2022

I'm interested in help, but it has to be done with care given the barely-present tests. Just merging the PRs isn't the right thing. Highest value work here would be to write tests.

I'm also not super interested in having all the features directly in this package. I'm more inclined to support ways for other people to extend this plugin with their own.

All of that said, there's been some work behind the scenes here organizing some work + it's looking like I will have some time this month to finally do some work on this plugin again.

@danepowell
Copy link
Collaborator

I'm helping to merge the most critical PRs. Like Cameron said, we can't merge anything risky due to the limited test coverage, but if there's something truly breaking you can ping me and I'll try to review it.

@cweagans
Copy link
Owner

cweagans commented Feb 3, 2023

FYI: As part of my work on 2.x (#447), I intend to review issues and pull requests and either fix or close them. There will probably be a lot of things that just get closed, but we'll see.

@cweagans cweagans closed this as completed Feb 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants