Git rb
git-rb is a simple command-line tool to simplify interactive rebase workflow
in Git, often I'd find my self copying hashes from git log output in order to
paste into git rebase -i. This tools only purpose is to simplify that.
Code is self contained within main.py, so you could just copy the whole script.
Note: I had this a form of this script kicking around for a while and figured I'd try using Gemini CLI to do the rest. Results were mixed, I wasn't able to 'set and forget', but it was still useful.
Usage
.gitconfig
Typically I'll have the following in .gitconfig:
[alias]
rb = !uvx git-rb
To provide alias git rb.
Example
Running this from sklearn gives:
Entering '6' in the prompt just runs git rebase -i <hash on line 6>, nothing fancy!
Simple
A simpler approach would be to just use:
git rebase -i HEAD~{{ N }}
That would mean no messing about with rich though.
Metadata
Release files for git-rb 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| git_rb-0.1.3.tar.gz | 465.1 kB | With provenance | Details for git_rb-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| git_rb-0.1.3-py3-none-any.whl | Python 3 | none | any | Details for git_rb-0.1.3-py3-none-any.whl |
Total release size: 469.7 kB
Release files / git_rb-0.1.3.tar.gz
| Download URL | git_rb-0.1.3.tar.gz |
|---|---|
| Size | 465.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5c60266deaca0e7b7ce0ea9aad4cbc98a50a5b90c8bc9da1e9c29e342a92f3aa
|
|
BLAKE2b-256 checksum How to use checksums |
418877aa3c68b6cce631480dd86629cc7cc96bab7dc63f1f0b2f48b769bd5cef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 7, 2025.
Transparency logRelease files / git_rb-0.1.3-py3-none-any.whl
| Download URL | git_rb-0.1.3-py3-none-any.whl |
|---|---|
| Size | 4.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
db40b244e369a1936b4c413e079561a64229329d2ac370f77de309fb38c30c02
|
|
BLAKE2b-256 checksum How to use checksums |
7a5c3079531c3c3821997da126bdfe79fd1954ed4057f99b0fa66c84829abf69
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 7, 2025.
Transparency logSecurity for git-rb 0.1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for git_rb-0.1.3.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 7, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.