Auto Commit in a Shared Development Model

• 
  This isn't currently possible - the commits only happen when you visit the commit tab and choose to actually execute the process.
  
  I'd imagine it could potentially be a dangerous operation; if a developer is working on something that involves changes to several objects then each one being committed automatically at various intervals could lead to strange behaviour or conflict with work other developers are doing?

  James B April 01, 2011 07:43

  - 0 +
• 
  Is it possible in future version as an option or setting that allows auto-commit. This will be very useful for small developer team (2 to 5 people). The developer often forgets to commit the changes to the source control.
  I do not want auto commit on the other way (from source control to database) as it would be not good option.

  shivanandk April 01, 2011 07:49

  - 0 +
• 
  I don't think it's currently planned as a feature, however could I ask you to check and post it on our Uservoice - see here
  
  Then other users who want this option can vote it up, increasing the chances we'll implement it!

  James B April 01, 2011 07:51

  - 0 +
• 
  One problem with this feature is that it would make it easy for breaking changes to be committed.
  
  There are other undesired changes that could happen. For example, if a developer accidentally commits a change that deletes data, and another developer assumes the change is good and gets it, this would have very undesirable consequences.
  
  What are your thoughts on these side effects?
  
  David Atkinson
  Product Manager
  Red Gate Software

  David Atkinson April 01, 2011 08:13

  - 0 +

Add comment

Please sign in to leave a comment.