Skip to content

Failed: HTTP status code 200 is returned #185

Failed: HTTP status code 200 is returned

Failed: HTTP status code 200 is returned #185

Triggered via issue November 7, 2023 13:20
Status Success
Total duration 25s
Artifacts

labeled_issue.yml

on: issues
Move "under development" issues
6s
Move "under development" issues
Move "ready for testings" issues
9s
Move "ready for testings" issues
Move "solved" issues
11s
Move "solved" issues
Move "deployed in reference validator" issues
11s
Move "deployed in reference validator" issues
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Move "under development" issues
The following actions uses node12 which is deprecated and will be forced to run on node16: konradpabjan/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Move "ready for testings" issues
The following actions uses node12 which is deprecated and will be forced to run on node16: konradpabjan/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Move "solved" issues
The following actions uses node12 which is deprecated and will be forced to run on node16: konradpabjan/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Move "deployed in reference validator" issues
The following actions uses node12 which is deprecated and will be forced to run on node16: konradpabjan/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/