You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/pull_request_template.md
+39-2Lines changed: 39 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,14 @@
1
1
## Description of Changes
2
2
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
4
6
5
7
## Issue Link
6
8
7
9
This PR addresses the following issues:
8
10
9
-
-REPLACE THIS TEXT WITH A LIST OF ISSUES, if applicable
11
+
-LINK TO RELEVANT ISSUES, IF APPLICABLE
10
12
11
13
## Security
12
14
@@ -17,6 +19,41 @@ This PR addresses the following issues:
17
19
18
20
Describe briefly what security risks you considered, why they don't apply, or how they've been mitigated.
19
21
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
0 commit comments