1

I have a Symfony project, which was always held in an svn project. Now I am trying to make the move to git (on github).

The problem is that

git status

always tells me that there are modified and new files/folders, which I cannot seem to commit...

When I

git add

these files/folders, then commit will just tell me I have nothing to commit, and that the files/folders are still untracked?

All the other stuff in my Symfony project is committed and pushed file, its just certain stuff in the vendors folder which I can't seem to get going.

How can I fix this?

ps: I am also having trouble getting composer to update my vendors.

Jason Aller
  • 3,541
  • 28
  • 38
  • 38
Sam Janssens
  • 1,491
  • 1
  • 12
  • 30
  • Did you tried '`git add .`' instead of just '`git add`'? – VonC Dec 11 '12 at 08:45
  • i have tried 'git add .' 'git add ./' 'git add [fileOrFolderInQuestion]', nothing, i guess it has to do with the fact that the vendors also have .git folders inside of them .. – Sam Janssens Dec 11 '12 at 11:11

2 Answers2

1

i guess it has to do with the fact that the vendors also have .git folders inside of them

I confirm a nested git repo won't respond well to git command, if that nested repo already consider said files committed.
Or, at the very least, you should add those files while being within that nested repo (not from a parent directory).

However, a git status done in a parent directory should ignore the content of that nested repo. See How to make top-level git to track all the files under another sub-directory git .

Community
  • 1
  • 1
VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
1

My best practice is to completely ignore the vendors directory, and install all the vendors bundle with composer on every development machine using composer.json and composer.lock (thus, you will need to add these files to your repo!)

GergelyPolonkai
  • 6,230
  • 6
  • 35
  • 69
  • this is the approach we eventually took, i just couldnt at first because the composer was throwing errors, its fixed now and we are running composer manually on each machine . – Sam Janssens Jan 14 '13 at 11:02