Is your feature request related to a problem? Please describe.
I would prefer that the backported MR's branch be deleted automatically. This is possible via GitLab's "Delete source branch when merge request accepted" settings. This is exposed in the API as remove_source_branch.
Describe the solution you'd like
When configured as so, set attribute remove_source_branch as part of a request to POST /projects/:id/merge_requests. However, I'm not sure if there's the equivalent thing in GitHub, and as such I'm not sure how to model config. Maybe just documentation (that a config is GitLab only) is enough?
Describe alternatives you've considered
- We can manually select "Delete source branch" just before pressing "Merge". However this is prone to forgetting.
- We can parse the program's output to fish out the MR address from the log and then manually send
PUT /projects/:id/merge_requests/:merge_request_iid. However, this can be prone to breakage.
Is your feature request related to a problem? Please describe.
I would prefer that the backported MR's branch be deleted automatically. This is possible via GitLab's "Delete source branch when merge request accepted" settings. This is exposed in the API as
remove_source_branch.Describe the solution you'd like
When configured as so, set attribute
remove_source_branchas part of a request toPOST /projects/:id/merge_requests. However, I'm not sure if there's the equivalent thing in GitHub, and as such I'm not sure how to model config. Maybe just documentation (that a config is GitLab only) is enough?Describe alternatives you've considered
PUT /projects/:id/merge_requests/:merge_request_iid. However, this can be prone to breakage.