Update Repo Naming (2/3)

[zacharyrobin]

Describe your changes

REMS -> rems-admin 
crd-request-generator -> request-generator 

• Updated documentation
• Updated paths for new repo names path in docker files and files that reference it

Need to update Docker Hub to reflect correct repository path

No action is needed unless you are running dockerized version. Operations targeting the previous location will continue to function as if made on the new location. If you want you can remove these repositories and reclone them to avoid confusion:

git clone https://github.com/mcode/request-generator.git%60
git clone https://github.com/mcode/rems-admin.git

Or just update local clones to point to the new directory url (not needed but good practice to avoid confusion.

In /REMS
git remote set-url origin https://github.com/mcode/rems-admin.git

In /crd-request-generator
git remote set-url origin https://github.com/mcode/request-generator.git

Issue ticket number and Jira link

REMS-495

Checklist before requesting a review

• I have performed a self-review of my code
• Ensure the target / base branch for any feature PR is set to dev not main (the only exception to this is releases from dev and hotfix branches)

Checklist for conducting a review

• Review the code changes and make sure they all make sense and are necessary.
• Pull the PR branch locally and test by running through workflow and making sure everything works as it is supposed to.

Workflow

Owner of the Pull Request will be responsible for merge after all requirements are met, including approval from at least one reviewer. Additional changes made after a review will dismiss any approvals and require re-review of the additional updates. Auto merging can be enabled below if additional changes are likely not to be needed. The bot will auto assign reviewers to your Pull Request for you.