-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Invitation to move to official eslint-community
org
#297
Comments
Thanks. It looks like I don't have permission to transfer this repository to @eslint-community because I'm not allowed to create public repositories in that organization. Seems like there are a few possible workarounds:
|
@not-an-aardvark I've created a team with you (& @aladdin-add?) for this repo & invite you |
I've transferred the repository. Thanks for getting Let me know if there's anything else I should do. From skimming this, it seems like I should add |
I think it would be good to add both |
Ok, I've added those three accounts. |
Probably also a good idea to add the |
We would love to have this repo added to the official
@eslint-community
organization on GitHub.As you can read in the '
@eslint-community
GitHub organization' RFC, the goal of this new org is to have a place where community members can help ensure widely depended upon ESLint related packages stay up to date with newer ESLint releases and doesn't hold the wider community back without depending on one person's GitHub/npm
account.Since this plugin is (together with
eslint-plugin-node
) a recommended plugin for linting custom plugins & since you —@not-an-aardvark— (according to eslint/rfcs#91 (comment)) already discussed with @aladdin-add to transfer this repo to a better home, you're welcome to transfer this repository to the new org.The text was updated successfully, but these errors were encountered: