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: CONTRIBUTING.md
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,9 @@ Contributions via pull requests are much appreciated. Before sending us a pull r
23
23
1. You are working against the latest source on the *main* branch.
24
24
2. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
25
25
3. You open an issue to discuss any significant work - we would hate for your time to be wasted.
26
+
4.4. You are not mixing substantial refactoring changes in with functional changes.
27
+
1. If refactoring is desirable, publish a separate refactoring PR first, followed by a functional change PR. This will ensure safe and efficient reviews.
28
+
2. PRs that do not meet these expectations will be rejected.
26
29
27
30
To send us a pull request, please:
28
31
@@ -32,6 +35,7 @@ To send us a pull request, please:
32
35
4. Commit to your fork using clear commit messages.
33
36
5. Send us a pull request, answering any default questions in the pull request interface.
34
37
6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
38
+
7. Please do not squash commits between revisions, this makes review challenging, as the diff between revisions is harder to find and review.
35
39
36
40
GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
37
41
[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
0 commit comments