add core files

Author: GrantBirki

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @GrantBirki

.gitignore

@@ -0,0 +1,21 @@
+# vscode
+.vscode
+
+# Dependency directory
+node_modules/
+
+# Coverage directory used by tools like istanbul
+coverage
+
+# Optional npm cache directory
+.npm
+
+# Optional eslint cache
+.eslintcache
+
+# OS metadata
+.DS_Store
+Thumbs.db
+
+# Extra
+tmp/

.node-version

@@ -0,0 +1 @@
+18.9.0

CONTRIBUTING.md

@@ -0,0 +1,43 @@
+# Contributing 💻
+
+All contributions are welcome and greatly appreciated!
+
+## Steps to Contribute 💡
+
+> Check the `.node-version` file in the root of this repo so see what version of Node.js is required for local development - note, this can be different from the version of Node.js which runs the Action on GitHub runners. It is suggested to download [nodenv](https://github.com/nodenv/nodenv) which uses this file and manages your Node.js versions for you
+
+1. Fork this repository
+2. Commit your changes
+3. Test your changes (learn how to test below)
+4. Open a pull request back to this repository
+    > Make sure to run `npm run all` as your final commit!
+5. Notify the maintainers of this repository for peer review and approval
+6. Merge!
+
+The maintainers of this repository will create a new release with your changes so that everyone can use the new release and enjoy the awesome features of this Action
+
+## Testing 🧪
+
+This project requires **100%** test coverage
+
+### Running the test suite (required)
+
+Simply run the following command to execute the entire test suite:
+
+```bash
+npm run test
+```
+
+> Note: this requires that you have already run `npm install`
+
+### Testing FAQs 🤔
+
+Answers to questions you might have around testing
+
+Q: Why do I have to commit my changes to `main`?
+
+A: The `on: issue_comment` workflow only uses workflow files from the `main` branch by design - [learn more in the branch-deploy repo](https://github.com/github/branch-deploy#security-)
+
+Q: How can I test my changes once my PR is merged and *before* a new release is created?
+
+A: You should create a repo like [this one](https://github.com/GrantBirki/actions-sandbox) that uses `github/command@main` as the Action version and test your changes there

badges/coverage.svg

@@ -0,0 +1,30 @@
+#!/bin/bash
+
+# Usage:
+# script/release
+
+# COLORS
+OFF='\033[0m'
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+BLUE='\033[0;34m'
+
+latest_tag=$(git describe --tags $(git rev-list --tags --max-count=1))
+echo -e "The latest release tag is: ${BLUE}${latest_tag}${OFF}"
+read -p 'New Release Tag (vX.X.X format): ' new_tag
+
+tag_regex='^v\d\.\d\.\d$'
+echo "$new_tag" | grep -P -q $tag_regex
+
+if [[ $? -ne 0 ]]; then
+    echo "Tag: $new_tag is valid"
+fi
+
+git tag -a $new_tag -m "$new_tag Release"
+
+echo -e "${GREEN}OK${OFF} - Tagged: $new_tag"
+
+git push --tags
+
+echo -e "${GREEN}OK${OFF} - Tags pushed to remote!"
+echo -e "${GREEN}DONE${OFF}"