Git Diff Tool
Welcome to Git Diff Tool! A simple yet powerful command-line utility designed to compare two branches of a Git repository and save their differences into a file. Whether you're working on a feature branch or resolving conflicts, this tool makes it easy to spot changes between branches.
Features
- Compare two branches of a Git repository (e.g.,
mainanddev). - Output the differences between the branches into a specified directory.
- Easy to use and flexible for any Git project.
How to Use
1. Running the Diff Tool
Use the following command to compare two branches of your Git repository:
python3 diff_tool.py \
--repository="https://github.com/<username>/<repository>" \
--main-branch="main" \
--local-branch="dev" \
--save-dir="/path/to/save/diff" \
--target-folder="."
Parameters
- repository: The URL of your Git repository. Example: https://github.com/username/repository
- main-branch: The branch you want to compare from (e.g., main).
- local-branch: The branch you want to compare to (e.g., dev).
- save-dir: The directory where you want to save the diff output file.
- target-folder: The target folder where the diff operation will be performed.
2. Example Usage
Here's an example that compares the dev branch with a feature-branch and saves the output to the /home/user/documents directory:
python3 diff_tool.py --repository="https://github.com/username/sample_project" \
--main-branch="dev" \
--local-branch="feature-branch" \
--save-dir="/home/user/documents" \
--target-folder="."
3. Interactive Mode
If you don't provide some of the parameters, the tool will prompt you to input them interactively. Simply run the command without arguments and the tool will guide you through the necessary steps.
python3 diff_tool.py
You will then be asked to enter details like the repository URL, branch names, save directory, and target folder. This command compares the dev branch with the feature-branch and saves the differences in the specified directory.
License
This project is licensed under the MIT License.
Metadata
Release files for git-diff-tool 1.0.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 |
|---|---|---|---|---|
| git_diff_tool-1.0.0.tar.gz | 3.7 kB | Without provenance | Details for git_diff_tool-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| git_diff_tool-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for git_diff_tool-1.0.0-py3-none-any.whl |
Total release size: 7.9 kB
Release files / git_diff_tool-1.0.0.tar.gz
| Download URL | git_diff_tool-1.0.0.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
df6bb48d8b0bf3eaccf2c35f23f4f7e9f1a5166d9032bcab3f623989b664f0d9
|
|
BLAKE2b-256 checksum How to use checksums |
dfc47492db510558504246fa5614e0c002035304cf953e4fd722a302fa7d8597
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Release files / git_diff_tool-1.0.0-py3-none-any.whl
| Download URL | git_diff_tool-1.0.0-py3-none-any.whl |
|---|---|
| Size | 4.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cf3e5878b3517994face13dc78e241f5d192bbc8bdb54154e977c1c5ea2563c2
|
|
BLAKE2b-256 checksum How to use checksums |
435d2f8fb2ebb376e21b493370ca948f761f6690dd69a0a46de2b8b1c3894b9c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Security for git-diff-tool 1.0.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.