{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 forever°为你锁心 的问题《How to lock SVN trunk except for merges from branc》','https://www.manongdao.com/q-1243591.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I'd like to prevent developers working directly on the trunk.
I'm aiming to enforce all developers off the trunk and to work on there own branches until CI tests are cleared. They then have to merge from the trunk to their branch (to pick up latest changes), run and pass tests before they merge back to the trunk.
Is there any rules for this style of SVN usage?
Restrict their access to
/trunkwith SVN permissions. Allow them to read, but dis-allow to write. Assign one "architect" role who can write to/trunk. Developers will have to report to the architect when a branch is ready, the architect will pass tests manually, and then will merge into/trunk.