Skip to content

Commit 015cbb1

Browse files
authored
Incorporate new PR template sections.
1 parent b6755f5 commit 015cbb1

File tree

1 file changed

+39
-2
lines changed

1 file changed

+39
-2
lines changed

.github/pull_request_template.md

Lines changed: 39 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,14 @@
11
## Description of Changes
22

3-
REPLACE THIS TEXT WITH A DESCRIPTION OF YOUR CHANGES
3+
> Briefly describe the change, including justification for the change, ramifications for not doing the change, and any specific versions/configurations impacted.
4+
5+
TODO: REPLACE WITH YOUR DESCRIPTION
46

57
## Issue Link
68

79
This PR addresses the following issues:
810

9-
- REPLACE THIS TEXT WITH A LIST OF ISSUES, if applicable
11+
- LINK TO RELEVANT ISSUES, IF APPLICABLE
1012

1113
## Security
1214

@@ -17,6 +19,41 @@ This PR addresses the following issues:
1719

1820
Describe briefly what security risks you considered, why they don't apply, or how they've been mitigated.
1921

22+
## Change Control Board (CCB) Approval
23+
24+
> CCB approval is required when the change affects organizational processes (like vulnerability management or disaster recovery), or has the potential to impact availability, security, or privacy. See the CR process for more detailed assessment guidelines.
25+
26+
- [ ] This change does NOT require CCB approval.
27+
- [ ] This change DOES require CCB approval. Tag `@careevolution/ccb`.
28+
29+
## Testing/Validation
30+
31+
> Describe how we will know if the change is working as intended. Consider both pre-production testing and post-implementation validation, including environment/configuration details, if applicable.
32+
33+
TODO: REPLACE WITH YOUR TESTING/VALIDATION PLAN
34+
35+
## Backout Plan
36+
37+
> Describe how we will restore the system to its pre-change state if something goes wrong.
38+
39+
TODO: REPLACE WITH YOUR BACKOUT PLAN
40+
41+
## Implementation Notes
42+
43+
> Describe any special considerations for implementing the change: scheduling constraints, down-time planning, if a co-pilot is needed, etc.
44+
45+
TODO: REPLACE WITH IMPLEMENTATION NOTES
46+
47+
## Documentation Updates
48+
49+
> Describe any necessary updates. Consider both internal (wiki, checklists) and external (user guides, developer docs, customer communications) documentation.
50+
51+
- [ ] This change has no documentation impact.
52+
- [ ] This change impacts external documentation (API docs, user guides). Tag `@careevolution/mdhd-docs` or `@careevolution/api-docs`.
53+
- [ ] This change impacts internal documentation (procedures, security plans, wiki). Tag the owner.
54+
55+
TODO: REPLACE WITH A DESCRIPTION OF DOCUMENTATION UPDATES, if applicable
56+
2057
## Reviewers
2158

2259
- [ ] I have assigned the appropriate reviewer(s).

0 commit comments

Comments
 (0)