Thanks to visit codestin.com
Credit goes to github.com

Skip to content

docs(eslint-plugin): correct link to FAQ.md #1488

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

Merged
merged 1 commit into from
Jan 21, 2020

Conversation

Userbit
Copy link
Contributor

@Userbit Userbit commented Jan 21, 2020

No description provided.

@typescript-eslint
Copy link
Contributor

Thanks for the PR, @Userbit!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!


🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day.

@Userbit Userbit changed the title Correct link to FAQ.md chore: correct link to FAQ.md Jan 21, 2020
@bradzacher bradzacher added the documentation Documentation ("docs") that needs adding/updating label Jan 21, 2020
@bradzacher bradzacher changed the title chore: correct link to FAQ.md docs(eslint-plugin): correct link to FAQ.md Jan 21, 2020
@bradzacher bradzacher merged commit 0948896 into typescript-eslint:master Jan 21, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Documentation ("docs") that needs adding/updating
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants