4 ms·
As someone who is no longer a professional programmer and does not work on a team, how I use git is I have an alias called `yolo` that adds everything, commits
by karaterobot 2y ago
As someone who is no longer a professional programmer and does not work on a team, how I use git is I have an alias called `yolo` that adds everything, commits with allow-empty-message, and pushes it all to main, where it is immediately deployed without gates straight into production. I've gone feral, and I'll never be an inside cat again.
- imiric 2y agoGood luck going back to that repo in a few months :)
- bryanlarsen 2y agoThe most likely alternative to "yolo" is no change control. They've got the most important part, the history.
- imiric 2y agoBut that history is hardly useful without metadata to tell them what each snapshot contains, at the very least. The only thing they have to go by is the commit date, so they can never know whether a snapshot is stable, what to revert to, etc. At that point you're not much better off from doing manual versioning by compressing the directory, and naming each file `v1`, `v2`, `v3-final-final2`, etc. (: They don't need Git for that.
- karaterobot 2y agoThe thing is, I don't really work on a complicated app anymore, and I'm the only one who commits to it. So, there's not much to think about. I know that if it worked last Wednesday and is broken now, I should roll it back to last Wednesday, etc.