Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.

First time visiting? Here are some places to start:
  1. Looking for a certain topic? Check out the categories filter or use Search (upper right).
  2. Need support? Ask a question to our Community Support category.
  3. Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
  4. Be respectful, on topic and if you see a problem, Flag it.

If you would like to contact our Community Manager personally, feel free to send a private message or an email.

Preventing merges unless they are from a release.

I am trying to adjust the permissions within my team's enterprise and I am trying to set up workspace protection and release management in a way that prevents members from merging branches into a protected workspace if they are not merging from an approved release.

Currently, it is technically possible for someone to make changes on a branch, and then merge it into a protected branch without it being approved, but I cant seem to find much in terms of settings for how workspace protection works, I can only really turn it on or off.

Is this something I can make a custom workflow in order to do?


Also, I noticed that in order to merge into a protected branch, the source of the merge must have all of the changes that the protected branch has, and I was wondering if there is a way to adjust how this works. It would be nice to be able to merge two separate branches both into a protected branch sequentially, but currently I would have to merge the first branch into the protected branch, then merge the protected branch into the second branch, then merge the second branch back into the protected branch, which just seems a bit clunky to me.

Sign In or Register to comment.