Repository files navigation

Navigate to subdirectories for more information about particular Actions.

Every directory (exceptnode_modules) is a separate Action.

In Actions' subdirectories, there are no separatenode_modules directories orpackage-lock.json files.That's because we try to maintain one top-level dependency stack for all Actions together.To add a new dependency (because some Action requires it), runnpm install in root directory of this repository.To update dependencies for all Actions at once, one needs to simply runnpm upgrade, while being in root directory of this repository too.

Workflow names match Actions' directory names, for consistency.Particular workflow to test an Action is run only when this Action's directory contents or workflow file are changed.In addition to that, all test workflows will run ifpackage.json orpackage-lock.json files ornode_modules directory are changed.

Please be careful not to start multiple workflow jobs testing the same Action at once, as it may cause a failure, because of the way some Actions are tested.

To test an action locally, first runnpm install in the root of this repository, then in the directory of your action, runnode main.js. Input variables are specified through the environment. For example, if an Action needed apull_request input, runningexport INPUT_PULL_REQUEST=1234 would pass that input to the Node.js script. For Actions that need variables from theGitHub Events API, you'll need to save (or construct) the appropriate JSON file, then setGITHUB_EVENT_PATH to the file's location.