Learn more about these different git repos.
Other Git URLs
Pagure does not seem to be able to properly render commits that have author dates that differ from commit dates.
As an example: https://pagure.io/appliance-tools/c/bca4b0df03b2831c31ace011fdcf3c6e73c9df66?branch=master
On pagure, it says that it was authored and committed on Feb 4. However, that's not true, according to the git log:
commit bca4b0df03b2831c31ace011fdcf3c6e73c9df66 Author: Neal Gompa <> AuthorDate: Fri Dec 2 08:52:11 2016 -0500 Commit: Neal Gompa <> CommitDate: Sat Feb 4 18:39:27 2017 -0500 Fix import for compatibility with livecd-tools v24
Another example: https://pagure.io/appliance-tools/c/9db3d307e4062946fc76f76a4573a07c111fce6c?branch=master
The original git log message:
commit 9db3d307e4062946fc76f76a4573a07c111fce6c Author: Peter Robinson <> AuthorDate: Tue Sep 20 12:43:25 2016 +0100 Commit: Neal Gompa <> CommitDate: Sat Feb 4 18:38:51 2017 -0500 Fix swap partition type creation, Set boot partition as bootable
Something is going wrong with how pagure is rendering git log data, and it's ignoring the AuthorDate and using exclusively the CommitDate.
I think I would bail this one to pygit2: http://www.pygit2.org/objects.html#commits it only provides the commit time not the author one :)
@pingou I think libgit2 can do this, since GitHub (which uses libgit2 for its system) is able to represent the data. I'm not sure how yet, though...
Should we at least not lie and say "Authored and committed" in Pagure, if we don't actually know that? Just say "Committed"?
Metadata Update from @wombelix: - Issue set to the milestone: 6.0 - Issue tagged with: RFE
Log in to comment on this ticket.