Martin Wagenführ wgnf

Conventional Commits

(adopted from Angular and based on Conventional Commits)

Message Format

Each commit message consists of a header, a body and a footer. The header has a special format that includes a type, a scope and a subject:

():

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

Follow standard conventions.
Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
Boy scout rule. Leave the campground cleaner than you found it.
Always find root cause. Always look for the root cause of a problem.

Design rules

$/
  artifacts/
  build/
  docs/
  lib/
  packages/
  samples/
  src/
 tests/

	<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">

	<!--
	How to define a variable.
	Just stick a new node in a property group.
	-->
	<PropertyGroup>
	<!-- This node in a property group will define a variable -->
	<TestVariable>Test Variable Value</TestVariable>

	###
	# Unity folders and files
	###
	[Aa]ssets/AssetStoreTools*
	[Bb]uild/
	[Ll]ibrary/
	[Ll]ocal[Cc]ache/
	[Oo]bj/
	[Tt]emp/
	[Uu]nityGenerated/