fix: do not consider the runs(for replay) that cant be created with c… #334
publish-latest.yml
on: push
verify
/
lint
1m 18s
verify
/
unit-test
3m 38s
verify
/
integration-test
2m 19s
documentation
1m 0s
publish-latest
6m 53s
Annotations
5 warnings
|
verify / lint
Unexpected input(s) 'skip-go-installation', valid inputs are ['version', 'install-mode', 'working-directory', 'github-token', 'verify', 'only-new-issues', 'skip-cache', 'skip-save-cache', 'problem-matchers', 'args', 'cache-invalidation-interval']
|
|
verify / lint
Unexpected input(s) 'skip-go-installation', valid inputs are ['version', 'install-mode', 'working-directory', 'github-token', 'verify', 'only-new-issues', 'skip-cache', 'skip-save-cache', 'problem-matchers', 'args', 'cache-invalidation-interval']
|
|
publish-latest
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
publish-latest
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
publish-latest
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|