Currently developing futuristic smart-device, IoT connected, highway construction site safety system in EU.
Used to work on infrastructure, application architecture and cloud engineering.
Hi, thank you! At the moment I don't know any use cases, I have heard some examples of putting code in one branch and CI deployment code in an orphan branch, but that is as far as my knowledge goes for now. For this example I just have done a test myself to experiment and see how to build them and what they look like
Currently developing futuristic smart-device, IoT connected, highway construction site safety system in EU.
Used to work on infrastructure, application architecture and cloud engineering.
Hi, I actually found one example directly in the git man page for git-checkout:
This can be useful when you want to publish the tree from a commit without exposing its full history. You might want to do this to publish an open source branch of a project whose current tree is "clean", but whose full history contains proprietary or otherwise encumbered bits of code.
Cool, that's a great spotting! I didn't read the full piece of the git man page for the --orphan flag and now I have learned something new on top of what I wrote. Thanks for your comments!
Where I have been able to utilize this is in a course I'm taking. I want all the parts of the course to be done in a single repo so I'm making each part an orphan branch.
P.S. some parts are not all related.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hello, nice article. Could you please elaborate on what are the use cases to use orphan branches? Thanks.
Hi, thank you! At the moment I don't know any use cases, I have heard some examples of putting code in one branch and CI deployment code in an orphan branch, but that is as far as my knowledge goes for now. For this example I just have done a test myself to experiment and see how to build them and what they look like
Hi, I actually found one example directly in the git man page for git-checkout:
This can be useful when you want to publish the tree from a commit without exposing its full history. You might want to do this to publish an open source branch of a project whose current tree is "clean", but whose full history contains proprietary or otherwise encumbered bits of code.Cool, that's a great spotting! I didn't read the full piece of the git man page for the
--orphanflag and now I have learned something new on top of what I wrote. Thanks for your comments!Where I have been able to utilize this is in a course I'm taking. I want all the parts of the course to be done in a single repo so I'm making each part an orphan branch.
P.S. some parts are not all related.