File tree Expand file tree Collapse file tree 1 file changed +0
-20
lines changed Expand file tree Collapse file tree 1 file changed +0
-20
lines changed Original file line number Diff line number Diff line change @@ -113,27 +113,7 @@ But there is another way. Instead of providing the changelog, the ``CHANGELOG.rs
113
113
file can hold a *link * to the changelog. This makes things much easier.
114
114
``sphinx-github-changelog `` encourages you to do that.
115
115
116
- A complete toolbelt
117
- -------------------
118
-
119
- Alongside ``sphinx-github-changelog ``, we suggest a few tools that play nice together:
120
-
121
- - `setuptools-scm `_ will compute your version in ``setup.py `` based on git tags.
122
- - `release-drafter `_ will keep a "Draft release" updated as you merge Pull Requests to
123
- your repository, so you just have to slightly adjust the release body, and create a
124
- tag.
125
- - Any Continuous Integration solution should be able to listen to new tags, and build
126
- and upload distributions to PyPI. Don't forget to use `PyPI API tokens `_!
127
- - And ReadTheDocs _ to host your built documentation, of course.
128
-
129
- .. _`setuptools-scm` : https://pypi.org/project/setuptools-scm/
130
- .. _`release-drafter` : https://help.github.com/en/github/administering-a-repository/about-releases
131
116
.. _towncrier : https://pypi.org/project/towncrier/
132
- .. _`PyPI API tokens` : https://pypi.org/help/#token
133
- .. _ReadTheDocs : https://readthedocs.org/
134
-
135
- If you're using all the tools above, then releasing is simple as proof-reading the
136
- draft GitHub Release and press "Publish Release". That's it.
137
117
138
118
Reference documentation
139
119
=======================
You can’t perform that action at this time.
0 commit comments