philipstanislaus

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional

	# create empty base commit that will be the reference for our code review
	git checkout --orphan base
	git rm -r --cached .
	git clean -fxd
	git commit --allow-empty -m "Start of the review"

	# create and checkout review branch that will include the latest code that should be reviewed
	git checkout -b review

	# merge main branch into that new review branch

	/*
	Go on your labels page (https://github.com/user/repo/labels)

	Edit the following label array
	or
	Use this snippet to export github labels (https://gist.github.com/MoOx/93c2853fee760f42d97f)
	and replace it

	Paste this script in your console
	Press Enter!!

	# Sample Nginx config with sane caching settings for modern web development
	#
	# Motivation:
	# Modern web development often happens with developer tools open, e. g. the Chrome Dev Tools.
	# These tools automatically deactivate all sorts of caching for you, so you always have a fresh
	# and juicy version of your assets available.
	# At some point, however, you want to show your work to testers, your boss or your client.
	# After you implemented and deployed their feedback, they reload the testing page – and report
	# the exact same issues as before! What happened? Of course, they did not have developer tools
	# open, and of course, they did not empty their caches before navigating to your site.