![]() ![]() ![]() I don't necessarily want to dictate nitpicky git usage but I have a hard time accepting when people just to refuse how rebasing and cherrypicking work when they're both core basic features of a tool we all use every day. I see it all because I have visibility in to the history and branch relationships but I still get shrugs and eye rolls when I bring it up. Still, I constantly struggle with coworkers merging feature branches from 100 commits ago in to new feature branches and brute force resolving conflicts across half a dozen files in one commit without any context. These days, the UI for rebasing and cherry picking in Gitkraken is state of the art and effortless and I use them every day without hesitation and without the fear that comes from not understanding or knowing what I'm doing. I was receptive and in about 10 minutes, I realized there was a significant set of standard features and day to day Git use I was previously just oblivious to. The result is, because developers only have a hammer, they brute force merge everything which results in grotesque conflict resolutions and commit histories and makes it hard to untangle problems.Īt a previous job, another developer was kind enough to walk through rebasing on the command line with vim. I think it's a tragedy that just about every developer uses git but most learn add, commit, branch, and merge and then just stop learning.Ī lot of people are scared of rebase and cherrypick and shut down or get defensive when you mention them or try to encourage their use. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |