Gitea: "user does not exist"

[holmesb]

Is there an existing issue for this?

• I have searched the existing issues

Description of the bug

Hi,

Versions > 2.4 error when trying to create change logs using command:

git cliff --workdir /foo-repo --config cliff.toml --gitea-token <token> --bump
▹▸▹▹▹ Retrieving data from Gitea... (foo-org/foo-repo)                                      ERROR git_cliff_core::remote    > Request error: {"message":"user does not exist [uid: 0, name: ]","url":"https://codeberg.org/api/swagger"}

GC v2.4 works fine. Can anyone reproduce? I also tried specifying the user's password instead of a token, no dice.

Steps To Reproduce

.

Expected behavior

Change logs created

Screenshots / Logs

No response

Software information

• Operating system:
• Rust version:
• Project version:

Additional context

No response

[welcome]

Thanks for opening your first issue at git-cliff! Be sure to follow the issue template! ⛰️

[orhun]

Hello!

Can you run with -vv arguments to see if there are any other errors while sending requests?

GC v2.4 works fine.

That version was a while ago, I don't remember what has changed relatively to Gitea since then :/

I can provide a better help if that repo is open source.

[holmesb]

Thanks for your help so far Orhan. The -vv output shows there are references to https://codeberg.org/. It appears git cliff is trying to find our private repo on that public Gitea server. Our code isn’t on https://codeberg.org/, it’s on our locally-hosted Gitea. Any idea why gitea > v2.4 tries to find it on https://codeberg.org/? We haven’t changed the command we invoke GC using. We don’t mention codeberg anywhere in our code.

I thought git cliff got the remote git repo from the <repo>/.git/config file in it. I’ve just double checked this and it correctly contains:

[remote "origin"]
    url = https://our.private.gitea.server/foo-org/foo-repo.git
    fetch = +refs/heads/*:refs/remotes/origin/*

Does >=v2.5 no longer read this file?

As a workaround, we've set:

[remote.gitea]
api_url = "https://our.private.gitea.server"

in our cliff.toml. Then >=v2.5 (eg 2.7) successfully creates change logs.

PS, the API URL for gitea is actually https://<gitea_domain>/api/v1, not https://<gitea_domain>, but only the latter works. Perhaps this should be a separate (lesser) issue.

PPS, just to note, in v2.4, it was possible to use a password for --gitea-token, now it requires a token.