New: [ELI-426] - _plus1day Cohorts#47
Merged
adam-wallernhs1 merged 7 commits intomainfrom Oct 2, 2025
Merged
Conversation
…age tomorrow or yesterday - added TCs for ELI-426 - made a minor chnage to the vita integration test config to ensure virtual N was orking as expected
…age tomorrow or yesterday - added TCs for ELI-426 - made a minor change to the vita integration test config to ensure virtual N was working as expected
Contributor
|
This branch is work on a ticket in an NHS England JIRA Project. Here is a handy link to the ticket: |
seansteberisal
previously approved these changes
Oct 1, 2025
seansteberisal
approved these changes
Oct 2, 2025
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
2 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.
Summary
Remove items from this list if they are not relevant. Remove this line once this has been done
Details
def _resolve_placeholder_valueanddef _resolve_age_placeholderto allow theDATE_AGE_65-TOMORROWandDATE_AGE_65-YESTERDAYreplacements to aid in boundary testingPull Request Naming
Pull requests should be named using the following format:
Tag can be one of:
Fix- for a bug fix. (Patch release)Update- either for a backwards-compatible enhancement or for a rule change that adds reported problems. (Patch release)New- implemented a new feature. (Minor release)Breaking- for a backwards-incompatible enhancement or feature. (Major release)Docs- changes to documentation only. (Patch release)Build- changes to build process only. (No release)Upgrade- for a dependency upgrade. (Patch release)Chore- for refactoring, adding tests, etc. (anything that isn't user-facing). (Patch release)If the current release is x.y.z then
Correct tagging is necessary for our automated versioning and release process (Release).
The description of your pull request will be used as the commit message for the merge, and also be included in the changelog. Please ensure that your title is sufficiently descriptive.
Rerunning Checks
If you need to rename your pull request, you can restart the checks by either:
git commit --allow-empty -m 'trigger build' git pushRerunning the checks from within the pull request will not use the updated title.