Content Comparison

...

1. Work from the FORKED repo, AtlasSystems/hosting-aeon-emorysb. Clone this repo to make code updates.
2. Within each Repo, there are FOUR copies of the fileset. Each of these need to be changed within the folders:
   
   1. Aeon
   2. Aeon_Testweb
   3. nonshib
   4. nonshib_Testweb
3. However, they only want PRs FROM AtlasSystems/hosting-aeon-emorysb<main> TO AtlasSystems-Prod/hosting-aeon-emorysb<main>. No PRing from feature branch to main repo. Merge feature branch into the forked repo, AtlasSystems/hosting-aeon-emorysb, then do PR. The forks are the only ones we have write access to. 
4. Then do PR from FORKED <main> to original <main>. 
5. When PR is submitted, there are some automatic tests that run. A comment will appear in the PR with the results of the tests. Check those out to see if there are any necessary changes. It seems like the reviewers will kick the PR back if there are critical issues, but not necessarily for warnings or suggestions (even though the suggestions can be things you would want fixed before it goes live, so definitely check them out). 
6. When everything is live on prod sandbox, let Elizabeth know so she can do UAT.
7. Copy updated files from sb-fork to branch main-fork,  in theory it should be ok to do a bulk copy of everything, but in practice sometimes they are not exactly the same, so proceed with caution, compare carefully. ← hopefully will be updating this to push to additional remote prod fork as of 01312023 conversation w/ Collin
8. Merge feature branch with copied files to main-fork main branch. 
9. Then, do a PR from prod-fork AS/h-a-e<main> to production system AS-P/h-a-e<main>.

...