-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Please help to maintain eslint-plugin-prettier
, again.
#11361
Comments
It becomes a bit ridiculous since the PR has been raised for more than one year! cc @sosukesuzuki @fisker @j-f1 @thorn0 I'll have to publish a fork instead later... |
|
If @BPScott is not actively maintain There are a lot of old issues. |
@JounQin I see. Btw, You are a contributor to various Open Source and have made many contributions to eslint-plugin-prettier. If we give you GitHub and npm permissions, can you maintain it? (I am not familiar with eslint-plugin-prettier, so I thought you would be better suited than I) |
@sosukesuzuki I'd be happy and pleasure to help to maintain that project. |
@JounQin We can close this? |
After a npm release, I'll close this one. |
Sorry, but I have to raise an issue same as #10699 again.
No really an issue of prettier core itself, sorry.
I've been suffered from prettier/eslint-plugin-prettier#411 and prettier/eslint-plugin-prettier#414. And I've raised two PRs prettier/eslint-plugin-prettier/pull/413 and prettier/eslint-plugin-prettier#415 to fix them, and the current maintainer @BPScott did review 3 months ago, but disappeared again later...
So I'm here to ask for help from the core maintainers.
It's been 4 months since I opened those PRs.
Is there any more active maintainer can offer help?
The text was updated successfully, but these errors were encountered: