repo-file-sync-action
repo-file-sync-action copied to clipboard
Problem setting git username/email with GH_PAT only
🐞 Describe the bug
Our sync action stopped working ~5 days ago (seemingly after this was merged - https://github.com/BetaHuhn/repo-file-sync-action/pull/153). Throwing an error that the git username/email was missing.
We're passing only a GH_PAT
, not an installation token.
🖼️ Screenshots
See last working run: https://github.com/nextauthjs/next-auth/actions/runs/1809749953 Failing run: https://github.com/nextauthjs/next-auth/actions/runs/1815281481
📋 Additional context
Sync action: https://github.com/nextauthjs/next-auth/blob/main/.github/workflows/sync-example.yml Sync config: https://github.com/nextauthjs/next-auth/blob/main/.github/sync.yml
Hi @ndom91, thanks for reporting this!
I will take a look and get this fixed asap.
I can't seem to reproduce your issue. I tried running the action with only the GH_PAT and it is working without any errors (see the test run).
Could you enable the step debug logging by setting the ACTIONS_STEP_DEBUG
secret to true and try again? It should print that it is setting the git username and email.
I can't seem to reproduce your issue. I tried running the action with only the GH_PAT and it is working without any errors (see the test run).
Could you enable the step debug logging by setting the
ACTIONS_STEP_DEBUG
secret to true and try again? It should print that it is setting the git username and email.
Thanks for taking a look! We'll give that a try and get back to you.
Cc: @balazsorban44
Yes, we can try that.
I got 404 on your test run, by the way. Is it a hidden repository you link to?
FWIW, pinning down to the previous version worked:
https://github.com/nextauthjs/next-auth/actions/runs/1838645699
https://github.com/nextauthjs/next-auth/commit/1c2b57393396b9a7611cea38d2ca087d411c5bd6
I got 404 on your test run, by the way. Is it a hidden repository you link to?
Whoops, yeah it was set to private. Fixed now.
Just checking in, is the issue still coming up? @balazsorban44 @ndom91
Closing this for now. Please reopen it if the issue persists.
I'm experiencing this issue on latest
Also experiencing this issue on latest, using GH_PAT
only with the same error message.
I'm experiencing this issue on latest as of 10/23/2022