Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 36c4d2b

Browse filesBrowse files
ArturoAmorQArturoAmorQogriselStefanieSenger
authored andcommitted
DOC Add guidelines for automated contributions (#29287)
Co-authored-by: ArturoAmorQ <arturo.amor-quiroz@polytechnique.edu> Co-authored-by: Olivier Grisel <olivier.grisel@ensta.org> Co-authored-by: Stefanie Senger <91849487+StefanieSenger@users.noreply.github.com>
1 parent 5eaa957 commit 36c4d2b
Copy full SHA for 36c4d2b

File tree

1 file changed

+20
-0
lines changed
Filter options

1 file changed

+20
-0
lines changed

‎doc/developers/contributing.rst

Copy file name to clipboardExpand all lines: doc/developers/contributing.rst
+20Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -102,6 +102,16 @@ and follows the decision-making process outlined in :ref:`governance`.
102102
Look for issues marked "help wanted" or similar. Helping these projects may help
103103
scikit-learn too. See also :ref:`related_projects`.
104104

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+
105115
Submitting a bug report or a feature request
106116
============================================
107117

@@ -181,6 +191,16 @@ Contributing code
181191
so far. In order to claim an issue for yourself, please comment exactly
182192
``/take`` on it for the CI to automatically assign the issue to you.
183193

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+
184204
Video resources
185205
---------------
186206
These videos are step-by-step introductions on how to contribute to

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.