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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 2, 20262026-06-02T00:04:22+00:00 2026-06-02T00:04:22+00:00

I like to commit quite frequently (and even randomly) when I am working on

  • 0

I like to commit quite frequently (and even randomly) when I am working on some code, because if I screw up somewhere I can always roll back my changes.

However, when I decide to push all the changes to the master repository, I don’t like people to see all the random commits, because some of them are really meaningless to them, and it makes the change tree unnecessarily long.

How do I “consolidate” all my local commits before I push?

  • 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-02T00:04:23+00:00Added an answer on June 2, 2026 at 12:04 am

    You can combine your commits by rebase and squashing the ones you dont need.

    Refere this: http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html

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

Sidebar

Related Questions

I've been working with branches for quite some time now, but I always used
Currently I always worked with GIT and was quite satisfied. Due to some project
Case Quite often I find myself staring at some old code that doesn't look
When I commit something in Mercurial like this: hg commit -m username question I
I like to use markdown notation in my subversion commit messages, planning to one
I'd like to have a commit message cleanup that will not necessarily remove lines
Seems like it would be better if you did commit followed by merge. I'm
I'm writing a pre-commit hook, and would like to do a check on the
I'm probably going to take some heat for this question. But I'd like to
Every time I need to design a new database I spend quite some time

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.