Skip to content
Comment issue on Jira

[TS-711] Wrong commit UUID is discovered #123

Sign in to view logs

[TS-711] Wrong commit UUID is discovered

[TS-711] Wrong commit UUID is discovered #123

Triggered via issue January 19, 2024 17:37
@SchoolGuySchoolGuy
commented on #78 cc07688
Status Success
Total duration 17s
Artifacts –

comment_issue.yml

on: issue_comment
jira
7s
jira
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
jira
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/github-script@v2.0.0, atlassian/gajira-login@v2.0.0, atlassian/gajira-comment@v2.0.2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
jira
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/
jira
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/
jira
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/