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: README.md
+2-51Lines changed: 2 additions & 51 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,8 @@ probably the skills to scratch that itch of mine: implement `git` in a way that
17
17
If you like the idea and want to learn more, please head over to [gitoxide](https://github.com/Byron/gitoxide), an
18
18
implementation of 'git' in [Rust](https://www.rust-lang.org).
19
19
20
+
*(Please note that `gitoxide` is not currently available for use in Python, and that Rust is required)*
21
+
20
22
## GitPython
21
23
22
24
GitPython is a python library used to interact with git repositories, high-level like git-porcelain,
@@ -220,57 +222,6 @@ Please have a look at the [contributions file][contributing].
220
222
6. Run `make release`.
221
223
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.
222
224
223
-
### How to verify a release (DEPRECATED)
224
-
225
-
Note that what follows is deprecated and future releases won't be signed anymore.
226
-
More details about how it came to that can be found [in this issue](https://github.com/gitpython-developers/gitdb/issues/77).
227
-
228
-
----
229
-
230
-
Please only use releases from `pypi` as you can verify the respective source
231
-
tarballs.
232
-
233
-
This script shows how to verify the tarball was indeed created by the authors of
0 commit comments