You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We tried to enable the "verify committer" option in our repositories, but GitBlit stopped
accepting merge commits even when done with the --no-ff option.
If we try to push regular commits they succeed, only merges fail with the "[...] was
not committed by [...]" error.
Please note we're using the LDAP authentication module, not the integrated one.
We're using GitBlit GO 1.2.1 on a Windows Server 2012.
You can find attached an example of the error in a test repository, I'm on the "my-feature"
branch where I just merged the "master" branch, and I'm trying to push the commit.
GitBlit's complaining the commit "Prova" was not done by me, even though I choose to
do a non fast forward merge.
Originally reported on Google Code with ID 264
Reported by
andrea.bertin
on 2013-07-02 16:29:51- _Attachment: screenshot.png
![screenshot.png](https://storage.googleapis.com/google-code-attachments/gitblit/issue-264/comment-0/screenshot.png)_
The text was updated successfully, but these errors were encountered: