#7 Setup CI/CD to run for PRs to main

[cstroliadavis]

Issue No:

closes GH-7

Issue Type:

• [ ] Architecture (ensure that the architecture lead is included in the reviewers
• [ ] Bug
• [ ] Chore
• [ ] Clean-up
• [X] DevOps (ensure that the devops lead is included in the reviewers)
• [ ] Documentation
• [ ] Feature Request (ensure that the team lead and architecture lead are included in reviewers if this involves any core functionality changes)

Description

Basically a stub CI/CD script that should log a test message and return a success status

How Has This Been Tested?

In all honesty, I have not tested this. If there is a way of doing so, outside of Github, I don't yet know what it is. For now, this project is small and no one relies on it, so I am accepting the potential of failure from the check-in as it will not affect others. If we get to a point where more would be affected, I would likely attempt to use this on PRs to a different branch to test it out, first.

Checklist:

• [x] This is not a code change, or my code follows the style guidelines of this project and I have run eslint
• [x] I have performed a self-review of my own changes
• [x] I have not added or modified any publicly available objects or methods or I have added appropriate jsdoc comments
• [x] I did not make any abnormal changes or I have added comments describing "why" I did things differently than usual.
• [x] This is a documentation update, or else I have made corresponding changes to the documentation
• [x] My changes generate no new errors or warnings
• [x] I have not added any code the requires unit test updates, or I have added unit tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes

[cstroliadavis]

Oh, good news, this pipeline ran on this merge, so I was able to test and verify it before actually merging it. Yay.