Procedures before checking in to source control?

Posted by Mongus Pong on Stack Overflow See other posts from Stack Overflow or by Mongus Pong
Published on 2010-01-13T14:56:12Z Indexed on 2010/04/02 4:13 UTC
Read the original article Hit count: 364

I am starting to get a reputation at work as the "guy who breaks the builds".

The problem is not that I am writing dodgy code, but when it comes to checking my fixes back into source control, it all goes wrong.

I am regularly doing stupid things like :

  • forgetting to add new files
  • accidentally checking in code for a half fixed bug along with another bug fix
  • forgetting to save the files in VS before checking them in

I need to develop some habits / tools to stop this.

What do you regularly do to ensure the code you check in is correct and is what needs to go in?

Edit

I forgot to mention that things can get pretty chaotic in this place. I quite often have two or three things that Im working on in the same code base at any one time. When I check in I will only really want to check in one of those things.

© Stack Overflow or respective owner

Related posts about version-control

Related posts about best-practices