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
+15-7Lines changed: 15 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,12 @@
1
1
🚨 **IMPORTANT: Please do not create a Pull Request without creating an issue first.**
2
2
3
-
_Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request._
3
+
_Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of
4
+
the pull request._
4
5
5
6
## Description
6
7
7
-
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
8
+
Please include a summary of the change and which issue is fixed. Please also include relevant
9
+
motivation and context. List any dependencies that are required for this change.
8
10
9
11
Related # (issue)
10
12
@@ -18,16 +20,19 @@ Please delete options that are not relevant.
18
20
19
21
-[ ] Bug fix (non-breaking change which fixes an issue)
20
22
-[ ] New feature (non-breaking change which adds functionality)
21
-
-[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
23
+
-[ ] Breaking change (fix or feature that would cause existing functionality to not work as
24
+
expected)
22
25
-[ ] This change requires a documentation update
23
26
24
27
## Screenshots/Sandbox (if appropriate/relevant):
25
28
26
-
Adding links to sandbox or providing screenshots can help us understand more about this PR and take action on it as appropriate
29
+
Adding links to sandbox or providing screenshots can help us understand more about this PR and take
30
+
action on it as appropriate
27
31
28
32
## How Has This Been Tested?
29
33
30
-
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
34
+
Please describe the tests that you ran to verify your changes. Provide instructions so we can
35
+
reproduce. Please also list any relevant details for your test configuration
31
36
32
37
-[ ] Test A
33
38
-[ ] Test B
@@ -40,7 +45,9 @@ Please describe the tests that you ran to verify your changes. Provide instructi
40
45
41
46
## Checklist:
42
47
43
-
-[ ] I have followed the [CONTRIBUTING](https://github.com/the-guild-org/Stack/blob/master/CONTRIBUTING.md) doc and the style guidelines of this project
48
+
-[ ] I have followed the
49
+
[CONTRIBUTING](https://github.com/the-guild-org/Stack/blob/master/CONTRIBUTING.md) doc and the
50
+
style guidelines of this project
44
51
-[ ] I have performed a self-review of my own code
45
52
-[ ] I have commented my code, particularly in hard-to-understand areas
46
53
-[ ] I have made corresponding changes to the documentation
@@ -51,4 +58,5 @@ Please describe the tests that you ran to verify your changes. Provide instructi
51
58
52
59
## Further comments
53
60
54
-
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
61
+
If this is a relatively large or complex change, kick off the discussion by explaining why you chose
62
+
the solution you did and what alternatives you considered, etc...
0 commit comments