Skip to content

docs: PR template update with assurance guidance#1836

Draft
rfk-nc wants to merge 2 commits intomainfrom
docs/dtoss-12158-pr-template
Draft

docs: PR template update with assurance guidance#1836
rfk-nc wants to merge 2 commits intomainfrom
docs/dtoss-12158-pr-template

Conversation

@rfk-nc
Copy link
Contributor

@rfk-nc rfk-nc commented Feb 11, 2026

Description

Add new Assurances section tot he PR template to assist collating required assurance evidence when PRs are released.

In PR edit mode user will see this:
image

And when saved the new section (if left unfilled) will look like:
image

Context

Improves clarity of requirements.

Type of changes

  • Refactoring (non-breaking change)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would change existing functionality)
  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • I am familiar with the contributing guidelines
  • I have followed the code style of the project
  • I have added tests to cover my changes
  • I have updated the documentation accordingly
  • This PR is a result of pair or mob programming

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

  • I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

@github-actions
Copy link

Unit Test Results

✔️ Tests 975 / 975 - passed in 66.1s
📝 Coverage 47.76%
📏 4755 / 10228 lines covered 🌿 1167 / 2172 branches covered
🔍 click here for more details

✏️ updated for commit 88d74c7

@sonarqubecloud
Copy link


<!-- A description of the risks associated with the change -->

### Mittigations to the risks associated with the change
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sp

- [ ] UI before/after screenshots
- [ ] Other manual testing (description of manual testing performed and results)

### Risks associated with the change
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these risks that are logged in Jira?


### Clinical assurance-friendly description of the change

<!-- A description of the change that is suitable for a clinical audience -->
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there an example of what this type of description is?


## Assurances

### Clinical assurance-friendly description of the change
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we better off makng one description and ensuring it's readable for all audiences?

@rfk-nc rfk-nc marked this pull request as draft February 11, 2026 15:59
@rfk-nc rfk-nc added the Non-functional change A change that does not change any functions. Mainly config or database changes label Feb 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Non-functional change A change that does not change any functions. Mainly config or database changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants