Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitfeb4414

Browse files
committed
Shorten another step
1 parenta151ea0 commitfeb4414

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

‎README.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -202,8 +202,7 @@ Please have a look at the [contributions file][contributing].
202202
2. Update/verify that the`doc/source/changes.rst` changelog file was updated. It should include a link to the forthcoming release page:`https://github.com/gitpython-developers/GitPython/releases/tag/<version>`
203203
3. Commit everything.
204204
4. Run`git tag -s <version>` to tag the version in Git.
205-
5._Optionally_ create and activate a[virtual environment](https://packaging.python.org/en/latest/guides/installing-using-pip-and-virtual-environments/#creating-a-virtual-environment) using`venv` or`virtualenv`.\
206-
(When run in a virtual environment, the next step will automatically take care of installing`build` and`twine` in it.)
205+
5._Optionally_ create and activate a[virtual environment](https://packaging.python.org/en/latest/guides/installing-using-pip-and-virtual-environments/#creating-a-virtual-environment). (Then the next step can install`build` and`twine`.)
207206
6. Run`make release`.
208207
7. Go to[GitHub Releases](https://github.com/gitpython-developers/GitPython/releases) and publish a new one with the recently pushed tag. Generate the changelog.
209208

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp