#ACTS IN FILR HOW TO#
#ACTS IN FILR INSTALL#

gitignore should be copied into container (default true) use-gitignore Controls whether paths specified in. secret-file string file with list of secrets to read from (e.g. s, -secret stringArray secret to make available to actions with optional value (e.g. rm automatically remove container(s)/volume(s) after a workflow(s) failure r, -reuse don't remove container(s) on successfully completed workflow(s) to maintain state between runs rebuild rebuild local action docker image(s) even if already present q, -quiet disable logging of output from steps p, -pull pull docker image(s) even if already present P, -platform stringArray custom image to use per platform (e.g. no-recurse Flag to disable running workflows from subdirectories of specified path in '-workflows'/'-W' flag insecure-secrets NOT RECOMMENDED! Doesn't hide secrets while printing logs. Don't use this if you are not using GitHub Enterprise Server.

github-instance string GitHub instance to use. e, -eventpath string path to event JSON file env-file string environment file to read and use as env in the containers (default '.env') env stringArray env to make available to actions with optional value (e.g. C, -directory string working directory (default '.') detect-event Use first event type from workflow as event that triggered the workflow defaultbranch string the name of the main branch container-daemon-socket string Path to Docker daemon socket which will be mounted to containers (default '/var/run/docker.sock') container-cap-drop stringArray kernel capabilities to remove from the workflow containers (e.g. container-cap-add stringArray kernel capabilities to add to the workflow containers (e.g. Ignored on earlier Docker server platforms. Requires Docker server API Version 1.41+.

If not specified, will use host default architecture. container-architecture string Architecture which should be used to run containers, e.g.: linux/amd64. b, -bind bind working directory to container, rather than copy artifact-server-port string Defines the port where the artifact server listens (will only bind to localhost). If not specified the artifact server will not start. artifact-server-path string Defines the path where the artifact server stores uploads and retrieves downloads from. replace-ghe-action-token-with-github-com If you are using replace-ghe-action-with-github-com and you want to use private actions on GitHub, you have to set personal access token replace-ghe-action-with-github-com=github/super-linter) replace-ghe-action-with-github-com If you are using GitHub Enterprise Server and allow specified actions from GitHub (), you can set actions on this.

a, -actor string user that triggered the event (default 'nektos/act') Installation through package managers Homebrew (Linux/macOS)

#ACTS IN FILR INSTALL#

If you are using Linux, you will need to install Docker Engine.Īct is currently not supported with podman or other container backends (it might work, but it's not guaranteed). If you are using Windows, please follow steps for installing Docker Desktop on Windows.

#ACTS IN FILR HOW TO#

If you are using macOS, please be sure to follow the steps outlined in Docker Docs for how to install Docker Desktop for Mac. Installation Necessary prerequisites for running act Let's see it in action with a sample repo! The environment variables and filesystem are all configured to match what GitHub provides. Once it has the execution path, it then uses the Docker API to run containers for each action based on the images prepared earlier. 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. github/workflows/ and determines the set of actions that need to be run. When you run act it reads in your GitHub Actions from. github/workflows/ to replace your Makefile! With act, you can use the GitHub Actions defined in your.

github/workflows/ files (or for any changes to embedded GitHub actions), you can use act to run the actions locally.

Fast Feedback - Rather than having to commit/push every time you want to test out the changes you are making to your.

Run your GitHub Actions locally! Why would you want to do this? Two reasons:

Acts in filr