What Part of Your Project Should be in Source Code Control?

Posted by muffinista on Programmers See other posts from Programmers or by muffinista
Published on 2011-11-18T15:51:34Z Indexed on 2011/11/18 18:02 UTC
Read the original article Hit count: 203

A fellow developer has started work on a new Drupal project, and the sysadmin has suggested that they should only put the sites/default subdirectory in source control, because it "will make updates easily scriptable." Setting aside that somewhat dubious claim, it raises another question -- what files should be under source control? And is there a situation where some large chunk of files should be excluded?

My opinion is that the entire tree for the project should be under control, and this would be true for a Drupal project, rails, or anything else. This seems like a no-brainer -- you clearly need versioning for your framework as much as you do for any custom code you write.

That said, I would love to get other opinions on this. Are there any arguments for not having everything under control? Is this sysadmin a BOFH?

© Programmers or respective owner

Related posts about best-practices

Related posts about version-control