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.rst
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ Repo Maintainers
23
23
To create a new release for pypi and conda:
24
24
25
25
1. Clone this repository
26
-
2. Make sure all tests pass first by running `./setup.py test`
26
+
2. Make sure all tests pass first by running :code:`./setup.py test`
27
27
3. Use git or the GitHub interface to tag the repository with the next version. Precede the version number with a 'v'. Follow symantic versioning rules https://semver.org/:
28
28
29
29
Given a version number MAJOR.MINOR.PATCH, increment the:
@@ -35,8 +35,8 @@ To create a new release for pypi and conda:
35
35
PATCH version when you make backwards compatible bug fixes.
36
36
37
37
4. Create a release via the GitHub interface for the new tag.
38
-
5. Build the package by running `./setup.py build sdist`
39
-
6. Upload the new package to pypi by running `twine upload -u brinkmanlab dist/<file with latest version number>.tar.gz`
38
+
5. Build the package by running :code:`./setup.py build sdist`
39
+
6. Upload the new package to pypi by running :code:`twine upload -u brinkmanlab dist/<file with latest version number>.tar.gz`
40
40
41
41
Bioconda will detect the upload and automatically update its recipe. A Bioconda maintainer will manually approve the update.
0 commit comments