Should I put the output files in the source control?

I was asked to put every single file in my project under source control, including a database file (not a schema, a complete file).

This seems wrong to me, but I can’t explain it. Every resource I found about version control tells me not to put the generated output files in the version control system. And I understand that these are not "source" files.

However, the following considerations were presented to me:

  • Who needs this? We have a lot of bandwidth.
  • I do not mind resolving the conflict every time I get the latest version, this is just one click
  • This is much more convenient than thinking about good ignore files.
    • In addition, if I need to add an external DLL file to the bin folder now, I cannot forget to put it in the original control, since now the bin folder is not ignored.

A simple solution for the last marker point is to add the file to the library folder and link to it from the project.

Please explain if and why it is incorrect to put the generated output files in the source control.

+3
source share
3 answers

You did not explain what a "database file" is.

, , , , , . , "libraries", .

, , , , " " , .

, , , , , , , . 3 , 3 150 obj/bin.

+3

( ) "" VCS, :

  • , , - : , , , , .
  • , , ( ) TM)
  • ( ), ( - ...)

VCS, , Maven, .

+3

, , , DLL ? , , ?

: .

eveything, , - . , , , ?

, :

,

? , .exe .class( - ). , , , ? ? , , . Eclipse CVS .

The "No Ignore Files" rule is almost certainly absurd. Once you have freedom, there are some ignore files, why not just use them wisely to exclude the database? Who is uncomfortable? Only you, if anyone, and you are ready to do extra work.

+1
source

Source: https://habr.com/ru/post/1724910/


All Articles