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
+13-9Lines changed: 13 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -322,13 +322,6 @@ message (e.g. "Bump version number"), save the file, and quit the
322
322
editor.
323
323
324
324
#### Step 11:
325
-
Push the release branch to GitHub.
326
-
327
-
```bash
328
-
git push origin release/v3.6.0
329
-
```
330
-
331
-
#### Step 12:
332
325
333
326
Run the PredictMD test suite on your local machine:
334
327
@@ -344,6 +337,13 @@ If you do not receive that message, then one or more of the tests failed.
344
337
**You may not proceed to the next step until all of the tests pass on your
345
338
local machine.**
346
339
340
+
#### Step 12:
341
+
Push the release branch to GitHub.
342
+
343
+
```bash
344
+
git push origin release/v3.6.0
345
+
```
346
+
347
347
#### Step 13:
348
348
Wait for all of the continuous integration (CI) tests to pass. You can
349
349
check on the status of the CI tests by going to
@@ -519,7 +519,11 @@ scroll down to find the release branch, and then click the
519
519
trash can icon to delete the branch.
520
520
521
521
#### Step 24:
522
-
The final step is to go to the Zenodo entry for the newly created release and put in the correct information. First go to [https://predictmd.net/zenodo](https://predictmd.net/zenodo), and then click on the yellow "Edit" button to edit the most recent release. Then, fill out the following fields with the specified values:
522
+
523
+
Tag the new release with [PredictMDRegistry](https://github.com/bcbi/PredictMDRegistry). Instructions are available here: [https://github.com/bcbi/PredictMDRegistry/blob/master/CONTRIBUTING.md](https://github.com/bcbi/PredictMDRegistry/blob/master/CONTRIBUTING.md)
524
+
525
+
#### Step 25:
526
+
The final step is to go to the Zenodo entry for the newly created release and put in the correct information. First go to [https://doi.org/10.5281/zenodo.1291209](https://doi.org/10.5281/zenodo.1291209), and then click on the yellow "Edit" button to edit the most recent release. Then, fill out the following fields with the specified values:
523
527
524
528
##### Upload type:
525
529
* Software
@@ -532,7 +536,7 @@ The final step is to go to the Zenodo entry for the newly created release and pu
532
536
| Name | Affiliation | ORCID |
533
537
| --- | -------- | ---- |
534
538
| Aluthge DP | Brown Center for Biomedical Informatics, Brown University | 0000-0002-9247-0530 |
535
-
| Sinha I | Brown Center for Biomedical Informatics, Brown University ||
539
+
| Sinha I | Brown Center for Biomedical Informatics, Brown University |0000-0001-7796-819X|
536
540
| Stey P | Brown Center for Biomedical Informatics, Brown University ||
537
541
| Restrepo MI | Brown Center for Biomedical Informatics, Brown University | 0000-0002-2708-8984 |
538
542
| Chen ES | Brown Center for Biomedical Informatics, Brown University | 0000-0002-6181-3369 |
0 commit comments