Code
How nektos/act is laid out, and where to start for common changes.
There is no import map for this report yet.
Where to start reading
- Repository root
- Repository root
- Likely public API
- Suggested starting pointAI
- Suggested starting pointAI
- Suggested starting pointAI
- Suggested starting pointAI
- Suggested starting pointAI
Find files for a task
AIAdd support for a new action type
- Add type constant and factory case to pkg/runner/action.go
- Create action_<type>.go implementing the execution logic
- Add test coverage in pkg/runner/action_test.go
Add a new GitHub expression function
- Register function name in pkg/exprparser/functions.go register map
- Implement function logic and add test case
- Verify integration in pkg/exprparser/interpreter_test.go
Add Docker container configuration option
- Add option field to container type in pkg/container/container_types.go
- Apply option in pkg/container/docker_run.go RunContainer or docker_build.go
- Add test case in pkg/container/docker_run_test.go
Add workflow context variable or function
- Define field in context struct in pkg/model/github_context.go or pkg/model/job_context.go
- Populate value in pkg/common/context.go NewContext setup
- Add test coverage in pkg/model/github_context_test.go
Change the public API
Add or update tests
Change build or automation
RepoPilot lists up to 500 files, so a file missing here may still exist.
- Files marked “likely” are guessed from their names.