top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Do I have to download all files or selectively to work on GIT

0 votes

If I create a git repo for multiple projects, for example ALL projects that my team works on, when they clone and pull, do they have to download all the files? Can they sort of selectively download the files they may want to read or work on?
The idea is I want to track a bunch of projects for my team ... so i was thinking to make a repo that contains something like this:


Then the entire team can contribute to any of the projects they may be working on, but they should not have to download every single file when they clone .. is that possible?
Basically I do not want to have to create a repo for every single project .. is that what people normally do?

posted Jul 1, 2013 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote
Best answer

I believe that one could create a repo with one branch for each project -- that is, the branches would be *completely different* from each other. Since you can pull single branches from a master repository, you should be able to create a dependent repository that contains only the history of the one project.

OTOH, Git isn't designed to be used this way, so there are probably a whole bunch of operational problems in implementing this idea.

answer Jul 2, 2013 by anonymous
Similar Questions
0 votes

I work on some files and push/merge them to the remote server. Sometimes I get merge conflicts on those files and have to fix them. That's completely fine. I get that.

What I don't understand is that sometimes during this process I will get merge conflicts in files _I have never touched_. In fact they are in a completely different series of directories to the one I am working on and someone else project entirely. How am I meant to know how to fix these? I dont know what the other developer wanted to do and if they have done it right.

I thought git only merged/pushed the files you have changed? If someone else has changed Group A files on the remote repo, why must I change my local Group A files when I am _pushing _completely different set of Group B files?

Sure, Id understand if I were pulling files down to my local and had to resolve merge conflicts then, but this isn't happening when I push the files up.

Any help or advice is much appreciated. Sorry if I sound frustrated - I am really trying hard to get my head round this whole git thing but its just so weird.

+1 vote

At some point I added a large file into a git repository. It now exists on multiple branches, possibly with some changes to it. I'd like to remove it from git, but leave its current form (say the one on the master branch) on the file system.

I tried (on a dummy git archive)

git filter-branch --index-filter 'git rm --cached --ignore-unmatch bigfile' master branch1 branch2

That, however, does not leave a copy of bigfile on the file system.It isn't clear to me why not, though the description of the --tree-filteroption to filter-branch (I'm using the --index-filter option, but is is "similar") states:" (new files are auto-added, disappeared files are auto-removed ... )".
Is there a direct way to do what I want, with git? I've found similar requests;none of the responses point out that the above command actually deletes the file from the file system.

+1 vote

All the git repositories are on one git server in specific directory.
I would like to know what I need to backup in order to be able to make a success restore, in case my disk on the git server will crushed.

I would like to understand, after the user run on his local workstation 'git init / add / commit / push' all the information was copied to the git server and the local directory in the local workstation can be removed?

I can see somehow the name of the files and their content in the git repository that saved on the git server?

+2 votes

I have Multiple SKU of my application (eg Standard, Enterprise, Corporate), what is best or suggested git workflow for it? or I should manage it in separate folders as separate project with individual git standard flow ?