@@ -102,6 +102,16 @@ and follows the decision-making process outlined in :ref:`governance`.
102
102
Look for issues marked "help wanted" or similar. Helping these projects may help
103
103
scikit-learn too. See also :ref: `related_projects `.
104
104
105
+ Automated Contributions Policy
106
+ ==============================
107
+
108
+ Please refrain from submitting issues or pull requests generated by
109
+ fully-automated tools. Maintainers reserve the right, at their sole discretion,
110
+ to close such submissions and to block any account responsible for them.
111
+
112
+ Ideally, contributions should follow from a human-to-human discussion in the
113
+ form of an issue.
114
+
105
115
Submitting a bug report or a feature request
106
116
============================================
107
117
@@ -181,6 +191,16 @@ Contributing code
181
191
so far. In order to claim an issue for yourself, please comment exactly
182
192
``/take `` on it for the CI to automatically assign the issue to you.
183
193
194
+ To maintain the quality of the codebase and ease the review process, any
195
+ contribution must conform to the project's :ref: `coding guidelines
196
+ <coding-guidelines>`, in particular:
197
+
198
+ - Don't modify unrelated lines to keep the PR focused on the scope stated in its
199
+ description or issue.
200
+ - Only write inline comments that add value and avoid stating the obvious: explain
201
+ the "why" rather than the "what".
202
+ - **Most importantly **: Do not contribute code that you don't understand.
203
+
184
204
Video resources
185
205
---------------
186
206
These videos are step-by-step introductions on how to contribute to
0 commit comments