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
Next, install the development dependencies. We recommend using a virtual environment,
20
19
such as `virtualenv <https://virtualenv.pypa.io/en/stable/>`_.
21
20
@@ -38,7 +37,6 @@ We can run all tests with:
38
37
39
38
pytest tests
40
39
41
-
42
40
Code Style
43
41
~~~~~~~~~~
44
42
@@ -50,7 +48,6 @@ manually with:
50
48
51
49
make lint
52
50
53
-
54
51
If you need to make a commit that skips the ``pre-commit`` checks, you can do so with
55
52
``git commit --no-verify``.
56
53
@@ -74,7 +71,7 @@ a discussion, and doesn't necessarily need to be the final, finished submission.
74
71
GitHub's documentation for working on pull requests is
75
72
`available here <https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests>`_.
76
73
77
-
Once you've made a pull request take a look at the Circle CI build status in the
74
+
Once you've made a pull request, take a look at the Circle CI build status in the
78
75
GitHub interface and make sure all tests are passing. In general pull requests that
79
76
do not pass the CI build yet won't get reviewed unless explicitly requested.
80
77
@@ -100,10 +97,8 @@ Before releasing a new version, build and test the package that will be released
100
97
.. code:: sh
101
98
102
99
git checkout main && git pull
103
-
104
100
make package-test
105
101
106
-
107
102
This will build the package and install it in a temporary virtual environment. Follow
108
103
the instructions to activate the venv and test whatever you think is important.
109
104
@@ -113,7 +108,6 @@ You can also preview the release notes:
113
108
114
109
towncrier --draft
115
110
116
-
117
111
Build the release notes
118
112
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
119
113
@@ -136,7 +130,6 @@ After confirming that the release package looks okay, release a new version:
136
130
137
131
make release bump=$$VERSION_PART_TO_BUMP$$
138
132
139
-
140
133
This command will:
141
134
142
135
- Bump the version number as specified in ``.pyproject.toml`` and ``setup.py``.
0 commit comments