forgejo_backup/models/migrations/v1_12
Gusted 7c150be23d feat: improved performances when checking for conflicts on pull requests (#7727)
- `testPatch` is a function that is called to test a pull request and determine the state of the pull request. Checking for merge conflicts, check if the diff is empty and if the pull request modifies any protected files.
- The checking for merge conflict and if the diff is empty used git commands that relied on a working tree to correctly functions. Forgejo store repositories in a bare format which do not contain a working tree. This means that a temporary copy was created every time a pull request had to be re-checked and for large repositories involving quite some I/O interaction.
- This patch adjusts those codepaths to instead use newer Git plumbing commands that work without requiring a work tree and can thus be used directly on the bare repository. The merge conflict is now done via [`git-merge-tree(1)`](https://git-scm.com/docs/git-merge-tree/) and checking if the diff is empty is done via [`git-diff-tree(1)`](https://git-scm.com/docs/git-diff-tree).
- If the function is called to test a patch where the head and base repository are not the same, then [Git alternate](https://git-scm.com/docs/gitglossary#Documentation/gitglossary.txt-aiddefalternateobjectdatabaseaalternateobjectdatabase) is used to make the head commit available in the base repository, this done on a per git command basis via the `GIT_ALTERNATE_OBJECT_DIRECTORIES` environment.
- As far as I can understand the documentation and the existing code, there's no edge case that the new code cannot handle. It also results in a cleaner codepath, as the existing code did a lot of checking and merging in a more traditional approach that required a lot of (parsing) code, while the new code offloads this to git and has a trivial parser of the output.
- Resolves forgejo/forgejo#7701
- Added exhaustive integration testing.

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/7727
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Reviewed-by: Otto <otto@codeberg.org>
Co-authored-by: Gusted <postmaster@gusted.xyz>
Co-committed-by: Gusted <postmaster@gusted.xyz>
2025-05-16 12:40:38 +00:00
..
v117.go Rename Sync2 -> Sync (#26479) 2023-08-13 21:17:21 +02:00
v118.go Rename Sync2 -> Sync (#26479) 2023-08-13 21:17:21 +02:00
v119.go Implement FSFE REUSE for golang files (#21840) 2022-11-27 18:20:29 +00:00
v120.go Rename Sync2 -> Sync (#26479) 2023-08-13 21:17:21 +02:00
v121.go Rename Sync2 -> Sync (#26479) 2023-08-13 21:17:21 +02:00
v122.go Rename Sync2 -> Sync (#26479) 2023-08-13 21:17:21 +02:00
v123.go Rename Sync2 -> Sync (#26479) 2023-08-13 21:17:21 +02:00
v124.go Rename Sync2 -> Sync (#26479) 2023-08-13 21:17:21 +02:00
v125.go Rename Sync2 -> Sync (#26479) 2023-08-13 21:17:21 +02:00
v126.go Implement FSFE REUSE for golang files (#21840) 2022-11-27 18:20:29 +00:00
v127.go chore: branding import path (#7337) 2025-03-27 19:40:14 +00:00
v128.go chore: branding import path (#7337) 2025-03-27 19:40:14 +00:00
v129.go Implement FSFE REUSE for golang files (#21840) 2022-11-27 18:20:29 +00:00
v130.go chore: branding import path (#7337) 2025-03-27 19:40:14 +00:00
v131.go Rename Sync2 -> Sync (#26479) 2023-08-13 21:17:21 +02:00
v132.go Rename Sync2 -> Sync (#26479) 2023-08-13 21:17:21 +02:00
v133.go Rename Sync2 -> Sync (#26479) 2023-08-13 21:17:21 +02:00
v134.go chore: branding import path (#7337) 2025-03-27 19:40:14 +00:00
v135.go Rename Sync2 -> Sync (#26479) 2023-08-13 21:17:21 +02:00
v136.go feat: improved performances when checking for conflicts on pull requests (#7727) 2025-05-16 12:40:38 +00:00
v137.go Rename Sync2 -> Sync (#26479) 2023-08-13 21:17:21 +02:00
v138.go Rename Sync2 -> Sync (#26479) 2023-08-13 21:17:21 +02:00
v139.go chore: branding import path (#7337) 2025-03-27 19:40:14 +00:00