Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7090669
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 28, 20262026-05-28T08:05:00+00:00 2026-05-28T08:05:00+00:00

I know that GIT rebases will rewrite the history — i.e. the commit ids

  • 0

I know that GIT rebases will rewrite the history — i.e. the commit ids will change. However, Is there any way to trace when a branch was rebased and from which branch?

EDIT: I have a development branch ‘A’ and a topic branch ‘B’. ‘A’ is shared by the team. At some point, ‘A’ has been re-based with a mainstream branch. As a result of the re-base (and subsequent commits), when I updated the topic branch, I saw discrepancies. I am trying to find out the correct person to talk to to resolve the issues.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-28T08:05:01+00:00Added an answer on May 28, 2026 at 8:05 am

    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.)

    You can see this information in gitk (in the diff pane in the lower left) or in the output of git log --pretty=fuller (as in more full than full). Example log output:

    commit b8624718b97a39a04637c91ec3517c109f3f681d
    Author:     Original Author <original@author.com>
    AuthorDate: Sun Aug 8 02:15:10 2010 -0300
    Commit:     New Committer <new@committer.com>
    CommitDate: Mon Jan 23 17:29:39 2012 -0800
    
        a lovely commit message
    
    ...
    

    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.

    As for where it was rebased from… 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:

    git log --all --grep='commit subject from a rebased commit'
    git log --all -S'void this_function_was_added() {'
    

    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 git reflog show <branch> in their repository, to see the history of that branch.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Assuming that I know there is a git-daemon running at git://git.mycompany.com , how can
I know that you can insert multiple rows at once, is there a way
I know that upon pulling there will be conflicts, but I already know that
I know that |DataDirectory| will resolve to App_Data in an ASP.NET application but is
I know that the MsNLB can be configured to user mulitcast with IGMP. However,
I know that I can use the git diff command to check the changes,
I want to reproduce the pager behavior that git-diff uses but I don't know
I know that git diff --word-diff=color shows a word diff between the working tree
I'm using git rebase -i to rewrite history — in this case, make a
As I am learning Git, I get to know that the other VCS systems

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.