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

  • Home
  • SEARCH
  • 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 627863
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T19:34:27+00:00 2026-05-13T19:34:27+00:00

Exposition: I do not git commit all that often; only after a lot of

  • 0

Exposition:

  1. I do not git commit all that often; only after a lot of work.
  2. I occasionally do stupid things, like ‘rm -f blah.hpp’ when I mean ‘rm -f blah.cpp’
  3. I use zsh
  4. I would like to set something up in my zsh precmd to do a “git add **/*; git commit -a -m ‘auto log …'”

Now, here’s the issue:
alot of these commits are spurious. At some future point (like 24 hours later), I would like to kill all these useless intermediate autocommits.

If your solution requires I slightly modify my git workflow — that is okay. I am willing to introduce changes in order to have this autocommit setup.

  • 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-13T19:34:27+00:00Added an answer on May 13, 2026 at 7:34 pm

    You want automatic “snapshot-style” commits which squash down once you have a true commit to make.

    Here is my rough idea:

    1. Treat master as your “official” commit timeline and work in a feature branch. (This is a pretty orthodox workflow anyway.)
    2. Work in a so-called feature branch which takes automatic snapshots (via zsh precommand)
    3. When you are ready for a (human) commit, merge all the automatic snapshots from your feature branch into master with --squash and commit with an appropriate message.

    This might require some aliases both in zsh and git but I think it could work. Here are some rough ideas, the key one being git merge –squash. (Also, sorry, I only speak Bash.)

    # I type this manually when I start work in the morning.
    start-snapshotting () {
        git checkout -b auto-snapshots master
        PROMPT_COMMAND=git-snapshot
    }
    
    git-snapshot () {
        branch=`git symbolic-ref HEAD`
        [ "$branch" = "refs/heads/auto-snapshots" ] || return 1
    
        git add . && \
        git status > /dev/null &&
        git commit -m 'Automatic snapshot'
    }
    
    # Do a real commit that I am interested in preserving.
    # Parameters are passed unmodified to "git commit"
    commit () {
        git checkout master && \
        git merge --squash auto-snapshots && \
        git commit "$@" && \
        git branch -D auto-snapshots && \
        git checkout -b auto-snapshots master
    }
    
    # I type this when I am done coding.
    stop-snapshotting () {
        unset PROMPT_COMMAND
        git checkout master && \
        git branch -D auto-snapshots
    }
    

    Keep in mind there will be tons of edge cases such as files you should have added to .gitignore and I am sure plenty of others. But I think it could work.

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

Sidebar

Ask A Question

Stats

  • Questions 371k
  • Answers 371k
  • Best Answers 0
  • User 1
  • Popular
  • Answers
  • Editorial Team

    How to approach applying for a job at a company ...

    • 7 Answers
  • Editorial Team

    How to handle personal stress caused by utterly incompetent and ...

    • 5 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • Editorial Team
    Editorial Team added an answer As the user will use the virtual machine to run… May 14, 2026 at 7:05 pm
  • Editorial Team
    Editorial Team added an answer It means the call stack as reported by Ruby's caller()… May 14, 2026 at 7:05 pm
  • Editorial Team
    Editorial Team added an answer WebLogic doesn't provide an embedded API so, even if it's… May 14, 2026 at 7:05 pm

Trending Tags

analytics british company computer developers django employee employer english facebook french google interview javascript language life php programmer programs salary

Top Members

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.