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 7987607
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 4, 20262026-06-04T12:11:52+00:00 2026-06-04T12:11:52+00:00

I do a commit to my local repo, then I pushed it to origin

  • 0

I do a commit to my local repo, then I pushed it to origin after that I amended the commit and tried to push it but I got an error saying that I need to pull from origin, I made that and a conflict happened I fixed it and committed the change to local and remote repos. Now my commit history is horrible here it is:

enter image description here
The commit I made named: An early version of the ImportImageModel

How I can rebase the history to fix these unnecessarily commits?

  • 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-06-04T12:11:53+00:00Added an answer on June 4, 2026 at 12:11 pm

    Interactive rebase should do the trick. It allows do to many things, among them removing commits.

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

Sidebar

Related Questions

I'm committing changes to my local git repo, then I push the changes to
Subversion: is it possible to commit local revisions without pushing them, and push them
I do: $ git commit . $ git push error: Entry 'file.php' not uptodate.
I am trying to push new changes, but I have a conflicted file. After
On my local git repo I've got many commits, which include 'secret' connection strings
Tried to use what's here , but that doesn't solve things for me. I've
My local repo contains the following commits: A ---- B ---- C ---- D
I have repository on GitHub to which I commit regularly from my local computer.
I heard that if we are working on a feature and then we need
I need to recover two Git branches that I somehow deleted during a push.

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.