Where Does act Read Config and Workflows?
act reads default flags from .actrc files in the repo or home directory, with workflows under .github.
Last updated
act configuration lives in dotfiles, not a central store. Repo-level .actrc sets project defaults such as runner images. Home-level .actrc sets personal defaults across projects.
Workflows themselves live under .github and belong to the repository. Secrets pass through flags or env files, never through .actrc. That separation keeps shared configs safe to commit.
Where act stores this, by platform
./.actrc (plus ~/.actrc for personal defaults)
Repo defaults for shared flags like runner images. Commit it with the project. CLI flags override file contents.
./.actrc (plus ~/.actrc for personal defaults)
Same lookup on Mac. Homebrew installs behave identically. Docker-backed runs need no extra local state beyond these files.
.\.actrc (plus ~\.actrc for personal defaults)
Same files on Windows runners. Secrets belong in env files or flags, never in committed .actrc. GITHUB_TOKEN handling stays manual.
Frequently asked questions
Where should act flags live?
Commit ./.actrc with the repo for shared defaults like runner images. Keep personal flags in ~/.actrc instead. Command-line flags override both files.
Do both .actrc files apply?
Yes, and the lookup order matters. Repo .actrc applies first, then home .actrc, then CLI flags. Newer builds also honor the XDG config path on some systems.
Notice an outdated path? Let us know.