The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Git: "Committer" limit, or "Author" limit?

Chris Butler
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 14, 2012

In git, the "Committer" and "Author" are two separate concepts. However, the FishEye documentation seems to use the two terms interchangeably, so I'm confused as to what counts towards the "Committer limit".

So is the limit applied to the Committer field, or the Author field, or both?

(background: we have problems with the same person using multiple name/email address combinations, which we map with mailmap, but I want to write a pre-receive hook to stop it happening again.. just need to know which field to use)

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Answer accepted
Conor
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 15, 2012

FishEye uses the author and author email fields from git to form what Fisheye refers to as the committer name. It is this combination which is used in the committer limit checks.

There is overloading of terms across a number of SCM types and FishEye itself. It's hard to avoid this problem but I apologize for the confusion.

It sounds like you are familiar with https://confluence.atlassian.com/display/FISHKB/Git+or+Hg+Repository+exceeds+number+of+allowed+Committers already.

TAGS
AUG Leaders

Atlassian Community Events