git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Feature Request git snap, Lightweight Commit Workflow for Iterative Development

From
SBSuraj Bhadrike <surajbh2233@gmail.com>
Date
Jul 2, 2025, 18:30 UTC
Message-ID
<CAPGv+4ZT774b-LGMFpyv3cJYUrpWPMpkCGn25AfwD7MHskbV=g@mail.gmail.com>
Hi Git contributors,

This proposal introduces a new command git snap designed to support highly iterative development workflows nowdays influenced by AI coding assistants.

The rise of AI assistants and agentic AI workflows has changed the pace and nature of coding. A developer might cycle through dozens of variations of a function or component in a short period while collaborating with an AI.

This feature would provide a soft commit or snapshot capability, allowing developers to save their work state frequently and create a new commit every time as a snapshot or checkpoint without a commit message and flag where We can provide an option for developers to include files at the start of snap Session.

The current Git workflow presents friction in this type of workflow.

I've created a small Git repository with documents to help illustrate the concept. Please review it at your convenience : https://github.com/surajbh123/git-snap/tree/main

Your feedback on this is highly valuable. Thanks, Suraj Bhadrike

Next: Lucas Seiki Oshiro
Message 1 of 5 in “Feature Request git snap, Lightweight Commit Workflow for Iterative Development”
  1. Suraj BhadrikeJul 2, 2025
  2. Lucas Seiki OshiroJul 2, 2025
  3. brian m. carlsonJul 2, 2025
  4. Ben KnobleJul 3, 2025
  5. Suraj BhadrikeJul 3, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.