Overview
This tool is meant to search many different repositories, looking for information contained inside of git databases.
Git is great at storing files and revisions, however there are many ways to lose track of changes made over time. It is not a simple task to search for data inside of git. Many folks have created shell scripts and one-line command line tools to search out changes that were lost or simply need to be found. These are all great, but they tend to be purpose built, and not usable by others.
This project attemts to consolidate several techniques for seeking out changes in one or more repositories at the same time.
Details
This tool will search the current repo, or many repos, for text in files, commit messages, authors or commit messages. The tool uses a standard python conditional to qualify the search using these variables:
message - full contents of message converted to lower case author - author converted to lower case email - author's email address converted to lower case files - list of files in the commit
Usage
Example of search in current directroy gitgrind -f "('myname' in author or 'myname' in email) and 'mydir/myfile.cpp' in files"
This will find any commits (dangling, in stash, or normal commits) and show the commit information
Metadata
Release files for gitgrind 0.2.0
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 |
|---|---|---|---|---|
| gitgrind-0.2.0.tar.gz | 7.3 kB | Without provenance | Details for gitgrind-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gitgrind-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for gitgrind-0.2.0-py3-none-any.whl |
Total release size: 15.8 kB
Release files / gitgrind-0.2.0.tar.gz
| Download URL | gitgrind-0.2.0.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c2c157a98f4f4237a188b0ba2a58a25267d6fd925584f5d64aa1daa9dac10c15
|
|
BLAKE2b-256 checksum How to use checksums |
4ac1e54b5e0b6a618cd1c3bfa0d2db5a190ff17040cd0ade422006c4cbcae082
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / gitgrind-0.2.0-py3-none-any.whl
| Download URL | gitgrind-0.2.0-py3-none-any.whl |
|---|---|
| Size | 8.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8fe8eab6cf696ddaf0a24c817f74cb4726d25d4bf34c123321da989d398ca549
|
|
BLAKE2b-256 checksum How to use checksums |
231ab8419afa7ab3668b3f8e19f03b22236f1dc61d2db8bd8521c18ce14eba10
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for gitgrind 0.2.0
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.