Rebasing is a frequent task for anyone using git. We sometimes use rebasing to branch our code from the last changes or even just to drop commits from a branch.
Oftentimes when trying to push after a rebase, you’ll see something like the following:
hint: Updates were rejected because the tip of your current branch is behind hint: its remote counterpart. Integrate the remote changes (e.g. hint: 'git pull ...') before pushing again. hint: See the 'Note about fast-forwards' in 'git push --help' for details.
Commonly developers will use the
-f flags during a
push to force pushing code changes:
git push origin my-branch --force # or git push origin my-branch -f
I was recently surprised to find out that you could also prefix the branch name with
+ to force a push:
git push origin +my-branch
+ syntax is interesting but doesn’t seem intuitive so it’s not a practice I’d use, but that doesn’t mean you shouldn’t!
You’ve probably heard the talk around the water cooler about how promises are the future. All of the cool kids are using them, but you don’t see what makes them so special. Can’t you just use a callback? What’s the big deal? In this article, we’ll…
Creating Scrolling Parallax Effects with CSS
Introduction For quite a long time now websites with the so-called “parallax” effect have been really popular. In case you haven’t heard of this effect, it basically includes different layers of images that are moving in different directions or at different speeds. This leads to a…
One interesting aspect of web development is geolocation; where is your user viewing your website from? You can base your local language on that data or show certain products in your store based on the user’s location. Let’s examine how you can…