feat: comment on pull requests with the next version of the software, if it deploys #300
tests.yml
on: pull_request
test
12s
test-it-runs
11s
Annotations
8 errors and 2 warnings
test
When trying to parse the GitHub Actions input value for analyze_commits_config, I encountered an error: SyntaxError: Unexpected token 'i', "invalid-json" is not valid JSON
|
test
The value I tried to parse was: invalid-json
|
test
When trying to parse the GitHub Actions input value for analyze_commits_config, I encountered an error: SyntaxError: Expected property name or '}' in JSON at position 8 (line 2 column 7)
|
test
The value I tried to parse was: {
|
test
Deploy command, echo 'hello world', failed with error code: 1
|
test
I will stop the deployment process now. Review the logs to see if this is an issue you need to fix before you retry the deployment again. Otherwise, simply retry running the deployment again later.
|
test
Deploy command, echo 'hello world', failed with error code: 1
|
test
I will stop the deployment process now. Review the logs to see if this is an issue you need to fix before you retry the deployment again. Otherwise, simply retry running the deployment again later.
|
test-it-runs
The `set-output` 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/
|
test-it-runs
The `set-output` 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/
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
junit-results
|
2.67 KB |
|