2019-09-11 02:25:29 -04:00
# Create a JavaScript Action
2019-09-11 02:21:19 -04:00
2019-09-11 02:25:29 -04:00
:rocket: Use this template to bootstrap the creation of a JavaScript action with tests, linting, a validation workflow and publishing.
2019-09-11 02:21:19 -04:00
2019-09-11 02:41:31 -04:00
This walk through takes you through creation, testing and publishing the action.
2019-09-11 02:21:19 -04:00
## Create an action from this template
Click the `Use this Template` and provide the new repo details for your action
## Code in Master
``` bash
$ npm install
```
``` bash
$ npm test
PASS ./index.test.js
✓ throws invalid number ( 3ms)
✓ wait 500 ms ( 504ms)
✓ test runs ( 95ms)
...
```
## Change actions.yml
The actions.yml contains defines the inputs and output for your action.
Update the actions.yml with your name, description, inputs and outputs for your action.
See the [documentation ](https://help.github.com/en/articles/metadata-syntax-for-github-actions )
## Change the Code
Most toolkit and CI/CD operations involve async operations so the action is run in an async function.
``` javascript
const core = require ( '@actions/core' ) ;
...
async function run ( ) {
try {
...
}
catch ( error ) {
core . setFailed ( error . message ) ;
}
}
run ( )
```
See the [toolkit documentation ](https://github.com/actions/toolkit/blob/master/README.md#packages ) for the various packages.
2019-09-11 02:32:20 -04:00
## Publish to a distribution branch
2019-09-11 02:41:31 -04:00
Actions are run from GitHub repos. We will create a releases branch and only checkin production modules (core in this case).
Comment out node_modules in .gitignore and create a releases/v1 branch
2019-09-11 02:32:20 -04:00
``` bash
# Dependency directories
# node_modules/
```
``` bash
$ git checkout -b releases/v1
2019-09-11 02:41:31 -04:00
$ git commit -a -m "prod dependencies"
2019-09-11 02:32:20 -04:00
```
``` bash
$ npm prune --production
2019-09-11 02:41:31 -04:00
$ git add node_modules/
$ git commit -a -m "prod dependencies"
$ git push origin releases/v1
```
See the [versioning documentation ](https://github.com/actions/toolkit/blob/master/docs/action-versioning.md )
## Validate
You can now validate the action by referencing the releases/v1 branch
``` yaml
uses : actions/javascript-action@releases/v1
with :
milliseconds : 1000
2019-09-11 02:32:20 -04:00
```
2019-09-11 02:21:19 -04:00
## Usage:
2019-09-11 02:41:31 -04:00
After testing you can [create a v1 tag ](https://github.com/actions/toolkit/blob/master/docs/action-versioning.md ) to reference the stable and tested action
2019-09-11 02:21:19 -04:00
``` yaml
uses : actions/javascript-action@v1
with :
milliseconds : 1000
```