| Website | https://cdmwebs.com |
| Work | https://knowndecimal.com |
| GitHub | https://github.com/cdmwebs |
| Website | https://cdmwebs.com |
| Work | https://knowndecimal.com |
| GitHub | https://github.com/cdmwebs |
I'm pedantic as hell when it comes to managing the git history for my work ... @cdmwebs broke me ....
Here's how I operate:
https://binarysolo.chapter24.blog/how-i-manage-my-git-history
I'm generally a rather pedantic person and this is supercharged when it comes to managing the git history on my projects. I used GitHub's squash and merge for a while before Chris Moore taught me a few tricks. I'm not a fan of squash and merge because it squashes an entire Pull Request into a single commit, no matter how large it is. This means that rather large changes could live under a single commit. I believe the commit history should tell a linear story, as pretentious as that might...
Tomorrow we're deploying a Rails 7 upgrade. I've been working on this app for ten years.
The codebase was born 14 years, 3 months and 30 days ago. It began life at Rails 2.1.
It's seen just about every JS framework come and go.
Forget diamonds. Rubies are forever :D
Finally ... the damn thing is out in the wild.
It was quite easy in the end, only cost me about 99% of my sanity.
Buy now ๐ https://railsandhotwirecodex.com.
We're giving away ten copies of @ayush's new book today for #GivingTuesday
Pre-orders are open!