843cd94cc2
* Add github action to codespell master on push and PRs
* Add codespell config with few custom skips
* [DATALAD RUNCMD] Do interactive fixing of leftover ambigous typos
=== Do not change lines below ===
{
"chain": [],
"cmd": "codespell -w -i 3 -C 2 ./pkg/common/git/git.go",
"exit": 0,
"extra_inputs": [],
"inputs": [],
"outputs": [],
"pwd": "."
}
^^^ Do not change lines above ^^^
* exclude pkg/runner/hashfiles/index.js
* [DATALAD RUNCMD] run codespell throughout fixing typos automagically
=== Do not change lines below ===
{
"chain": [],
"cmd": "codespell -w",
"exit": 0,
"extra_inputs": [],
"inputs": [],
"outputs": [],
"pwd": "."
}
^^^ Do not change lines above ^^^
---------
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
|
||
|---|---|---|
| .github | ||
| .vscode | ||
| cmd | ||
| pkg | ||
| .actrc | ||
| .codespellrc | ||
| .editorconfig | ||
| .gitignore | ||
| .gitleaksignore | ||
| .golangci.yml | ||
| .goreleaser.yml | ||
| .markdownlint.yml | ||
| .mega-linter.yml | ||
| .mergify.yml | ||
| .prettierignore | ||
| .prettierrc.yml | ||
| CODEOWNERS | ||
| CONTRIBUTING.md | ||
| IMAGES.md | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| VERIFICATION | ||
| VERSION | ||
| act-cli.nuspec | ||
| codecov.yml | ||
| go.mod | ||
| go.sum | ||
| install.sh | ||
| main.go | ||
README.md
Overview 
"Think globally,
actlocally"
Run your GitHub Actions locally! Why would you want to do this? Two reasons:
- Fast Feedback - Rather than having to commit/push every time you want to test out the changes you are making to your
.github/workflows/files (or for any changes to embedded GitHub actions), you can useactto run the actions locally. The environment variables and filesystem are all configured to match what GitHub provides. - Local Task Runner - I love make. However, I also hate repeating myself. With
act, you can use the GitHub Actions defined in your.github/workflows/to replace yourMakefile!
How Does It Work?
When you run act it reads in your GitHub Actions from .github/workflows/ and determines the set of actions that need to be run. It uses the Docker API to either pull or build the necessary images, as defined in your workflow files and finally determines the execution path based on the dependencies that were defined. Once it has the execution path, it then uses the Docker API to run containers for each action based on the images prepared earlier. The environment variables and filesystem are all configured to match what GitHub provides.
Let's see it in action with a sample repo!
Act User Guide
Please look at the act user guide for more documentation.
Support
Need help? Ask on Gitter!
Contributing
Want to contribute to act? Awesome! Check out the contributing guidelines to get involved.
Manually building from source
- Install Go tools 1.20+ - (https://golang.org/doc/install)
- Clone this repo
git clone git@github.com:nektos/act.git - Run unit tests with
make test - Build and install:
make install