mirror of
https://github.com/kp2pml30/git-third-party.git
synced 2026-02-16 23:54:41 +04:00
Tool for patching third-party dependencies without need to fork them
| .editorconfig | ||
| .gitignore | ||
| .pre-commit-config.yaml | ||
| git-third-party | ||
| LICENSE | ||
| README.md | ||
| ruff.toml | ||
Git third party
Tool for patching third-party libraries without need to fork them
This is a small zero-dependency utility that is an alternative to git-submodules and git-subtree. It stores only delta (changes) inside your tree
This tool is not oriented for highly concurrent modification of third-party tools by multiple users
Usage
# adding third-party repository
git-third-party add third-party/RustPython https://github.com/RustPython/RustPython.git a13b99642b0bc13ca89d01768a7ddbec18fe8219
# ^ git-third-party add <relative path> <repository url> <commit hash>
# now you can modify it as a regular repository, commit your changes
# save patches to push to your origin
git-third-party save third-party/RustPython
# ^ git-third-party save <relative path>
# update
git-third-party update third-party/RustPython
# ^ git-third-party update <relative path>
How it works?
It stores (at /.git-third-party/) a configuration that describes all third party repositories and patches. save command updates the patches, update command reapplies them
Directory .git-third-party must be controlled by git, while third-party repos should not
Best effort is done to keep patches deterministic and strip all metadata from them, which includes:
- git version
- commit hash (which depends on committer)
- ...