actions/checkout failing to fetch repository #2311

Tobiky commented 2026年01月14日 15:51:12 +01:00

Comment

Hey, I'm having issues with using the checkout action as the title suggest. Context:

• Repo/Runner: https://codeberg.org/Tobiky/Cyberpunk-Slang/actions/runs/1/jobs/0
  • Should be public but if inaccessible (still learning the platform) I have attached the logs
• Command failing in runner succeeds locally

  [command]/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules --depth=1 origin +68db6f1447f696394d68f6fa6ad7fe1f8bcc9b7d2c13d37afc1695941333c67f:refs/tags/v0.0.0
  fatal: couldn't find remote ref 68db6f1447f696394d68f6fa6ad7fe1f8bcc9b7d2c13d37afc1695941333c67f
  The process '/usr/bin/git' failed with exit code 128
  

• Tried rerunning in case of temporary error but same error/output

I'm not really sure why its failing. It's the first step in the job pipeline so there's not much of my input that could cause this to err. There is no issue here, on forgejo, or the github original that mentions this problem for the active version, as far as I could find.

Any ideas on what the problem is/could be?

Thanks!

### Comment Hey, I'm having issues with using the `checkout` action as the title suggest. Context: - Repo/Runner: https://codeberg.org/Tobiky/Cyberpunk-Slang/actions/runs/1/jobs/0 - Should be public but if inaccessible (still learning the platform) I have attached the logs - Command failing in runner succeeds locally ```none [command]/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules --depth=1 origin +68db6f1447f696394d68f6fa6ad7fe1f8bcc9b7d2c13d37afc1695941333c67f:refs/tags/v0.0.0 fatal: couldn't find remote ref 68db6f1447f696394d68f6fa6ad7fe1f8bcc9b7d2c13d37afc1695941333c67f The process '/usr/bin/git' failed with exit code 128 ``` - Tried rerunning in case of temporary error but same error/output I'm not really sure why its failing. It's the first step in the job pipeline so there's not much of my input that could cause this to err. There is no issue here, on forgejo, or the github original that mentions this problem for the active version, as far as I could find. Any ideas on what the problem is/could be? Thanks!

Gusted commented 2026年01月14日 15:57:31 +01:00

This is a known problem and is tracked in https://code.forgejo.org/forgejo/forgejo-actions-feature-requests/issues/64. It's due to the fact you are using SHA256.

This is a known problem and is tracked in https://code.forgejo.org/forgejo/forgejo-actions-feature-requests/issues/64. It's due to the fact you are using SHA256.

Tobiky commented 2026年01月14日 16:02:34 +01:00

Oh my, thank you for the quick reply! Sorry for missing such an obvious relation to my problem. Is there a way for me to change this setting without recreating the repository?

Oh my, thank you for the quick reply! Sorry for missing such an obvious relation to my problem. Is there a way for me to change this setting without recreating the repository?

Tobiky commented 2026年01月14日 16:58:14 +01:00

Ended up recreating the repo and converted history via fast-import/export. Thanks for all the help!

Ended up recreating the repo and converted history via fast-import/export. Thanks for all the help!