docs: testing Commit process

Changes

Made an empty file to test the commit/PR Process. Tailored to be understood by maintainer

resolve #30

@kelly-sovacool can you reveiw kopardev any comments?

(~Strikethrough~ any points that are not applicable.)

[x] This comment contains a description of changes with justifications, with any relevant issues linked.
[ ] ~Write unit tests for any new features, bug fixes, or other code changes.~
[x] Update the docs if there are any API changes (roxygen comments, vignettes, readme, etc.).
[ ] ~Update NEWS.md with a short description of any user-facing changes and reference the PR number. Guidelines: https://keepachangelog.com/en/1.1.0/~
[x] Run devtools::check() locally and fix all notes, warnings, and errors.