7

I'm crying internally. The project(s) i work on have configuration files with dev and prod-info, the prod is just commented out. But thanks to reasons everyone has a different dev environment so there are many dev-config-blocks. I just use mine and carry on, BUT SOMEONE ALWAYS COMMITS THOSE FILES. I JUST THOUGHT OF IT NOW, BUT I'LL PUT THOSE FILES ON A BLACKLIST. FROM NOW ON YOU CAN ONLY COMMIT THESE FILES DURING A FULL MOON.

There's also this codebase to create licenses for our products. The license data fpr every customer is there, commented out. If you wanted to create another license, comment something and comment out another thing and you're good to go. THAT'S NOT WHAT VERSIONING IS FOR.

Comments
  • 3
    you know you can create a .gitignore file, right?

    Or you're not using git? Surely every modern versioning system has something.
  • 1
    @AndSoWeCode the files are needed for the program to run, we cannot gitignore them. I tried to --assume-unchanged, but eclipse doesnt respect that. Because of that some people commit the files instead of tediously searching for them and unchecking them before every commit
  • 2
    @YouAreAPIRate "the files are needed for the program to run, we cannot gitignore them." - therein lies the problem. Local stuff should be an optional override, and added to .gitignore.
  • 1
    You're right, we should've never added from the start. But the project was made with this flaw and we'll have to live with it.
    But you're always smarter afterwards
Add Comment