Copy link to clipboard
Copied
I've seen posts with tidbits of what should not go into source control, but I haven't seen a comprehensive list of what should and should not go into source control. Does anyone know? Here's what I know so far - do not put the following files in source control: .pss, .cpd, .ldb and .hhp.
Right now I'm wondering about the XPJ file. If two or more people are working on a project, should this file be source controlled?
Is there a specific list of files that DO need to be in source control in order to maintain the project's integrity?
The simple answer here is that machine specific files do not need to be checked in. This includes .PSS and .CPD files. The .HHP and .XPJ files are not machine specific, they are project specific and therefore must be checked in. The confusion over the HHP file may come down to whether CHM output is being produced. If you are not, you could safely say that this file need not be source controlled. However it doesn't cost anything to include it under source control so why make life more difficult b
...Copy link to clipboard
Copied
The simple answer here is that machine specific files do not need to be checked in. This includes .PSS and .CPD files. The .HHP and .XPJ files are not machine specific, they are project specific and therefore must be checked in. The confusion over the HHP file may come down to whether CHM output is being produced. If you are not, you could safely say that this file need not be source controlled. However it doesn't cost anything to include it under source control so why make life more difficult by excluding it.
The RoboColum(n) | @robocolumn | Colum McAndrew |
Copy link to clipboard
Copied
Thanks Colum! I do not know how to determine which files are machine specific, and which are project specific, but according to your answer, it seems like what we've been doing so far is correct.