gitea: Conflicting files shown on pull request but merging without conflict
- Gitea version (or commit ref):
1.12.5and1.14.0+dev-251-g78204a7a7 - Git version:
2.24.1 - Operating system:
- Database (use
[x]):- PostgreSQL
- MySQL
- MSSQL
- SQLite
- Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Log gist:
Description
I created a pull request which showed me that one of the files was conflicting. I then wanted to resolve this conflict locally but the merge worked just fine.
I re-created this on try.gitea.io with a simplified example, see this test repo: https://try.gitea.io/test-gitea3/conflict-test
Steps taken:
- created initial version on
master - created branch
test - modified same file on branch
test - modified same file on branch
master - created PR
Result:
This pull request has changes conflicting with the target branch. settings.py
This is the output when merging locally:
$ git merge test
Auto-merging settings.py
Merge made by the 'recursive' strategy.
settings.py | 41 +++++++++++++++++++++++++++++++++++++++--
1 file changed, 39 insertions(+), 2 deletions(-)
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 4
- Comments: 29 (23 by maintainers)
Commits related to this issue
- Improve TestPatch to use git read-tree -m The current TestPatch conflict code uses a plain git apply which does not properly account for 3-way merging. However, we can improve things using `git read-... — committed to zeripath/gitea by zeripath 3 years ago
- Improve TestPatch to use git read-tree -m and implement git-merge-one-file functionality (#18004) The current TestPatch conflict code uses a plain git apply which does not properly account for 3-way... — committed to go-gitea/gitea by zeripath 3 years ago
- Improve TestPatch to use git read-tree -m and implement git-merge-one-file functionality (#18004) The current TestPatch conflict code uses a plain git apply which does not properly account for 3-way... — committed to Chianina/gitea by zeripath 3 years ago
OK, my proposed PR using
git read-tree -mworks correctly for that.Can you give an example that should conflict too?