Hello rafals,
The "ccollab admin trigger create-review" trigger should be configured as a post-commit hook on your SVN server. Once this event happens, the hook will trigger the Collaborator command-line client that will interact with the SVN and Collaborator servers to check if a review was already created for the commit. If it was not created, the trigger will pull the needed information from the SVN side and will create a new review in Collaborator. This trigger is smart enough to compare the name of the commit author with the current Collaborator user base. If a match was found, the review will be created under the matched Collaborator account. To avoid storing the credentials of a real LDAP/AD user, you can create a service account in your AD and utilize this account for this hook configuration.
An example of the trigger content can be found at the bottom of this Help Article:
>>>
we can control the participants of the review (ie. like a per-user or per-source branch template? I imagine this could be done with some "custom scripting" but since it's probably a very popular request is there some built-in support or best practice?)
<<<
Collaborator has a built-in feature that allows adding participants by a subscription. Each Collaborator user can subscribe to a template, Collaborator user, or a specific file path. Collaborator will add this issue to a new review if the condition was matched:
