Skip to content

feat: optional readiness probe configuration #129

feat: optional readiness probe configuration

feat: optional readiness probe configuration #129

Triggered via pull request November 8, 2024 17:35
@jkerryjkerry
closed #95
Status Success
Total duration 25s
Artifacts

create-jira-issue.yml

on: pull_request_target
call-workflow  /  Jira sync
16s
call-workflow / Jira sync
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
call-workflow / Jira sync
The following actions use a deprecated Node.js version and will be forced to run on node20: atlassian/gajira-login@45fd029b9f1d6d8926c6f04175aa80c0e42c9026, atlassian/gajira-transition@38fc9cd61b03d6a53dd35fcccda172fe04b36de3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
call-workflow / Jira sync
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/
call-workflow / Jira sync
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/