How a simple practice can add a lot of value to a team's work.

thanks for pointing this. It's fixed!

I would re-write the first sentence to "You probably know how to use Git on a daily basis" or perhaps "You probably know how to use Git in your daily workflow."

The rebase would ideally be the last thing you do on your branch, and very carefully.

And I also mention in the post that we should always use what's best for our teams, so if the squash merge works best for you, go for it! :)

Nothing stops you to use continuous integration with this workflow. For instance, Travis-CI and Codeship support branching (they can tell you if the new build will be fine or not).

I didn't mention that in the post because it's intended for beginners and adding that info there could maybe be a little too much :/

Sure, most CI systems support branching.

But what if you need to do ship a full pipeline of a branch for multi-repository project? I clarify the issue better in my post.