GitLab | Reduce generation of Merge Commits (#90)

Kinsey Moore (@opticron) gitlab at rtems.org
Fri Nov 15 19:06:06 UTC 2024



Kinsey Moore created an issue: https://gitlab.rtems.org/administration/gitlab/-/issues/90



This setting needs to get updated so that users can't push to their fork's default branch without unprotecting it: admin->settings->general->visibility and access controls->Default project creation protection

This should be set to "no one" so that it can only be updated from the UI with the "Update fork" button.

We also need to set the default merge method for new projects/forks to fast-forward instead of the current default of "merge commit". This is important because clicking "Update Fork" from a branch in your personal fork will use this method to perform the update. I suspect this is because it uses a merge request internally.

-- 
View it on GitLab: https://gitlab.rtems.org/administration/gitlab/-/issues/90
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20241115/5fab88c1/attachment.htm>


More information about the bugs mailing list