Suggestion: Collections and commit check

[Thomas Linder Puls]

When I want to commit vault says if I need to merge changes. This is a nice feature, but I actually don't think it is enough in its present form.

The problem is that the changes that I really have to consider are not only the changes made to the files that I have also changed. If I work on a software project then I really need to merge all changes made to the project before I can commit my changes.

I.e. before I can commit my changes I will have to "get latest" of the complete project, and merge the file level changes.

Vault could make this more safe if I could mark a folder as containing a "project". Commiting anything inside such a "project" is only possible if: I have the latest files from this project and all chages are merged.

In principle it should also only be possible to commit all changed files from a "project" at once (these are the files that you have compiled together). I must however admit that I sometimes commit more selectively, because I belive that some files can be submitted without the rest.

Marking a folder as a project will in a way consider the whole folder as one "document".

[Guest]

I'd like to add my support to this feature.

The work you've done should really always be tested with the changes made by others before a check-in otherwise there's no guarantee that your changes will integrate. Left to the discipline of us developers to do a merge of the changes made by others with our outstanding before a check-in is just asking for trouble!

The idea here of Thomas to mark a folder as a project perhaps fits with the more general idea of associating a policy (one or more rules) with areas of the repository. This is something you can do with higher-end SCM tools.

Christian