Move all template repo files into their own directory, and add ADR describing why

Author: deadlydog

docs/ArchitectureDecisionRecords/001-Use-separate-repo-files-for-template.md

@@ -0,0 +1,43 @@
+# 001 - Use separate repo files for template
+
+## Status
+
+Accepted 2024-02-25
+
+## Context
+
+When I originally conceived of this template repository I was just going to have the template files be this actual repo's files, and I started out the implementation that way.
+When writing the script that would be used to initialize the template repository with the user's module information, I had to keep track of which files in the repo would need to be updated (e.g. the new module directory and files, License, Changelog, Smoke Tests).
+This had me questioning if it would be better to use totally separate files for all of the template files, and just have the initialization script overwrite all of the repo contents with the template files.
+
+## Options Considered
+
+1. Use this repo's files as the template files.
+1. Use separate files for all of the template files (stored in their own directory).
+
+### Use this repo's files as the template files
+
+Pros:
+
+- Fewer files in the repo.
+- Possibly less confusing to the user, as it follows the traditional idea of what a template repository is.
+e.g. the files in the repo are where you start from.
+
+### Use separate files for all of the template files
+
+Pros:
+
+- Less logic in the initialization script, as we don't need to keep track of which files are for the repo and which are for the template.
+- Easier to update the template files without having to worry about the repo files.
+- Less confusion about which files are for this repo vs. which are for the template.
+- Allows users to more easily create their own custom template files easier if they want to; they just need to update the template files.
+- Allows for the PowerShell module to be able to create new starter repos, rather than having to clone the GitHub repo template.
+
+Cons:
+
+- Some of the files in the repo will be duplicates of the template files, so when adding new feature/changes we may need to remember to make them in both this repo and the template files.
+
+## Decision
+
+We are going to store all of the template repo files in their own directory, as this separation makes it easier to understand which files are part of the template and which are part of this repo.
+It also allows for users to more easily create their own custom templates, and to use the PowerShell module to create new starter repos.

src/Template.PowerShell.ScriptModule/TemplateRepoFiles/.cspell.json

@@ -0,0 +1,24 @@
+// This is the configuration file for cspell (code spell check).
+// Use this to define legitimate words not in the dictionary, and other words the spellcheck should ignore.
+// Used by the streetsidesoftware.code-spell-checker VS Code extension and streetsidesoftware/cspell-action@v3 GitHub Action.
+// For more information on configuration, see https://cspell.org/configuration/.
+{
+	"version": "0.2",
+	"language": "en",
+	"ignorePaths": [],
+	"words": [
+		"hashtable"
+	],
+	"ignoreWords": [
+		"CICD", // Continuous Integration/Continuous Deployment
+		"CODEOWNERS", // GitHub CODEOWNERS
+		"Codespace", // GitHub Codespaces
+		"Codespaces", // GitHub Codespaces
+		"devcontainer", // VS Code devcontainer
+		"Hmmss", // Time format
+		"jacoco", // Java code coverage
+		"madrapps", // GitHub action author
+		"nunit", // .NET unit testing framework
+		"pwsh" // PowerShell Core
+	]
+}

src/Template.PowerShell.ScriptModule/TemplateRepoFiles/.editorconfig

@@ -0,0 +1,26 @@
+# This file should only include settings that affect the physical contents of the file, not just how it appears in an editor.
+# Do not include personal preference presentation settings like a tab's `indent_size` in this file; those should be specified
+# in a parent .editorconfig file outside of the repository.
+# v1.7
+
+# Ensure that personal preference presentation settings can be inherited from parent .editorconfig files.
+root = false
+
+#### Core EditorConfig Options ####
+
+[*]
+charset = utf-8
+indent_style = tab
+end_of_line = crlf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+# For some languages, the number of spaces used for indentation matters.
+[*.{tf,md,psd1,pp,yml,yaml}]
+indent_style = space
+indent_size = 2
+
+
+#### .NET Coding Conventions ####
+
+csharp_style_namespace_declarations = file_scoped

src/Template.PowerShell.ScriptModule/TemplateRepoFiles/.gitattributes

@@ -0,0 +1,41 @@
+# Use 'git add --renormalize .' to apply rules to files added to the repository before the .gitattributes file.
+
+# Have GitHub language statistics ignore generated files.
+#	More info: https://github.com/github-linguist/linguist/blob/master/docs/overrides.md
+#generatedFiles/** linguist-generated=true
+
+# Auto detect text files and perform LF normalization.
+* text=auto
+
+# Documents
+*.doc diff=astextplain
+*.DOC diff=astextplain
+*.docx diff=astextplain
+*.DOCX diff=astextplain
+*.dot diff=astextplain
+*.DOT diff=astextplain
+*.pdf diff=astextplain
+*.PDF diff=astextplain
+*.rtf diff=astextplain
+*.RTF diff=astextplain
+*.md text
+*.adoc text
+*.textile text
+*.mustache text
+*.csv text
+*.tab text
+*.tsv text
+*.sql text
+
+# Graphics
+*.png binary
+*.jpg binary
+*.jpeg binary
+*.gif binary
+*.tif binary
+*.tiff binary
+*.ico binary
+# SVG treated as an asset (binary) by default, but it's actually just a text file so let's treat it as one.
+#*.svg binary
+*.svg text
+*.eps binary

src/Template.PowerShell.ScriptModule/TemplateRepoFiles/.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# Auto-include these teams/individuals on all PRs.
+* @deadlydog

src/Template.PowerShell.ScriptModule/TemplateRepoFiles/.github/FUNDING.yml

@@ -0,0 +1,12 @@
+# These are supported funding model platforms
+
+github: deadlydog # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+otechie: # Replace with a single Otechie username
+custom: https://www.paypal.me/deadlydogDan # Replace with a single custom sponsorship URL

src/Template.PowerShell.ScriptModule/TemplateRepoFiles/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,46 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: 'Bug: '
+labels: ''
+assignees: ''
+
+---
+
+### Describe the bug
+
+A clear and concise description of what the bug is.
+
+### To reproduce
+
+Steps to reproduce the behavior:
+
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+### Expected behavior
+
+A clear and concise description of what you expected to happen.
+
+### Logs or error messages
+
+Any error messages or logs that might help us understand the problem.
+
+### Screenshots
+
+If applicable, add screenshots or video to help explain the problem.
+
+### System information
+
+Information about the system you are using where the bug occurred.
+
+- Device: (e.g. PC, iPhone6)
+- OS and version: (e.g. Windows 10, iOS 12.3.1)
+- Browser and version: (e.g. Chrome 121.0.6167.140, Safari 12.1.2)
+- Application version: (e.g. 1.0.6)
+
+### Additional information
+
+Add any other context or information about the problem or how to reproduce it.

src/Template.PowerShell.ScriptModule/TemplateRepoFiles/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,26 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: 'Feature Request: '
+labels: ''
+assignees: ''
+
+---
+
+### Is your feature request related to a problem? Please describe
+
+A clear and concise description of what the problem is.
+Ex. I'm always frustrated when '...'.
+Ex. I want to be able to '...'.
+
+### Describe the solution you'd like
+
+A clear and concise description of what you want to happen.
+
+### Describe alternatives you've considered
+
+A clear and concise description of any alternative solutions or features you've considered.
+
+### Additional context
+
+Add any other context or screenshots about the feature request here.

src/Template.PowerShell.ScriptModule/TemplateRepoFiles/.github/pull_request_template.md

@@ -0,0 +1,26 @@
+### Summary
+
+A brief summary of the change this PR brings.
+
+### Checklist
+
+Addresses issue #ISSUE_NUMBER (if applicable)
+
+- [ ] Tests have been added for this code change (if applicable)
+- [ ] Docs have been added or updated (if applicable)
+- [ ] Code format follows the project style
+- [ ] All new and existing tests passed
+
+### What type of changes does this PR include
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+
+### Describe the change in more detail
+
+What is the motivation for this change? What does it do? What problem does it solve?
+
+### Additional information
+
+Any other information about the change, such as screenshots, example flows, etc.