Skip to content

Latest commit

 

History

History
79 lines (47 loc) · 1.84 KB

File metadata and controls

79 lines (47 loc) · 1.84 KB

Development

If you are interested in Action Development, these resources may help.

[[toc]]

 

Request Action

Unpublished Actions

These are actions I have not published. Some of which I use internally.

Template Actions

These are actions I use as starting points for creating new actions.

Get Started

Running Locally

The most important tool for developing actions is nektos/act.

Run from source

Instead of using a watcher you can change the runs: in your action.yml to your source file and run act with --use-gitignore=false so the node_modules folder is copied with your files.

act -j test --use-gitignore=false

Secrets, env, event

For secrets and environment variables you can just create a .secrets and .env file.

To customize the github event add an event.json file and run act with -e event.json.

act -j test -e event.json
event.json

This lets you skip workflow steps with this if: ${{ !github.event.act }}

{
  "act": true
}

Debug logging

The best way to see all log output is to enable RUNNER_DEBUG and show secrets.

Because of everything covered, this is the command I usually run.

act -j test -e event.json --use-gitignore=false --insecure-secrets --env RUNNER_DEBUG=1
<script setup> import actions from '../.vitepress/scripts/actions.js' </script>