Feat(hm/conf/git): Reword git commit template

3 files changed, 73 insertions, 76 deletions

diff --git a/home-manager/config/git/default.nix b/home-manager/config/git/default.nix
index 47710718..c01738e0 100644
--- a/home-manager/config/git/default.nix
+++ b/home-manager/config/git/default.nix
@@ -1,79 +1,4 @@
-{
-  config,
-  pkgs,
-  ...
-}: let
-  gitIgnoreFile = pkgs.writeText "git_ignore.git" ''
-    Session.vim
-  '';
-  gitTemplateFile =
-    pkgs.writeText "git_template.git"
-    ''
-      # Title: Summary, imperative, start upper case, don't end with a period
-      # If applied, this commit will <your Title>
-
-      # Body: Explain *what* and *why* (not *how*).
-
-
-      # BREAKING CHANGE: <description>
-      # Fixes: #
-      # Refs: #
-      # Co-authored-by: <name> <email>
-
-
-
-      # Convention Commits (https://www.conventionalcommits.org/en/v1.0.0/):
-      #  feat: [Features] -> MINOR version bump
-      #      A new feature
-      #
-      #  fix: [Bug Fixes] -> PATCH version bump
-      #      A bug fix
-      #
-      #  append '!' after the type/scope: [Breaking Change] -> MAJOR version bump
-      #    A breaking API change
-      #
-      #  docs: [Documentation]
-      #      Documentation only changes
-      #
-      #  style: [Styles]
-      #      Changes that do not affect the meaning of the code
-      #      (white-space, formatting, missing semi-colons, etc)
-      #
-      #  refactor: [Code Refactoring]
-      #      A code change that neither fixes a bug nor adds a feature
-      #
-      #  perf: [Performance Improvements] -> PATCH version bump
-      #      A code change that improves performance
-      #
-      #  test: [Tests]
-      #      Adding missing tests or correcting existing tests
-      #
-      #  build: [Builds] -> PATCH version bump
-      #      Changes that affect the build system or external dependencies
-      #      (example scopes: gulp, broccoli, npm)
-      #
-      #  ci: [Continuous Integrations]
-      #      Changes to our CI configuration files and scripts
-      #      (example scopes: Travis, Circle, BrowserStack, SauceLabs)
-      #
-      #  chore: [Chores]
-      #      Other changes that don't modify src or test files
-      #
-      #  reverts: [Reverts]
-      #      Reverts a previous commit
-
-      # How to Write a Git Commit Message:
-      # [https://chris.beams.io/posts/git-commit/] -> https://cbea.ms/git-commit/
-      #
-      # 1. Separate subject from body with a blank line
-      # 2. Limit the subject line to 50 characters
-      # 3. Capitalize the subject line
-      # 4. Do not end the subject line with a period
-      # 5. Use the imperative mood in the subject line
-      # 6. Wrap the body at 72 characters
-      # 7. Use the body to explain *what* and *why* vs. *how*
-    '';
-
+{...}: let
   gitConfig = {
     core = {
       excludesFile = "${gitIgnoreFile}";
@@ -92,6 +17,8 @@
       template = "${gitTemplateFile}";
     };
   };
+  gitIgnoreFile = ./git_ignore.git;
+  gitTemplateFile = ./git_template.git;
 in {
   programs.git = {
     enable = true;
diff --git a/home-manager/config/git/git_ignore.git b/home-manager/config/git/git_ignore.git
new file mode 100644
index 00000000..8f29815e
--- /dev/null
+++ b/home-manager/config/git/git_ignore.git
@@ -0,0 +1,4 @@
+# default nvim Session file name
+Session.vim
+
+# vim: ft=gitignore
diff --git a/home-manager/config/git/git_template.git b/home-manager/config/git/git_template.git
new file mode 100644
index 00000000..9621698d
--- /dev/null
+++ b/home-manager/config/git/git_template.git
@@ -0,0 +1,66 @@
+
+# Title: Summary, imperative, start upper case, don't end with a period
+# If applied, this commit will <your Title>
+
+# Body: Explain *what* and *why* (not *how*).
+
+
+# BREAKING CHANGE: <description>
+# Fixes: #
+# Refs: #
+# Co-authored-by: <name> <email>
+
+
+
+# Convention Commits (https://www.conventionalcommits.org/en/v1.0.0/ or https://github.com/angular/angular/blob/85b4941be137a2fcdc664dc870e408dd72ad7de7/CONTRIBUTING.md#commit):
+#  Feat: [Features] -> MINOR version bump
+#      A new feature
+#
+#  Fix: [Bug Fixes] -> PATCH version bump
+#      A bug fix
+#
+#  append '!' after the type/scope: [Breaking Change] -> MAJOR version bump
+#      A breaking API change
+#
+#  Docs: [Documentation]
+#      Documentation only changes
+#
+#  Style: [Styles]
+#      Changes that do not affect the meaning of the code
+#      (white-space, formatting, missing semi-colons, etc)
+#
+#  Refactor: [Code Refactoring]
+#      A code change that neither fixes a bug nor adds a feature
+#
+#  Perf: [Performance Improvements] -> PATCH version bump
+#      A code change that improves performance
+#
+#  Test: [Tests]
+#      Adding missing tests or correcting existing tests
+#
+#  Build: [Builds] -> PATCH version bump
+#      Changes that affect the build system or external dependencies
+#      (example scopes: gulp, broccoli, npm)
+#
+#  Ci: [Continuous Integrations]
+#      Changes to our CI configuration files and scripts
+#      (example scopes: Travis, Circle, BrowserStack, SauceLabs)
+#
+#  Chore: [Chores]
+#      Other changes that don't modify src or test files
+#
+#  Reverts: [Reverts]
+#      Reverts a previous commit
+
+# How to Write a Git Commit Message:
+# [https://chris.beams.io/posts/git-commit/] -> https://cbea.ms/git-commit/
+#
+# 1. Separate subject from body with a blank line
+# 2. Limit the subject line to 50 characters
+# 3. Capitalize the subject line
+# 4. Do not end the subject line with a period
+# 5. Use the imperative mood in the subject line
+# 6. Wrap the body at 72 characters
+# 7. Use the body to explain *what* and *why* vs. *how*
+#
+# vim: ft=gitcommit