1
0
Fork 0
 
 
 
Go to file
Bryan MacFarlane 571d130f50
Branching Strategy for Production Modules (#39)
* starting walkthrough docs
2019-08-03 12:15:05 -04:00
.github/workflows Update workflow.yml (#34) 2019-07-25 23:08:57 -04:00
docs Branching Strategy for Production Modules (#39) 2019-08-03 12:15:05 -04:00
packages Correct github interfaces 2019-08-02 15:25:51 -04:00
res add logo (#27) 2019-07-10 14:02:56 -04:00
scripts Simplify package creation 2019-04-22 11:54:05 -04:00
.eslintignore DRY up core tests 2019-05-21 11:23:35 -04:00
.eslintrc.json Add io (#5) 2019-05-22 16:05:34 -04:00
.gitignore Add io (#5) 2019-05-22 16:05:34 -04:00
.prettierignore Add .prettierignore 2019-05-21 10:11:44 -04:00
.prettierrc.json Add ESLint and Prettier tooling 2019-04-19 15:35:44 -04:00
LICENSE.md Add license files 2019-04-20 10:38:10 -04:00
README.md Create Actions Walkthrough (#36) 2019-08-01 11:26:17 -04:00
jest.config.js Add working Jest & TypeScript config 2019-04-19 15:15:34 -04:00
lerna.json Initialize a Lerna project 2019-04-19 14:29:24 -04:00
package-lock.json Add concurrently and check-all script 2019-05-21 10:43:05 -04:00
package.json v2 workflow (#30) 2019-07-11 16:12:50 -04:00
tsconfig.json Add ESLint 2019-05-21 10:34:23 -04:00

README.md

Toolkit

The toolkit provides a set of packages to make creating actions easier and drive consistency.

Packages

The toolkit provides four separate packages. Since actions are run by pulling actions from the github graph, dependencies including the packages are vendored into your action.

Package Description
@actions/core Core functions for getting inputs, setting outputs, setting results, logging, secrets and environment variables
@actions/exec Functions necessary for running tools on the command line
@actions/io Core functions for CLI filesystem scenarios
@actions/tool-cache Functions necessary for downloading and caching tools

Creating an Action with the Toolkit

Actions are units of work which can either run in a container or on the host machine.

Choosing an action type: Outlines the differences and why you would want to create a host or a container based action.

JavaScript Action Walthrough: Create an action which runs on the host using the toolkit

Docker Action Walkthrough: Create an action that is delivered as a container and run with docker.

Docker Action Walkthrough with Octokit: Create an action that is delivered as a container which uses the toolkit. This example uses the GitHub context to construct an Octokit client.

Versioning: Recommendations on versioning, releases and tagging your action.

Contributing

We welcome contributions. See how to contribute.