No difference shown when merging request

[SantoMozzarella]

Description

Problem:

1. There are two repositories:

• A shared/original repository (myorg/repo)
• My personal fork (myuser/repo), created from the shared one.

2. I made changes in my fork and pushed them to a feature branch.

3. I attempted to create a pull request from my fork into the original repository.

4. However, Gitea shows "nothing to compare" - as if there are no differences - even though the changes do exist.

Try to resolve:

1. I upgraded to version 1.24.3 (from 1.23), but the issue still persists.

2. From my observations, Gitea attempts to compare my fork with itself (fork vs fork), even when I explicitly select the original repository (myorg/repo) as the target during pull request creation.

3. I verified using Git on the command line:

• I compared my pushed changes to the upstream repository (the original repo).
• The changes are present, and the diff is real.
• git diff upstream/main..HEAD confirms the difference.

4. I enabled debug logging in app.ini, but when triggering the pull request creation, the logs only show an HTTP 200 OK response.
   It seems that Gitea is not comparing the fork against the original repository, but instead compares the fork with itself (fork vs fork) - despite the correct base repository being selected in the UI.

Additionally: docker exec gitea gitea doctor --all

Screenshots

Diff problem Show push in my local repo

Gitea Version

1.24.3

Can you reproduce the bug on the Gitea demo site?

No

Operating System

Docker container from docker hub (gitea/gitea:1.24.3)

Browser Version

Firefox 140.0.4 (64-bit)

[SantoMozzarella]

I set up a test container instance, and recreating the shared repository solved the problem there.
However, this issue has occurred three times already, and I cannot recreate the shared repository in production.

Also, the problem does not affect all users - some can commit to the shared repository.

[wxiaoguang]

Can you try these two fixes?

[wxiaoguang]

Another question, what is that commit ID for? The base repo's master, or the fork repo's master?

[SantoMozzarella]

Can you try these two fixes?

Hi.

Yes, I tried that, and I also ran: docker exec gitea gitea doctor --all

But it didn't resolve the issue.

[SantoMozzarella]

Another question, what is that commit ID for? The base repo's master, or the fork repo's master?

These are the latest commit ID in both repositories.
For some reason, they are identical, even though the shared repository doesn't have that commit yet (a378aa66c0).

The first ID - latest commit in share repository.
The second ID - latest commit in my forked repository.

'Share Repo' <<----pull request-- 'Forked Repo'

[SantoMozzarella]

If I manually create a link to compare the latest commit from share repository with my forked master branch, it suddenly detects the differences.

Example link where the latest commit from the shared repository is compared with the forked one:
https://git-example.org/WayneIndustries/framework/compare/78d8c048...ige/framework:master

[SantoMozzarella]

I created the PR using tea (https://gitea.com/gitea/tea).
It seems to be a bug on the frontend side.

[wxiaoguang]

I created the PR using tea (https://gitea.com/gitea/tea). It seems to be a bug on the frontend side.

Good point! So it is reproducible by using tea cli?

[SantoMozzarella]

Good point! So it is reproducible by using tea cli?

Yes, but the comparison also doesn't happen in the Web UI.

[wxiaoguang]

IIRC tea cli uses API, I am not able to reproduce:

 curl -X 'POST' \
  'http://localhost:3000/api/v1/repos/root/test-btn/pulls' \
  -H 'accept: application/json' \
  -H 'authorization: bearer xxxxxxxxxxxxxxxxxxxxxx' \
  -H 'Content-Type: application/json' \
  -d '{"base":"main","head":"orgprivate:branch-for-base","title":"test pr"}'

---

Can you provide the reproducible steps?