Add all configuration

[darkred]

Implements #247

I hope I didn't miss anything.

Note to reviewers:

I see that the last test action CI / update fails but I can't find why.

[ota-meshi]

I see that the last test action CI / update fails but I can't find why.

Run the npm run update command.

[darkred]

I just did (while on my add-all-configuration branch)
and the resulting uncommitted changes reverted my changes in README.md and all.ts *(it's now identical to recommended.ts).
Please see screenshots of the changes: 1, 2, 3

[RunDevelopment]

I think the easiest way to make the all config is to import the recommended config, make a copy of it and then add all rules that aren't included already. This would also mean that won't have to change any scripts/* files and won't have problems with npm run update.

[ota-meshi]

docs/user-guide/README.md is automatically generated from README.md. Update README.md and run npm run update.

[darkred]

@ota-meshi
To be sure, I deleted my cloned directory altogether, then cloned again my fork.

Then I just updated README.md (I mean the root one)
and ran npm run update
and now my lib\configs\all.ts once again became identical to lib\configs\recommended.ts (uncommitted changes).

How can I fix this? What have I missed?

[RunDevelopment]

now my lib\configs\all.ts once again became identical to lib\configs\recommended.ts (uncommitted changes).

How can I fix this? What have I missed?

Well, in tools/update-rulesets.ts you instruct npm run update to do exactly that. Just revert the file.

[ota-meshi]

LGTM! Thank you very much for your contribution!

[darkred]

You are welcome. I'm glad I could contribute!
Thank you both for the help.