About `update-tic.yml` about gsodr HOT 12 CLOSED

I think this is finally fixed, here and on a couple other repositories where I’ve tried it. Will wait another 24hrs to be sure and then close this.

from gsodr.

All good! No error messages today. Thanks for your assistance, @pat-s.

from gsodr.

Right, thanks for that. I had a feeling I was missing something here but got sidetracked and didn't investigate further.

from gsodr.

Hi Adam, just wondering if something is still unclear since the update-tic action is still erroring due to the lack of the secret?

from gsodr.

Is it? I thought it all ran fine.

tic::gha_add_secret(<secret>, "TIC_UPDATE")

Where <secret> was my GH PAT with a "workflow" scope. So, yes, I guess something wasn't clear to me because I thought it was working now. 😕

from gsodr.

Ah, I fixed a different issue that I was having. Dang.

OK, no, it's not clear. Sorry, I don't understand what needs to be done here.

from gsodr.

The PR creation fails because you renamed your default branch from master to main: https://github.com/ropensci/GSODR/runs/974227217?check_suite_focus=true#step:6:100

Maybe updating the action helps (just run tic::use_update_tic()) again. If not, you need to set the new default branch name in the "create-pull-request" action manually.

from gsodr.

from gsodr.

OK, I just feel dumb. I know that the YAML, update-tic.yml, specifies "main" not "master" but it's still failing when I trigger a build.

I thought that I had even updated that before I even ran tic::use_update_tic() just now, but now I know for sure that I've done both and it still fails.

from gsodr.

I do not see it failing. Note that the action is only run once a day in cron job. Where do you see it failing?

LGTM on the first look.

from gsodr.

from gsodr.

You triggered a run for your main branch. This will not trigger a run for the update-tic YAML. The latter is configured CRON-only.

Let's wait for tmrw. Chances are that everything will just work then ;)

from gsodr.