Skip to content
staging-pipeline

add notifications for Qacc #80

Sign in to view logs

add notifications for Qacc

add notifications for Qacc #80

Triggered via pull request August 20, 2024 01:17
@ae2079ae2079
synchronize #22
QaccNotifications
Status Failure
Total duration 2m 27s
Artifacts –

staging-pipeline.yml

on: pull_request
Run linters
47s
Run linters
test
1m 18s
test
publish
0s
publish
deploy
0s
deploy
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
test: src/adapters/notifications/NotificationCenterAdapter.ts#L31
'dappUrl' is assigned a value but never used
test
Process completed with exit code 1.
Run linters
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/
Run linters
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v1, wearerequired/lint-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test
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/
test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/