Submodules is the way to go, but really it's always a good idea to use tagged releases or commit id's for code from upstream as they might implement a breaking change at some point, taking Your project down with it.
this post was submitted on 19 Jul 2023
13 points (100.0% liked)
Git
2882 readers
2 users here now
Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
Resources
Rules
- Follow programming.dev rules
- Be excellent to each other, no hostility towards users for any reason
- No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.
Git Logo by Jason Long is licensed under the Creative Commons Attribution 3.0 Unported License.
founded 1 year ago
MODERATORS
It’s probably also good to link to a fork of the repo in question, in case the original disappears.
take a look at subtree, it incorporates the history of the upstream repository into your repository easily and if the upstream vanishes one day, you would still have a full repo history of upstream
Haven’t heard of, will check out! Thanks.
great, thanks a ton!
Couple of others have suggested to Submodules. git subtree is another alternative. Personally, I felt subtree much more easier to use.