Add "Delete source branch when merge request is accepted" option in PRs for Gitlab/Gitlab selfhosted
We use Gitlab self-hosted and use the Pull Request feature.
The problem is, we need to select "Delete source branch when merge request is accepted." as a merge option.
Currently, we need to create a PR and always switch to GitLab for setting this setting
- Push feature branch to remote branch
- Drag & drop feature branch onto develop and select create pull-request
- Be able to set bit Delete source branch when the merge request is accepted.
Comments: 4
Oldest
•
Newest
•
Most likes
•
Fewest likes
-
13 Apr, '22
the alien MergedDear GitKraken overlords,
according to the gitlab API doc, it's possible to tell gitlab to add `reviewer(s)`, tell it to `squash` commits and `remove_source_branch`. these are options which are really handy and are constantly used in most MRs.
I know that it's possible to open the link after the MR is created and edit the MR and set these options, but the whole of gitkraken is to ease this work! :D
so, if the overlords agree, "as a user, I'd like Gitkraken to support" setting these values directly from Gitkraken when creating MRs.
PS: gitlab's doc about creating MR:
https://docs.gitlab.com/ee/api/merge_requests.html#create-mr
best regards, -
21 Jun, '24
Vicente Roche System"Add gitlab `reviewer`, `squash` and `remove_source_branch` values while creating merge requests" (suggested by <Hidden> on 2022-04-13), including upvotes (26) and comments (0), was merged into this suggestion.
-
06 Sep, '24
Luis Burbano MergedHi there,
The remote source branch is useless after request is accepted and merge into target branch completed. An optional checkbox to autoremove it would be very grateful. Exactly as the merge request works in GitLab server. Thanks
-
06 Sep, '24
Chris Bowie System"Add to the Pull Request option to "delete remote source branch when request is accepted"" (suggested by <Hidden> on 2024-09-06), including upvotes (1) and comments (0), was merged into this suggestion.
