Disclaimer: I wrote this post about six weeks ago but forgot to publish it, I probably should start using scheduling. Hope you enjoy it anyway!…
Tag: github
I have been discovering and experimenting with Kubernetes right after I passed my AWS Certified Solutions Architect Associate exam. So far, I wrote and deployed…
It’s that time of the year again. Hacktoberfest 2019 begun a couple of days ago and pull requests are off the charts! We are back…
Hello Mishamigos, in a week we will be the last day of October. The day where ghouls and demons will sprout and throw one more spell at us humble coding people. The day where until the last second you will look at your inbox petrified waiting for the next jump scare. As you guessed, in case you were oblivious to the post title, tomorrow is the first day of the last week of Hacktoberfest, 2018 edition.
Git squash merge: non, no, nein, nee, na, nej, não, net
Posted in Building future-proof software, and Did you notice?
Today I will tell you why you should say no to git squash merges. Even better I will show you. First, I will explain what lead me to write this post. Then, I will provide you with steps to reproduce a problem that seems ignored. A problem that will eventually bite you if you keep using git squash merges. No spoilers until you get there. Hopefully, you will get my point. Since the aim of this post is to save you time in the future or even now this will also be the latest entry of my future-proof series.