Skip to content

Cron

Cron #1809

Triggered via schedule September 17, 2024 08:18
Status Failure
Total duration 12m 4s
Artifacts

cron.yml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
crawl
{"command":"git push origin HEAD","exitCode":1,"outputData":"","errorData":"error: The destination you provided is not a full refname (i.e.,\nstarting with \"refs/\"). We tried to guess what you meant by:\n\n- Looking for a ref that matches 'HEAD' on the remote side.\n- Checking if the <src> being pushed ('HEAD')\n is a ref in \"refs/{heads,tags}/\". If so we add a corresponding\n refs/{heads,tags}/ prefix on the remote side.\n\nNeither worked, so we gave up. You must fully qualify the ref.\nhint: The <src> part of the refspec is a commit object.\nhint: Did you mean to create a new branch by pushing to\nhint: 'HEAD:refs/heads/HEAD'?\nerror: failed to push some refs to 'https://github.com/City-Bureau/city-scrapers.git'\n"}
crawl
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v1, dschep/install-pipenv-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
crawl
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v1, dschep/install-pipenv-action@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/