You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi folks, quick question please (sorry I got rid of the Issue template - too much faff for such a simple question): we are using the codacy cov uploader via CircleCI as orb ie:
and noticed that the coverage upload is not skipped if the PR is from a forked repo (so the project API token is missing there), and fails with the obvious "project token missing" - do we have to explicitly have the --skip option turned on to allow for a skip in this case, and avoid a fail? Many thanks in advance! Cheers muchly 🍻
The text was updated successfully, but these errors were encountered:
@lolgab my apologies, mate - proves out were were indeed skipping with skip: true (my colleague @bouweandela looked a few lines down the config file, unlike me 🤣 ) - and still, the upload was tried and failed, but only after one merged main in the fork PR-ed branch, otherwise, before that, the upload was indeed skipped on the fork - any ideas? No rush, no major issue here, it's more like a curiosity 🔍
Hi folks, quick question please (sorry I got rid of the Issue template - too much faff for such a simple question): we are using the codacy cov uploader via CircleCI as orb ie:
and noticed that the coverage upload is not skipped if the PR is from a forked repo (so the project API token is missing there), and fails with the obvious "project token missing" - do we have to explicitly have the
--skip
option turned on to allow for a skip in this case, and avoid a fail? Many thanks in advance! Cheers muchly 🍻The text was updated successfully, but these errors were encountered: