Skip to content
Repo Automator

ci: Use GITHUB_OUTPUT envvar instead of set-output command #131

Sign in to view logs

ci: Use GITHUB_OUTPUT envvar instead of set-output command

ci: Use GITHUB_OUTPUT envvar instead of set-output command #131

Triggered via pull request July 5, 2024 10:50
@iamdharmeshiamdharmesh
synchronize #1178
develop
Status Failure
Total duration 12s
Artifacts –

repo-automator.yml

on: pull_request
Validate
2s
Validate
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 1 warning
Validate
HttpError: Resource not accessible by integration
Validate
Please fill out the changelog information
Validate
Please fill out the credits information
Validate
Please add some description about the changes made in PR
Validate
The following actions uses Node.js version which is deprecated and will be forced to run on node20: 10up/action-repo-automator@trunk. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/