News for hackers. Stuff that matters.
Re:Ask HN: How would you describe a commit? by ilkhan4 on Thursday August 08, 2024 @09:43AM (#41191416)
I would describe it as a stopping point, or a chunk of work that represents a finished step (however you define a step).
Re:Ask HN: How would you describe a commit? by pipesorter on Thursday August 08, 2024 @09:51AM (#41191509)
People are familiar with Draft (email or blog) state and Send or Publish state. I would go with email analogy. So I would describe commit similar to sending an email after drafting in a thread. Here I also could undo anytime and make it a draft. Similar to forward I can clone a thread (branch out?).
Re:Ask HN: How would you describe a commit? by samuelstros on Thursday August 08, 2024 @09:59AM (#41191611)
Isn't sending an email publishing (in version control terms CI/CD deployment)?
Re:Ask HN: How would you describe a commit? by samuelstros on Thursday August 08, 2024 @09:40AM (#41191381)
Things we discussed:

- a commit is somewhat a 'save' but unlike a 'final_v1.docx'

- a commit prevents changes from being overwritten

Re:Ask HN: How would you describe a commit? by PaulHoule on Thursday August 08, 2024 @09:17AM (#41191177)
Like taking a snapshot with a camera?
Re:Ask HN: How would you describe a commit? by samuelstros on Thursday August 08, 2024 @09:39AM (#41191368)
Doesn't make click for me. Snapshot is a VCS term that seems to have a different meaning in photography.

From Wikipedia "A snapshot is a photograph that is "shot" spontaneously and quickly, most often without artistic or journalistic intent and usually made with a relatively cheap and compact camera."