Instead of encoding the GitHub snapshot robot access token in a file that needs to be decoded by an
ambiguously named secret called `KEY`, the token can be directly stored in the secrets of CircleCI
given easier maintenance and the same risk.
The leakage of the secret still means the GitHub token file could be decoded. We are switching to a
similar model as in the components repo, which also simplifies key rotations etc.
With this change we update yargs help method to output help in JSON format which is needed to generate the documents that are used to generate AIO man pages.
All TypeScript files have been updated to pass the new eslint-based linting checks. eslint compatible disabling comments have also been added in place of the previous tslint comments.
* ci: snapshots can push to specific branches
Can take either a branch argument, or use CIRCLE_BRANCH if available.
* ci: run snapshots on all branches
