mirror of
https://github.com/go-gitea/git.git
synced 2026-07-19 22:44:05 -04:00
[GH-ISSUE #129] 'tagger' value should be assigned to both Author and Committer probably #12
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @SagePtr on GitHub (Sep 19, 2018).
Original GitHub issue: https://github.com/go-gitea/git/issues/129
In cat-file output, regular commits have following keys:
author (one who wrote code and sent diff content)
committer (one who commited that code to repo or merged PR)
Tag commits have one key: tagger (which corresponds to user who made new tag)
Now, in repo_commit.go, function parseCommitData, tagger is assigned to commit.Author, and commit.Committer stays nil.
I think, for better compatibility, tagger should be assigned to both commit.Author and commit.Committer, because in this case tagger is both author of tag and committer of this tag.
This would also solve go-gitea/gitea#4961 issue when signatures are verified against Committer field, but Committer field is just nil for tag commit.
'tagger' value should be assigned to both Author and Committer probablyto [GH-ISSUE #129] 'tagger' value should be assigned to both Author and Committer probably