f1wade Posted December 22, 2014 Report Share Posted December 22, 2014 how do i restrict check ins to merges only? Link to comment Share on other sites More sharing options...
manu Posted December 22, 2014 Report Share Posted December 22, 2014 You will need to create a before-clientcheckin trigger to check if the checkin is involving a merge operation or not. To check if you are committing you'll need to check the "$wkpath\.plastic\plastic.mergechanged" file. It contains something like: Merge from 436 (mount:56e62dd7-241f-41e9-8c6b-dd4ca4513e62#/#default@localhost:8084): C:145:120 When you are checking-in a merge. Means that you are mergin from the changeset #436 of the default repository. If you are not committing a merge you can make the trigger fail. Link to comment Share on other sites More sharing options...
nadavroz Posted January 30, 2015 Report Share Posted January 30, 2015 Hi, I have the same problem. I would like to enforce developers to create branches and not working directly on the main branch. I have a problem with client triggers since each dev use different paths, different OS ... Is there a way to enforce that on the server side without client trigger?? Or is there a way to set the clientbefore-checkin trigger path to the local workspace path (each dev have his workspace in different path, but if there is a way to use variable like $WKSP_PATH that point to each dev local path?? ) Thanks! Nadav. Link to comment Share on other sites More sharing options...
calbzam Posted February 4, 2015 Report Share Posted February 4, 2015 Hi, If you want to avoid developers to commit in the main branch, why don´t you configure the branch permissions based on your needs? We could use a trigger approach, but I think that configuring the permissions makes more sense. Regards, Carlos. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.