I’ve written about using “git push –force-with-lease” instead of git push –force” because “force-with-lease” will only force push changes if your local copy is aware of all of the commits on the remote branch but how is git “aware” of the commits.
On a project I needed to redirect a URL based on the presence or absence of a URL parameter. This is the htaccess rule I added.
The Allow / Block popup in Google Chrome is an all too familiar sight when browsing the web, however this can be prevented. We can change the setting to automatically Block all location requests (they will not be able to see your location) without seeing the popup.
One of my posts was shared and it did not have an image for the Twitter Card. After I added an image for the Twitter Card, I had to clear the cached version on Twitter so the image would appear in tweets. This is how I cleared the cache and updated the image in the URL for Twitter.
The PDF Toolbar that comes up in Google Chrome when displaying a PDF can be suppressed by modifying the URL.
Both HEAD^ and HEAD~ can be used in Git to refer to previous commits but in different ways.
Recently, I had the opportunity to work with some elementary students on their math fast facts (i.e. single-digit addition, subtraction, multiplication, and division). I noticed that I was able to keep the students much more engaged with one simple change.
By default Vim is the editor used when writing a Git commit message. While I love Vim, it does work very differently than most other editors. A good option for those who are not comfortable with Vim, is to use a different editor. This is how to setup Git to use a different editor.
I do most of my work in Vim (or Neovim) in tmux inside of iTerm on my Mac. I found my color schemes were being properly applied in Neovim but not in Vim (version 8). Adding two lines to my .vimrc corrected the problem for me.