Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You can probably tell who did it! When you rebase, since the commits are rewritten, the committer information will be from the person doing the rebase, not the original author. (This is separate from the author information.)</p> <p>You can see this information in <code>gitk</code> (in the diff pane in the lower left) or in the output of <code>git log --pretty=fuller</code> (as in more full than full). Example log output:</p> <pre><code>commit b8624718b97a39a04637c91ec3517c109f3f681d Author: Original Author &lt;original@author.com&gt; AuthorDate: Sun Aug 8 02:15:10 2010 -0300 Commit: New Committer &lt;new@committer.com&gt; CommitDate: Mon Jan 23 17:29:39 2012 -0800 a lovely commit message ... </code></pre> <p>The committer name, email, and date are from the operation that actually wrote the commit. Note that if it's been rewritten multiple times, you'll only have the most recent information.</p> <p>As for where it was rebased <em>from</em>... if the original version of the rebased commits are also in your history, that's easy. Just search the full history for a matching commit, for example by a fragment of the commit message, or by something that was changed in the commit:</p> <pre><code>git log --all --grep='commit subject from a rebased commit' git log --all -S'void this_function_was_added() {' </code></pre> <p>If you don't have the original commit anywhere in history anymore, that's going to be tougher. Hopefully you'll be able to find out by tracking down the person who did it, and if they don't know, asking them to run <code>git reflog show &lt;branch&gt;</code> in their repository, to see the history of that branch.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload