It does repetitive jobs on GitHub repos
Last updated 5 months ago by eomm .
MIT · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install massive-wax 
SYNC missed versions from official npm registry.


oclif Version Downloads/week License

Edit every file of a list of GitHub repositories and open a PR ✨

This tool will:

  • fork
  • clone
  • edit the files
  • submit a PR

for you!


  • update all the package's of your ORG with the new greenkeeper.ignore
  • add the new support field in your package.json
  • update the LICENSE of your repos
  • all the things that are boring and need to be done to all your repos!!


$ npm install -g massive-wax
$ massive-wax COMMAND
running command...
$ massive-wax (-v|--version|version)
massive-wax/1.0.0 win32-x64 node-v10.11.0
$ massive-wax --help [COMMAND]
  $ massive-wax COMMAND


massive-wax help [COMMAND]

display help for massive-wax

  $ massive-wax help [COMMAND]

  COMMAND  command to show help for

  --all  see all commands in CLI

See code: @oclif/plugin-help

massive-wax upgrade

Process the files of many GitHub repositories as you want and open PR with changes!

  $ massive-wax upgrade

  -B, --pr-body=pr-body                [default: This is an automatic PR created with
                                       [massive-wax](!] the body message of the PR

  -C, --[no-]commit                    commit the changes

  -F, --[no-]fork                      fork the project before cloning. Useful if you don't have the write grant

  -K, --token=token                    the GitHub token to fork the project and push the changes. You can set it via env
                                       named GITHUB_TOKEN

  -L, --[no-]clone                     clone the repo before executing the processors

  -R, --[no-]pr                        open the PR to forked repo

  -b, --branch=branch                  [default: wax] the branch name where apply the changes

  -c, --commit-message=commit-message  [default: wax in action] the commit message

  -m, --match=match                    [default: .js$|.json$] the files that match this pattern will be processed

  -p, --processor=processor            (required) the processor(s) that will modify the cloned repo. It must be a node

  -r, --repo=repo                      (required) the URL repo to upgrade. If it is a file, each line of the file must
                                       be a repo URL

  -t, --pr-title=pr-title              [default: automatic PR] the title of the PR

  -w, --work-path=work-path            [default: C:\Users\behem\workspace\massive-wax] current working directory: where
                                       cloning the repos

  This command will:
  - fork the repos in the GH account associated with the --token
  - clone the repos in your local env
  - process all the files of the cloned repos
  - commit the changes in a dedicated branch
  - open a PR to the master branch in the origin repo

  All these steps are optionals.

  Change all the LICENCE file of your org
    $ upgrade -K GITHUB-TOKEN --fork -p='./toMit.js' -t='Changed license' -c='chore changed license' -b licensebranch -r 

See code: src\commands\upgrade.js


The processor file will be loaded relative to the PWD and it must be like this scaffolding:

module.exports = function factory (args, logger) {
  // This function will be called for each REPO you are processing

  return {
    onRepo (repo) {
      // OPTIONAL, sync function called before processing the files
    onFile (file) {
      // MANDATORY, do what you whant to each file of your project.
      // The files are processed sequentially and, if you return a promise
      // it will be waited.
      // If you will throw an error, it will be logged but all will continue
    onComplete (repo) {
      // OPTIONAL, sync function called after all the processed files


Copyright Manuel Spigolon, Licensed under MIT.

Current Tags

  • 1.0.0                                ...           latest (5 months ago)

1 Versions

  • 1.0.0                                ...           5 months ago
Maintainers (1)
Today 0
This Week 1
This Month 1
Last Day 0
Last Week 0
Last Month 3
Dependencies (8)
Dev Dependencies (6)
Dependents (0)

Copyright 2014 - 2016 © |