GitHub Local Actions

Run your GitHub Actions locally with the power of the GitHub Local Actions Visual Studio Code extension! Say goodbye to the hassle of committing and pushing changes every time you need to test a workflow. This extension lets you quickly and efficiently run your workflows locally, leveraging the nektos/act CLI tool. Enjoy a seamless experience with an interface designed to feel as familiar as the official GitHub Actions extension.

• 🚀 Run Workflows/Jobs: Run entire workflows or specific jobs locally without leaving your editor.
• ⚡ Trigger Events: Trigger standard GitHub events to run multiple workflows.
• 📖 View Workflow Run History: Track and investigate past workflow logs.
• ⚙️ Manage Workflow Settings: Define secrets, variables, inputs, runners, payloads, and options for execution.

✨ Documentation site is now live here!

Components

The Components view is where you can manage the components for using the extension.

• nektos/act provides the core functionality for running GitHub Actions locally. Whenever a workflow, job, or event is triggered, the extension is essentially building up an act command and executing it as a VS Code task.

• Docker Engine is required for nektos/act if you plan to run workflows in containers. The containers are configured to mirror GitHub's environment, including matching environment variables and filesystems, ensuring a consistent and reliable local execution.

  If you do not require container isolation, you can run selected (e.g. Windows or MacOS) workflow jobs directly on your system. In this case, you do not need to have docker installed or running. Click here to learn how to use your host system as your runner.

Workflows

The Workflows view is where you can manage and run workflows locally. You have several options to execute a workflow:

1. Run All Workflows: Run all workflows in the workspace.
2. Run Single Workflow: Run a single workflow in the workspace.
3. Run Job: Run a specific job in a workflow.
4. Run Event: Run multiple workflows using a GitHub event.
5. Run Workflow Event: Run a specific event on a workflow.
6. Run Job Event: Run a specific event on a job.

History

The History view is where you can browse and manage workflows currently being executed as well as review logs from previous workflow runs.

Settings

The Settings view is where you can configure various settings to be used when executing workflows.

• Secrets: Configure sensitive information used in workflows.
• Variables: Define workflow variables and import from GitHub.
• Inputs: Assign input values for workflow runs.
• Runners: Customize runners for executing workflows.
• Paylods: Configure payloads that define event properties.
• Options: Define additional act options related to cache, artifacts, containers, etc.

Bugs and Feature Requests

If you encounter any issues or have feature requests specific to GitHub Local Actions, please feel free to open an issue or post on the discussion board.

🚨 For any bugs or feature requests related to nektos/act specifically, please open an issue on the nektos/act repository.

Contribution

Contributions are always welcome! Please see our contributing guide for more details.

Maintainers

• @SanjulaGanepola