Skip to content

feat: Add `mr_for` command for creating MR and branch for issues

John McAvoy requested to merge github/fork/j-mcavoy/trunk into trunk

Description MR's can be created using:

glab mr for <issue_num>

This creates a

Related Issue #114 (closed)

Motivation and Context

How Has This Been Tested?

I tested on a dummy GitLab project

Procedure:

$ glab issue create -t 'My New 123 Issue'

#5 My New 123 Issue (less than a minute ago)
https://gitlab.com/j-mcavoy/glab-test/-/issues/5

$ glab mr for 5
#21 Draft: My New 123 Issue (#5) (master) less than a minute ago
https://gitlab.com/j-mcavoy/glab-test/-/merge_requests/21

This command is self-contained, it does not modify other mr commands

Screenshots (if appropriate):

image

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Merge request reports