* feat: log parsed command data in json logger
* Could be used to upload the GITHUB_STEP_SUMMARY by downstream Projects
* You can see the summary and other commands
* Access the raw line of most commands
* Update step.go
* Update step.go
* Update push.yml
* .
---------
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
* feat: Support graceful job step cancellation
* for gh-act-runner
* act-cli support as well
* respecting always() and cancelled() of steps
* change main
* cancel startContainer / gh cli / bugreport early
* add to watch as well
---------
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
E.g. if GoGitAction Cache had a fetch failure this error did not trigger report jobResult Failure.
Also the error has been not printed until the last message before exit of act.
* adds tests for both corner cases
* Report the elapsed time for each workflow step
The `runStepExecutor` was extended to track and report the execution time of the step.
This applies both to the standard and JSON log format.
Please, note that:
- on the standard log the time format depends on the value (e.g. `3.038334954s` or `2m0.054014069s`)
- on the JSON log the time format is nanoseconds
* Added the `executionTime` report also to failing steps
* parse_env_file discard utf8 bom
* powershell 5 may add the BOM even when explicitly using utf8
* add test + apply to GITHUB_PATH as well
* fix it
* fix powershel 5 syntax
* misc
* fixup
* fix wrong subaction
---------
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
* chore: upgrade dependencies
* fix: linter errors
* chore: bump version of golangci-lint
* chore: go mod tidy
* fix: failing test
* fix: update version of upload-artifact to v4
* chore: format test output with gotestfmt
* fix: typo in test exec
* fix: failing tests
* fix: windows unit test execution
* fix: windows unit test execution
* fix: whitespace
* fix: tests with validation errors were skipped
* fixup
* [no ci] fix one test
* fix some tests
* fix last test
---------
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
* bash without "-o pipefail" option when "bash" is not explicitely
defined in the workflow
* bonus: fix inverted expected and actual in TestGetGitHubContext assertions
* fix: make node tool non volatile
Currently downgrading node via setup-node can break later actions
* fix it and lookup on startup
* fix problems
---------
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
* fix: Implement missing health ceck for Services
* Add test case
* linter doesn't support min builtin and fix check
---------
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
* fix: skip service container for empty image
It is used to skip empty image name in services which is the only way to handle condition services in github action currently https://github.com/actions/runner/issues/822
* test: add testdata for empty image in services
* fix: add missing test call
* fix: wring test call
* fix: invalid without expression
---------
Co-authored-by: ChristopherHX <christopher.homberger@web.de>
* fix: composite action input pollution
* fix run steps
* fix missing defaults in post after env cleanup
* fix test to make more sense
* Add tests and simplify change
---------
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
* Actions Artifacts v4 backend
* lint
* fix it now
* remove protofile, to make linter not complain
* sync changes
* add delete
* import auth test from gitea
* add more tests
* codecov ignore protobuf
The toolcache on GitHub Actions need to be in
/opt/hostedtoolcache. This is the case for all
environment variables set by act, but it's not the
case for the volume mounted into the container.
Co-authored-by: Björn Brauer <zaubernerd@zaubernerd.de>
Co-authored-by: ChristopherHX <christopher.homberger@web.de>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
- include repoURL and repoRef in error
- map NoErrAlreadyUptodate to `couldn't find remote ref` for branchOrtag
fetch request
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Move the logging back up a level to fix a minor logging issue introduced in #2088
`RunContext`s for composite actions have dummy/blank `Job`s with no `runs-on`,
meaning their calls to `withGithubEnv` would result in an inaccurate log message
complaining that `'runs-on' key not defined in ...`
Co-authored-by: Jason Song <i@wolfogre.com>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
