Unable to update repository invalid branch name, when branch name is valid.

[jnstockley]

Hi, I recently switched to forgejo instead of Gitea, and when I was moving my OpenTofu config from Gitea to forgejo, for a few of my repos I ran into this error

│ Error: Unable to update repository
│ 
│   with forgejo_repository.ece-scholarships,
│   on repos.tofu line 209, in resource "forgejo_repository" "ece-scholarships":
│  209: resource "forgejo_repository" "ece-scholarships" {
│ 
│ Unknown error (status 500): exit status 128 - fatal: '' is not a valid branch name
│ hint: See `man git check-ref-format`
│ hint: Disable this message with "git config set advice.refSyntax false"
│  - fatal: '' is not a valid branch name
│ hint: See `man git check-ref-format`
│ hint: Disable this message with "git config set advice.refSyntax false"

Here is the config for the repo in question

resource "forgejo_repository" "ece-scholarships" {
  default_branch  = "main"
  description     = null
  mirror          = true
  clone_addr      = "https://github.com/jnstockley/ECE-Scholarships.git"
  mirror_interval = "8h0m0s"
  has_releases    = true
  service         = "github"
  auth_token      = var.github_token
  name            = "ECE-Scholarships"
  private         = false
  owner           = forgejo_user.jack-stockley.login

  depends_on = [forgejo_user.jack-stockley]
}

the default branch is main. Also when I view the repo in the WebUI I do see it and it seems to be setup correctly which is strange.

Any ideas why this is happening? Thanks for your work on this!

[acch]

Hi @jnstockley, thanks much for your interest in the provider!

That's interesting indeed. For repo creation we've implemented a "create-then-update" workflow. Not all settings can be controlled during initial creation, hence we have to immediately update the repo to apply the remaining settings.
From the output you've provided it appears to me that the initial create works, but the subsequent update fails.

For repository mirrors, the default branch ist not sent during create. I guess that the server ignores it for updates, as the default branch is inferred from the source repo. Have you tried omitting the default_branch attribute? Have you tried setting it to an empty string ("")?

I remember seing weird behavior if the source repo is empty (no commits means no branches, not even a default one), but clearly this is not the case here. Can you spot any other differences between the repos that work, and the ones that don't?

[jnstockley]

@acch Sorry for the delay in my response. Omitting default_branch and setting it to "" give the same results. Honestly I can't think of anything, or see anything noticeable that could be causing this issue.

In case there is anything that I might be missing, here are links to two of the repos
https://github.com/jnstockley/BTTN/tree/main
https://github.com/jnstockley/ECE-Scholarships