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
+30-11Lines changed: 30 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,18 @@
1
1
<!--
2
2
Thank you for contributing to this project! You must fill out the information below before we can review this pull request.
3
+
3
4
By explaining why you're making a change (or linking to an issue) and what changes you've made, we can triage your pull
4
5
request to the best possible team for review.
5
6
6
7
💡 **TIP**
7
-
Remember that you can always open a PR in draft status and fill all the information afterwards.
8
+
Remember that you can always open a PR in draft status and fill all the information afterward.
8
9
9
-
Opening a PR in draft allows other team members to knwo that you are working on this change, and let's you have a
10
+
Opening a PR in draft lets other team members know you're working on this change, and gives you a
10
11
place to track your work in progress.
11
12
12
-
When opening PRs in Draft, don't assign reviewers until the PR is ready for review. Once you are confortable with the
13
-
status of the PR and all the tests and CI is green, you can assign the reviewers to start the review process.
13
+
When opening PRs in Draft, **don't assign reviewers until the PR is ready for review**.
14
+
15
+
Once you are comfortable with the status of the PR and all the tests and CI is green, you can assign the reviewers to start the review process.
14
16
-->
15
17
16
18
### Summary 💡
@@ -19,24 +21,25 @@ status of the PR and all the tests and CI is green, you can assign the reviewers
19
21
20
22
<!--
21
23
If there's an existing issue for your change, please link to it below inserting a link or the issue number.
24
+
22
25
If there's _not_ an existing issue, please open one first if the problem you are solving needs to be clearly identified,
23
-
for example is an error message that other users could get and google it.
26
+
for example, an error message that other users could get and search for online.
24
27
-->
25
28
Closes:
26
29
27
30
28
-
<!-- If this PR is related to changes produced in other repos, like a Module, please link them below. -->
31
+
<!-- If this PR is related to changes produced in other repos, like a Module or the distribution, please link them below. -->
29
32
Relates:
30
33
31
34
32
35
### Description 📝
33
36
34
37
<!--
35
38
Let us know what you are changing. Share anything that could provide the most context.
36
-
Feel free to add screenshots, code examples, the Description could end up in the release notes to help users adopt
37
-
the new feature or changes that you are introducing.
38
39
39
-
Expand on the reasoning behind some decision that you could have made to help reviewers understand the diff in the PR.
40
+
Feel free to add screenshots and code examples. The description could end up in the release notes to help users adopt the new feature or changes that you are introducing.
41
+
42
+
Expand on the reasoning behind any decisions you made to help reviewers understand the diff in the PR.
40
43
41
44
-->
42
45
@@ -53,8 +56,9 @@ If this PR introduces Breaking Changes, please include all the relevant informat
53
56
54
57
<!--
55
58
Create a checklist with all the tests that you performed on your changes, being manual or automated.
56
-
If you are opening a Draft PR, you can use the checklist to track the tests that you want to do and mark them once you
57
-
have performed them.
59
+
60
+
If you are opening a Draft PR, you can use the checklist to track the tests that you want to do and mark them once you have performed them.
61
+
58
62
Example:
59
63
60
64
- [ ] Tested the change with SD version X.Y.Z
@@ -67,3 +71,18 @@ Example:
67
71
If there's any future work that could improve or extend on the work you've done in this PR you can mention it so
68
72
this PR can be used as context for that.
69
73
-->
74
+
75
+
### Self-assessment checklist 🏁
76
+
77
+
> [!IMPORTANT]
78
+
> Make sure that you completed this checklist before asking for review.
79
+
>
80
+
> PRs that do not have this checklist ready won't be reviewed.
81
+
82
+
-[ ] My PR has a clear scope and does not mix together several unrelated changes
83
+
-[ ] I've updated the `docs/releases/unreleased.md` file (or equivalent)
84
+
-[ ] I've tested the proposed changes and wrote the tests performed in the section above
85
+
-[ ] My branch is up-to-date with the target branch and there are no conflicts
86
+
-[ ] I've considered all the different cluster kinds (KFDDistribution, OnPremises, EKSCluster, Immutable) that may be affected by this change
0 commit comments