"Require Check In comments" not enforced for new f

[jmetcalfe]

Server/Client version 3.1.6

We have the "Require Check In comments" selected for one of our repositories. When we check in new files into the repository, the comments field is there, but SGV is not forcing any comment to be made.

Is this supposed to work this way? Is there a work around for forcing comments to be entered when checking in new files?

Thanks!
Josh

[Perry]

I'm working with 3.1.6 client and server, and I have to put in comments when I add a file -- otherwise I get the "Check In comments are required for this Repository" (sic) error.

[jmetcalfe]

Perry,

There must be some difference between our settings then.

What is your setting under Tools > Options > Concurrent Development Style for the option "Auto-commit after each operation" ?

We have been using SGV with this option selected. This gives us a one step add and commit vs. the two step 1) add, 2) commit if you leave the box unchecked.

In either case, in my testing the "add" step never enforces a comment even though it is required for this repository.

If I choose the later option of separate add/commit steps, the commit step does enforce the comment.

Since we have multiple repositories, I've also test making comments required for all repositories. This test also did not cause SGV to enforce comments upon adding a new file.


Anyone else have any other ideas?

[lbauer]

Josh, you're right, when files are added with auto-commit on, there is no opportunity to force a checkin comment.

I'll log this as a bug to be addressed in a later release.

[ant]

Hi,

is there any way to force "Auto-commit" to off for all users of a repository. Default behavior appears to be "Auto-commit" is on. This results in related changes (such as added files and file check-ins) not being grouped in a changeset. Advice appreciated.

Regards

Ant

[quote="jmetcalfe"]Perry,

There must be some difference between our settings then.

What is your setting under Tools > Options > Concurrent Development Style for the option "Auto-commit after each operation" ?

We have been using SGV with this option selected. This gives us a one step add and commit vs. the two step 1) add, 2) commit if you leave the box unchecked.

In either case, in my testing the "add" step never enforces a comment even though it is required for this repository.

If I choose the later option of separate add/commit steps, the commit step does enforce the comment.

Since we have multiple repositories, I've also test making comments required for all repositories. This test also did not cause SGV to enforce comments upon adding a new file.


Anyone else have any other ideas?[/quote]

[lbauer]

There isn't a way to enforce checkout, or item comments.

Regarding setting auto-commit for everyone -- this is a user specific configuration. We do have a feature request for the ability for the Admin to set and enforce client options.


You can add comments during an add, but adding comments is not enforced. I'll add a feature request for this functionality.