500 on Actions page #1760

Comment

Hello everyone!

I am currently helping the backintime project to migrate to Codeberg. My task is to migrate the CI config to Forgejo Actions in order to prepare the move.

So I created a new project and pushed the code, its available at https://codeberg.org/gcrkrause/backintime

Since I want to look into actions, I enabled actions and visited https://codeberg.org/gcrkrause/backintime/actions, but it throws a 500 error page.

I cannot reproduce this on my own instance running Forgejo Version 9.0.1+gitea-1.22.0

Let me know if you need any more information.

@fnetX If this is a bug in Forgejo, is there already a report I can follow or should I report the issue to Forgejo?

Not yet. I just looked up the exact error message:

GetBranchCommit, object does not exist [id: refs/heads/main, rel_path: ]

Note that not only "Actions" is broken, but https://codeberg.org/gcrkrause/backintime/activity

GetActivityStats, FillFromGit: Failed to get GetCodeActivityStats for repository.
Error: exit status 128
Stderr: fatal: ambiguous argument 'main': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

Hmm, I think the issue is that the default branch is set to "main", but main does not exist (any more)?

@fnetX Your error message was something that got me a hint:

I used the default for the default branch, which is main. Then I pushed the code from the upstream repository. But the default branch there is dev. So a main branch just simply does not exist. I changed the default branch and now everything is working.

However, I think this should be handled more gracefully by Forgejo.

Yes, I completely agree. Did the main branch ever exist (e.g. on repo creation) and was removed, or did it never actually exist?

@fnetX it never existed, because I created an empty project and pushed only the develop branch I pulled from Github before.