Hacker News new | past | comments | ask | show | jobs | submit login

Something I kind of depend on--which may be a crutch, I'm not entirely sure--is VS Code's "gutter indicators" feature[1] that simply indicates where code was added/edited/deleted. It helps me jump between changes to tweak further or undo them. The normal diff view in VS Code is often useful too, and is essentially also made less useful if you commit too frequently.

In the past this has caused me to commit way too little (i.e. sometimes weeks between commits...), but I've improved on that somewhat.

I still have a bunch of tabs open on my laptop about some Git workflows that should allow me to commit more frequently and then revert back to my 'starting point' for the gutter indicators and other diffing. Must get around to trying some of that stuff out.

I'm probably missing some other useful tool or way of working to help with this kind of thing - let me know if anyone else has thoughts on this. Personally I don't think I could ever get to this 'micro-committing' state, but there is a middle ground somewhere that I'm aiming towards.

[1] https://code.visualstudio.com/Docs/editor/versioncontrol#_gu...




> I'm probably missing some other useful tool or way of working to help with this kind of thing - let me know if anyone else has thoughts on this.

The combination of 'git commit --amend' with 'git reflog' enables creation of commits that are hidden from the usual history as shown by 'git log --oneline', but no less fully inspectable later. Likewise recoverable, by passing commit hashes from 'git reflog' to the usual tools.


That sounds interesting, thanks! Will look into it.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: