...
Documentation of the full process is on the Atlas support website. Emory is an Atlas-hosted PCI environment.
Workflow:
- Work from the FORKED repo, AtlasSystems/hosting-aeon-emorysb. Clone this repo to make code updates.
- Within each Repo, there are FOUR copies of the fileset. Each of these need to be changed within the folders:
- Aeon
- Aeon_Testweb
- nonshib
- nonshib_Testweb
...
- 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 from FORKED <main> to original <main>.
- 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).
- When everything is live on emorysb, let Elizabeth know so she can do UAT.
- Then, do a PR from hosting-aeon-emorysb<main> to hosting-aeon-emory<main> ← as of 01/17/23, waiting to hear back from Aeon to ensure this is correct workflow to get changes to production.
Any questions, feel free to ask Clare Barton.