This command represents a faster alternative to git add -i or git gui. It allows you to stage or unstage files from the index in an editor, just like when you perform an interactive rebase.
For example, let’s assume you have the following three modified files (git status --short):
M path/to/file1
M another/path/to/file2
M yet/another/path/to/file3After running git edit-index, an editor will show up with the above output. To stage (add) the first two files, simply change the text to
A path/to/file1
A another/path/to/file2
M yet/another/path/to/file3The supported statuses are M, A, D, and ?. They allow you to not only stage files but also unstage them, delete them, or revert changes done to them since the last commit.
See the project’s homepage for more information.
1 maintainer
Metadata
1 maintainer
Release files for git-edit-index 0.7
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-edit-index-0.7.tar.gz | 10.1 kB | Without provenance | Details for git-edit-index-0.7.tar.gz |
Release files / git-edit-index-0.7.tar.gz
| Download URL | git-edit-index-0.7.tar.gz |
|---|---|
| Size | 10.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
856acd9c716405d753da39f52892a12139c4c38c7030d40357863a3240920429
|
|
BLAKE2b-256 checksum How to use checksums |
5389cb7fc226e141058f9974560b5e26057acc46df3099b6a2b7687f0af5070d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.5
|
Security for git-edit-index 0.7
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
