GitHub Action to validate Elm code is formatted correctly
Go to file
2020-04-20 20:00:57 +01:00
__tests__ Initial commit 2020-04-20 18:11:39 +01:00
.github/workflows Switch to Yarn 2020-04-20 18:26:05 +01:00
dist Switch to Yarn 2020-04-20 18:26:05 +01:00
src Initial commit 2020-04-20 18:11:39 +01:00
.eslintignore Initial commit 2020-04-20 18:11:39 +01:00
.eslintrc.json Initial commit 2020-04-20 18:11:39 +01:00
.gitignore Initial commit 2020-04-20 18:11:39 +01:00
.prettierignore Initial commit 2020-04-20 18:11:39 +01:00
.prettierrc.json Initial commit 2020-04-20 18:11:39 +01:00
action.yml Initial commit 2020-04-20 18:11:39 +01:00
jest.config.js Initial commit 2020-04-20 18:11:39 +01:00
LICENSE Initial commit 2020-04-20 18:11:39 +01:00
package.json Upgrade ncc 2020-04-20 19:59:43 +01:00
README.md Update README 2020-04-20 18:26:07 +01:00
tsconfig.json Initial commit 2020-04-20 18:11:39 +01:00
yarn.lock Upgrade @types/node 2020-04-20 20:00:57 +01:00

typescript-action status

Create a JavaScript Action using TypeScript

Use this template to bootstrap the creation of a JavaScript action.🚀

This template includes compilication support, tests, a validation workflow, publishing, and versioning guidance.

If you are new, there's also a simpler introduction. See the Hello World JavaScript Action

Create an action from this template

Click the Use this Template and provide the new repo details for your action

Code in Master

Install the dependencies

$ yarn

Build the typescript and package it for distribution

$ yarn run build && yarn run pack

Run the tests ✔️

$ yarn test

 PASS  ./index.test.js
  ✓ throws invalid number (3ms)wait 500 ms (504ms)test runs (95ms)

...

Change action.yml

The action.yml contains defines the inputs and output for your action.

Update the action.yml with your name, description, inputs and outputs for your action.

See the documentation

Change the Code

Most toolkit and CI/CD operations involve async operations so the action is run in an async function.

import * as core from '@actions/core';
...

async function run() {
  try { 
      ...
  } 
  catch (error) {
    core.setFailed(error.message);
  }
}

run()

See the toolkit documentation for the various packages.

Publish to a distribution branch

Actions are run from GitHub repos so we will checkin the packed dist folder.

Then run ncc and push the results:

$ yarn run pack
$ git add dist
$ git commit -a -m "prod dependencies"
$ git push origin releases/v1

Your action is now published! 🚀

See the versioning documentation

Validate

You can now validate the action by referencing ./ in a workflow in your repo (see test.yml])

uses: ./
with:
  milliseconds: 1000

See the actions tab for runs of this action! 🚀

Usage:

After testing you can create a v1 tag to reference the stable and latest V1 action