I have a repository which contains Content & Source files. Developers should work only on source files. To save space, developers should not clone the content files (which are in GB) to their local repo. Source files are not present in the project as sub-modules rather they are in the same location where the contents are.
My approach is like this - I created a branch Source from Master and then deleted the content files from that branch. And I published the same branch for cloning to the developers.
As I am merging the changes from the Source branch back to Master, the content files are getting deleted in Master. How to restrict it? And if it is not possible then is there a way to achieve my requirement of having a separate branch / clone having only filtered files i.e. the source files in it?
The obvious answer is that you should have separate source and content repositories. Or just leave the content be.
You shouldn’t have removed the files from the Source
branch at all. If Source
and Master
are only branches in the same repository your developers will have the content anyway; there’s no harm in having it lying around.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With