From #3152637-37: Opt-in to the Drupal.org Issue Forks and Merge Requests beta:
that would be nice to have an option to generate the full git command with remote URL and proper remote name.
Fewer interactions with sidebar would be better for newcomers and will save few seconds in general.
Now I have to copy remote-name and remote URL separately (one interaction to expand the Clone block and 2 copy interaction).I also noticed that now a maintainer would work more with different remotes on the single project, so I propose adding a recommendation to rename "origin" remote name to "< project_name >" remote name. This will reduce possible unintended pushes to the wrong repo during the work on multiple projects.
Once a merge request is open, GitLab’s UI does have a button to show more instructions:
The “following these guidelines” link at the bottom goes to https://git.drupalcode.org/help/user/project/merge_requests/reviewing_an... (We of course can’t really customize the GitLab UI, these instructions will only change when the GitLab product makes changes.)
Remaining tasks
- Draft best practices at https://www.drupal.org/drupalorg/docs/gitlab-integration/issue-forks-mer...
- Decide which parts should be in the UI.
- Build them.
Comment | File | Size | Author |
---|
Comments
Comment #3
drummvoleger reported this at #3152637-37: Opt-in to the Drupal.org Issue Forks and Merge Requests beta
Comment #4
drummComment #5
drummWith this additional instruction, and everything else we’ve added, I think it is time to move issue forks into place next to files in the main content area. This is not styled yet, and I need a toggle to hide/show instructions. This should only be reviewed for content.
Comment #7
drummIssue forks are now in the main content area and have a “Show commands” toggle.