Conversation
smalho01
assigned
rdingwell,
plarocque4 and
kennyEung and unassigned
rdingwell and
plarocque4
smalho01
commented
May 15, 2023
| 'REMS Requirement Lookup', | ||
| 'REMS Requirement Lookup', | ||
| prefetch | ||
| ); |
Collaborator
Author
There was a problem hiding this comment.
skipped for now, will make a JIRA task to fill back in
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Describe your changes
This will need to be pushed up to main after as well and added to the REMSv0.10 release since its a breaking change for the dev environment on that tag, which an external stakeholder may try to install with. Run with mcode/pims#23 and mcode/rems-cds-hooks#4
Issue ticket number and Jira link
https://jira.mitre.org/browse/REMS-395
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.