toreautomation.blogg.se - Smartgit force to mine merge

#SMARTGIT FORCE TO MINE MERGE UPDATE#

If more than 1 role is selected display N roles.If a single role is displayed, display the role.Clicking outside the dropdown should close it.If No one is selected, clicking should not remove selection.Selecting No one should remove other role selections.

Clicking an already selected option should unselect it.

#SMARTGIT FORCE TO MINE MERGE UPDATE#

Selecting an option should mark the option as selected and update input field.Dropdown should allow the user to search users.Dropdown should allow the user to select one or more users.Dropdown should allow the user to select one or more groups.Dropdown should allow the user to select one or more roles (or No one).Clicking the field should open a dropdown selection.Add field Allowed to force push to the list of protected branches.Add field Allowed to force push to the Protect a branch form.Step 2, once roles/groups/users have been defined as allowed to push, "allow force push" option shows next to each item on the listĪdd a new setting on protected branches called 'Allowed to Force Push' which would enable maintaners/owners to define which user/groups have this elevated privilege.Step 1, define which roles/groups/users are allowed to push.`force push` option is only available for items which already are allowed to push. Important note regarding Protected branches API: When protecting a branch via API and setting the unprotect_access_level to admin (60), only admins should be able to change the new Allow force push setting (like all other branch protection settings).Īllow project maintainers and owners to define which users/groups are allowed to force push to a protected branch. Proposed tooltip text: Allows force push for users with push access. ProposalĪdd a new Allow force push toggle on the protected branches section, which will enable force push for any roles/groups/users defined in the Allow to push section. We should provide a more convenient way to allow force pushes for specific users/groups on protected branches.

More use cases on the #use cases section.

Prevent force push for most branches except those matching a pattern, ie wip-*.

POC projects where an owner would want to always be able to force push to master.

Production incidents that require pushing an immediate fix, bypassing previously configured rules.

Finally, users migrating from competing services who made use of this feature have a break in their workflow. Currently, maintainers can remove branch protections to allow temporary force push, however, all settings for the previously protected branch in question are lost. While preventing force push is generally best practice, there are certain exceptions that currently cannot be configured.