See how a minor change to your commit message style can make you a better programmer.
Format: <type>(<scope>): <subject>
<scope> is optional
| // S and K are primitive function combinators. | |
| const S = a => b => c => a (c) (b (c)) | |
| const K = a => b => a | |
| // Non-primitive combinators can be created with S and K. | |
| const C = S (S (K (S (K (S)) (K))) (S)) (K (K)) | |
| const I = S (K) (K) | |
| const KI = K (I) | |
| const M = S (I) (I) | |
| const R = S (K (S (K (S)) (K))) (S (K (S (I))) (K)) |
| # <type>: (If applied, this commit will...) <subject> (Max 50 char) | |
| # |<---- Using a Maximum Of 50 Characters ---->| | |
| # Explain why this change is being made | |
| # |<---- Try To Limit Each Line to a Maximum Of 72 Characters ---->| | |
| # Provide links or keys to any relevant tickets, articles or other resources | |
| # Example: Github issue #23 |
| # ~/.tmux.conf | |
| # | |
| # See the following files: | |
| # | |
| # /opt/local/share/doc/tmux/t-williams.conf | |
| # /opt/local/share/doc/tmux/screen-keys.conf | |
| # /opt/local/share/doc/tmux/vim-keys.conf | |
| # | |
| # URLs to read: | |
| # |
| #!/bin/bash | |
| PASTEL='{ | |
| "Ansi 0 Color" = { | |
| "Blue Component" = 0.3097887; | |
| "Green Component" = 0.3097887; | |
| "Red Component" = 0.3097887; | |
| }; | |
| "Ansi 1 Color" = { | |
| "Blue Component" = 0.3764706; |