Updating migration guide for single-line disable

[justinhelmer]

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)

The multiline comment string doesn't seem to work.

Main docs page is right; JSCS migration guide appears to be wrong.

Is there anything you'd like reviewers to focus on?

[jsf-clabot]

Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Justin Helmer seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.

[eslintbot]

Thanks for the pull request, @justinhelmer! I took a look to make sure it's ready for merging and found some changes are needed:

• The commit summary needs to begin with a tag (such as Fix: or Update:). Please check out our guide for how to properly format your commit summary and update it on this pull request.

Can you please update the pull request to address these?

(More information can be found in our pull request guide.)

[justinhelmer]

as requested

[platinumazure]

Thanks! Can you please sign our Contributor License Agreement?

[platinumazure]

LGTM, thanks for contributing!

[ilyavolodin]

@justinhelmer just a friendly ping. Could you sign our CLA? Unfortunately we can't merge anything without a signed CLA.

[kaicataldo]

@justinhelmer Friendly ping. We'd love to land this, but we unfortunately can't until the CLA is signed.

[justinhelmer]

I signed this way back.

[justinhelmer]

The status in the comment is incorrect, it was signed a long time back

[kaicataldo]

@kborchers Hi! Any idea what might be going on here re the CLA bot?

[kborchers]

The commit was made by an account that GitHub doesn't recognize so this was either done with a different account that was deleted or something was done to the commit that edited the author information so it can't be tied to @justinhelmer.

[aladdin-add]

oh, I have encountered it before(my first contribution to ESLint 😄 ).
maybe it's because your git configed email has not been added in github. could you please check it? @justinhelmer

[platinumazure]

@justinhelmer Have you had a chance to look into the CLA issue, using the information provided here and here?

[justinhelmer]

@platinumazure apologize for not getting back sooner, I have been out of town.

I added my work email, hoping it will solve the problem

[justinhelmer]

The CLA assistant continues to show it signed, but it doesn't allow me to change emails. Let me know if there is any other action I need to take.

[platinumazure]

Closing/reopening the pull request seems to have fixed the CLA status. Now the only issue is the commit message (should just start with "Docs:"). Maybe we could take care of that on merge, but if you do get a chance to amend the commit summary, that would be super awesome. Thinks!

[justinhelmer]

edit: I wrote Fix: instead... updating now.

[justinhelmer]

Done!

[platinumazure]

Thank you! This looks good to me, I'll go ahead and merge shortly (assuming the Travis and AppVeyor checks pass). Thanks so much for your patience on this!