-
Notifications
You must be signed in to change notification settings - Fork 1
Update docs for Jan 2024 Connectathon #89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
avirgulto
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good
ecf0c49 to
fbd57d2
Compare
fbd57d2 to
a85279d
Compare
a85279d to
94d48fa
Compare
|
@avirgulto sorry for the giant diffs- just rebased off dev and cherry-picked/edited a bunch of commits just to get Rob's PR changes from da1baef in. The only real changes were adjusting the |
avirgulto
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, pulled down and ran and everything works as expected
Describe your changes
Updated documentation, removing unused auto-assign GitHub workflow, and alphabetized .env file
Issue ticket number and Jira link
https://jira.mitre.org/browse/REMS-556
Checklist before requesting a review
devnot main (the only exception to this is releases fromdevand hotfix branches)Checklist for conducting a review
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.