8000 DOC improve titles for saved replies · scikit-learn/scikit-learn@c91699d · GitHub
[go: up one dir, main page]

Skip to content

Commit c91699d

Browse files
committed
DOC improve titles for saved replies
1 parent e260119 commit c91699d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc/developers/tips.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -140,7 +140,7 @@ Issue/Comment: Linking to code
140140

141141
Friendly advice: for clarity's sake, you can link to code like [this](https://help.github.com/articles/creating-a-permanent-link-to-a-code-snippet/).
142142

143-
Issue/Comment: Linking to issues
143+
Issue/Comment: Linking to comments
144144
::
145145

146146
Please use links to comments, which make it a lot easier to see what you are referring to, rather than just linking to the issue. See [this](https://stackoverflow.com/questions/25163598/how-do-i-reference-a-specific-issue-comment-on-github) for more details.
@@ -155,7 +155,7 @@ PR-NEW: Fix #
155155

156156
Please use "Fix #issueNumber" in your PR description (and you can do it more than once). This way the associated issue gets closed automatically when the PR is merged. For more details, look at [this](https://github.com/blog/1506-closing-issues-via-pull-requests).
157157

158-
PR-NEW or Issue:
158+
PR-NEW or Issue: Maintenance cost
159159
::
160160

161161
Every feature we include has a [maintenance cost](http://scikit-learn.org/dev/faq.html#why-are-you-so-selective-on-what-algorithms-you-include-in-scikit-learn). Our maintainers are mostly volunteers. For a new feature to be included, we need evidence that it is often useful and, ideally, [well-established](http://scikit-learn.org/dev/faq.html#what-are-the-inclusion-criteria-for-new-algorithms) in the literature or in practice. That doesn't stop you implementing it for yourself and publishing it in a separate repository, or even [scikit-learn-contrib](http://scikit-learn-contrib.github.io).

0 commit comments

Comments
 (0)
0