1
0
Fork 0
 
 
 
Go to file
Jonathan Leitschuh b529540e0c Don't recommend the use of HTTP to download code (#120) 2019-09-09 09:39:43 -04:00
.github/workflows Added unzip for darwin (#49) 2019-08-13 12:39:01 -04:00
docs added file name of action.yml file. When first starting out, everything is confusing and a first time actions creator might not know which file to update (#122) 2019-09-07 20:39:41 -04:00
packages Don't recommend the use of HTTP to download code (#120) 2019-09-09 09:39:43 -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 JavaScript walk through update (#107) 2019-09-04 17:30:45 -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 Bump TypeScript to 3.6.2 2019-09-05 10:03:10 -04:00
package.json Bump TypeScript to 3.6.2 2019-09-05 10:03:10 -04:00
tsconfig.json Add ESLint 2019-05-21 10:34:23 -04:00

README.md

GitHub Actions status

GitHub Actions Toolkit

The GitHub Actions ToolKit provides a set of packages to make creating actions easier and drive consistency.

Packages

The toolkit provides five separate packages. See the docs for each 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
@actions/github An Octokit client hydrated with the context that the current action is being run in

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 JavaScript or a container based action.

JavaScript Action Walkthrough using a Template: A full walkthrough creating an action using the toolkit along with TypeScript for compile time support and Jest for unit testing. It also covers a branching strategy for versioning and safely testing and releasing an action.

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.