Skip to content

Commit 87c2206

Browse files
move entry around
1 parent 4ba8253 commit 87c2206

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

.github/CONTRIBUTING.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -66,10 +66,6 @@ When you file a pull request, you should add some tests to this file with this i
6666

6767
What numbers should be used for new tests? Numbers should be new relative to current master at the time of your PR. If another PR is merged before yours, then there may be a conflict, but that is no problem, as [a Committer will fix the test numbers when merging your PR](https://github.com/Rdatatable/data.table/pull/4731#issuecomment-768858134).
6868

69-
#### Performance testing
70-
71-
If your PR may have an effect on time/memory usage, please consider adding a performance test, either in the same PR, or a follow-up PR. See the [Performance testing](https://github.com/Rdatatable/data.table/wiki/Performance-testing) wiki page for details.
72-
7369
#### Using `test`
7470

7571
See [`?test`](https://rdatatable.gitlab.io/data.table/reference/test.html).
@@ -80,6 +76,10 @@ See [`?test`](https://rdatatable.gitlab.io/data.table/reference/test.html).
8076
1. **[Squashing Github pull requests into a single commit](http://eli.thegreenplace.net/2014/02/19/squashing-github-pull-requests-into-a-single-commit)**.
8177
1. **[Github help](https://help.github.com/articles/using-pull-requests/)** - you'll need the *fork and pull* model.
8278

79+
#### Performance testing
80+
81+
If your PR may have an effect on time/memory usage, please consider adding a performance test, either in the same PR, or a follow-up PR. See the [Performance testing](https://github.com/Rdatatable/data.table/wiki/Performance-testing) wiki page for details.
82+
8383
Minimal first time PR
8484
---------------------
8585

0 commit comments

Comments
 (0)