[GH-ISSUE #72] GetCommitsInfo mishandles merge commits #5

New Issue

2026-02-16T10:23:44-05:00

yindo commented

2026-02-16 10:23:44 -05:00

Originally created by @ethantkoenig on GitHub (Jun 27, 2017).
Original GitHub issue: https://github.com/go-gitea/git/issues/72

GetCommitInfos does not properly handle merge commits. In some cases, it will only traverse one parent of a merge commit. If this happens, it may reach the initial commit without finding a match for some entries. This could result in either an infinite loop, or a 500 (bad revision <hash>^).

I'm hoping to have a fix soon.

Originally created by @ethantkoenig on GitHub (Jun 27, 2017). Original GitHub issue: https://github.com/go-gitea/git/issues/72 `GetCommitInfos` does not properly handle merge commits. In some cases, it will only traverse one parent of a merge commit. If this happens, it may reach the initial commit without finding a match for some entries. This could result in either an infinite loop, or a 500 (`bad revision <hash>^`). I'm hoping to have a fix soon.

yindo referenced this issue

2026-02-16 10:23:51 -05:00

[PR #5] [MERGED] Fix variable name collision with import name #17

yindo changed title from ~~GetCommitsInfo mishandles merge commits~~ to [GH-ISSUE #72] GetCommitsInfo mishandles merge commits

2026-06-05 16:30:41 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: go-gitea/git#5