3 ms·
Commit graph is just a data structure. Sometimes it represents a "history", sometimes other things. Personally, I like it when project's repository represents
by seba_dos1 3mo ago
Commit graph is just a data structure. Sometimes it represents a "history", sometimes other things.
Personally, I like it when project's repository represents the history of the project rather than the history of random things developers do on their machines, but you do you.
- hahahaa 3mo agoI am thinking of remote. Edits before pushing OK with me (they ate equivalent of recloning and redoing anyway)
- seba_dos1 3mo agoRemotes aren't equal either. Sometimes the remote is my other machine, sometimes it's a fork on a forge used for producing CI artifacts. It's a good rule of thumb to consider shared branches to be append-only, but not every remote branch is "shared" and, as with any proper rule of thumb, you can always find exceptions.
- hahahaa 3mo agoOk I amend to what I think I really mean: don't edit history for anything deployed to prod (or released to public or customers) already.
- deleted 3mo ago[deleted]