No changes selected as default
Provide option to select all or no changes as default in the Commit Changes and Get Latest tab
Closing as request is 6 years old. There is a checkbox in the column header that will quickly allow you to select/unselect all.
-
Dan Algarin commented
We have already implemented a "policy" that developers uncheck everything to begin with and then select ONLY the items that are ready to be committed. Unfortunately, we still have numerous occurrences where the developer fails to do this and commits unfinished code/schema changes. Since Commit and Get Latest are core functionality for SQL Source Control, it would seem critical to provide options for the default behaviors. Note: We also use dedicated databases, so the feature mentioned above does not help us.
-
Jason Felton commented
We have a Dedicated database development setup. We reuse the same local database for different branches due to limitations of our code base. (Don't ask :-) ) When we switch a single database's branch to a new branch created from trunk there are changes from other branches that have not yet made it into trunk. Instead of reverting those changes, I choose to have a growing list of changes in my commit changes tab. I almost checked the entire lot into SVN this morning because everything was selected by default.
Having a settings option to set the default behavior of 'Select All by default' or 'Select None by default' would be great!
-
For now, there is a checkbox in the column header that will quickly allow you to select/unselect all.
Also, if you right click on the specific object that you want to commit and select Commit changes, then only this object will be selected on the "Commit Changes" tab.
Similarly, if you right click on a "directory" (e.g., stored prodedures) and select Commit changes, then only the objects in the "directory" will be selected on the "Commit Changes" tab.