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

Docs: Add jscs-dev.github.io links to rule names in docs #10771

Merged
merged 1 commit into from Aug 18, 2018

Conversation

santanaG
Copy link
Contributor

What is the purpose of this pull request? (put an "X" next to item)

[X ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:

What changes did you make? (Give an overview)
I "reverted" a recent pull request that removed links for JSCS rule names spread through the docs. I have replaced them with the new jscs-dev.github.io link target.

Is there anything you'd like reviewers to focus on?
I am probably stepping on this guy's toes ( #10736 ) by doing this but it is a trivial change, and I hope everyone forgives me. If possible though, could I get some guidance on how to deal with the other suggested PRs? #10706 and #10737 as well as any other ones I may have missed? One of them is stuck in triage. I am merely attempting to get some of this stuff moving along through the pipes. Any help with this is appreciated. A way to consolidate all these might be even better!

@eslint-deprecated eslint-deprecated bot added the triage An ESLint team member will look at this issue soon label Aug 17, 2018
@aladdin-add aladdin-add added enhancement This change enhances an existing feature of ESLint documentation Relates to ESLint's documentation accepted There is consensus among the team that this change meets the criteria for inclusion and removed triage An ESLint team member will look at this issue soon labels Aug 17, 2018
@platinumazure
Copy link
Member

Closing and reopening to see if the CLA check will repair itself.

@platinumazure
Copy link
Member

@kborchers Any idea what's going on with the license check in this PR?

@ilyavolodin ilyavolodin reopened this Aug 18, 2018
@not-an-aardvark
Copy link
Member

not-an-aardvark commented Aug 18, 2018

The CLA bot problem should be solved. I had accidentally broken it in this organization by enabling OAuth app restrictions, but I granted it permission and it seems to be working again. Sorry about the confusion!

@ilyavolodin ilyavolodin merged commit a70909f into eslint:master Aug 18, 2018
@eslint-deprecated eslint-deprecated bot locked and limited conversation to collaborators Feb 15, 2019
@eslint-deprecated eslint-deprecated bot added the archived due to age This issue has been archived; please open a new issue for any further discussion label Feb 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
accepted There is consensus among the team that this change meets the criteria for inclusion archived due to age This issue has been archived; please open a new issue for any further discussion documentation Relates to ESLint's documentation enhancement This change enhances an existing feature of ESLint
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants