See how a minor change to your commit message style can make you a better programmer.
Format: <type>(<scope>): <subject>
<scope>
is optional
# One liner | |
wget --recursive --page-requisites --adjust-extension --span-hosts --convert-links --restrict-file-names=windows --domains yoursite.com --no-parent yoursite.com | |
# Explained | |
wget \ | |
--recursive \ # Download the whole site. | |
--page-requisites \ # Get all assets/elements (CSS/JS/images). | |
--adjust-extension \ # Save files with .html on the end. | |
--span-hosts \ # Include necessary assets from offsite as well. | |
--convert-links \ # Update links to still work in the static version. |
Warning: this document has to be updated by pointing to https://github.com/SpenceKonde/ATTinyCore
This note describes the configuration of an ATtiny85 based microcontroller development board named Digispark and similar to the Arduino line. It is available in many online marketplaces for roughly 1 dollar (e.g., Ebay, Amazon, AliExpress) and is shipped fully assembled, including a V-USB interface (a software-only implementation of a low-speed USB device for Atmel's AVR microcontrollers). Coding is similar to Arduino: it uses the familiar Arduino IDE and is already provided with a ready-to-use bootloader (
#!/usr/bin/env bash | |
# Usage: ./bump_version.sh <major|minor|patch> - Increments the relevant version part by one. | |
# | |
# Usage 2: ./bump_version.sh <version-from> <version-to> | |
# e.g: ./bump_version.sh 1.1.1 2.0 | |
set -e | |
# Define which files to update and the pattern to look for |
# The initial version | |
if [ ! -f .env ] | |
then | |
export $(cat .env | xargs) | |
fi | |
# My favorite from the comments. Thanks @richarddewit & others! | |
set -a && source .env && set +a |
<p> | |
<button id="btn7">Tween Faces</button> | |
<button id="btn8">Rotate Parent</button> | |
<div> | |
<button id="btn1">front face</button> | |
<button id="btn2">right face</button> | |
<button id="btn3">back face</button> | |
<button id="btn4">left face</button> | |
<button id="btn5">top face</button> | |
<button id="btn6">bottom face</button> |
Shortcut | Action |
---|---|
CTRL+@ | set-mark-command |
CTRL+A | beginning-of-line |
CTRL+B | backward-char |
CTRL+D | delete-char-or-list |
CTRL+E | end-of-line |
CTRL+F | forward-char |
CTRL+G | send-break |
CTRL+H | backward-delete-char |
# ---------------------------------- | |
# Colors | |
# ---------------------------------- | |
NOCOLOR='\033[0m' | |
RED='\033[0;31m' | |
GREEN='\033[0;32m' | |
ORANGE='\033[0;33m' | |
BLUE='\033[0;34m' | |
PURPLE='\033[0;35m' | |
CYAN='\033[0;36m' |
Inspired by dannyfritz/commit-message-emoji
See also gitmoji.
Commit type | Emoji |
---|---|
Initial commit | 🎉 :tada: |
Version tag | 🔖 :bookmark: |
New feature | ✨ :sparkles: |
Bugfix | 🐛 :bug: |
As a freelancer, I build a lot of web sites. That's a lot of code changes to track. Thankfully, a Git-enabled workflow with proper branching makes short work of project tracking. I can easily see development features in branches as well as a snapshot of the sites' production code. A nice addition to that workflow is that ability to use Git to push updates to any of the various sites I work on while committing changes.