Skip to content
.github/workflows/pull_request.yml

⚙️ Change GitHub Action to Push to GHCR #1

Sign in to view logs

⚙️ Change GitHub Action to Push to GHCR

⚙️ Change GitHub Action to Push to GHCR #1

Triggered via pull request December 7, 2023 23:54
@nerajchandnerajchand
opened #5
fix/update-github-actions-to-push-to-ghcr
Status Success
Total duration 1m 25s
Artifacts –

pull_request.yml

on: pull_request
pre-commit
21s
pre-commit
test-integration
1m 15s
test-integration
test-frontend
16s
test-frontend
Matrix: test-unit
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
test-frontend
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
pre-commit
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test-unit (3.7.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test-unit (3.8.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/