Set default branch to 2.0.x

Created on 26 April 2023, about 1 year ago
Updated 31 May 2024, 25 days ago

Problem/Motivation

The default branch for this module is still 8.x-1.x.
When creating a merge request or cloning the module repository, the old branch is set.
See the image bellow:

Proposed resolution

Edit the default branch on: https://www.drupal.org/node/246513/edit/default-branch β†’

πŸ“Œ Task
Status

Needs work

Version

2.0

Component

Miscellaneous

Created by

πŸ‡§πŸ‡·Brazil paulocs Belo Horizonte

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @paulocs
  • πŸ‡¦πŸ‡ΊAustralia ThomWilhelm Sydney

    If 2.x is also the Recommended version, could we mark this as such on the project page?

  • Status changed to Needs work 25 days ago
  • πŸ‡«πŸ‡·France DYdave

    Hi Todd (@Todd Nienkerk),

    Could you please help us change the default branch of the module to the current 2.0.x in the Gitlab repository?

    It is starting to become particularly painful and costly having to rebase merge requests on Gitlab manually.

    Most of the merge requests received now in the Gitlab repo are targeting the 2.0.x branch.
    But since it isn't currently the default branch configured, Gitlab is unable to properly automatically rebase the merge requests through the interface and requires additional manual work.

    Although I have the chance to be one of the maintainers of the block_class module, I don't seem to have the required level of permissions to access the Maintainers tab and Settings in the project's Gitlab repo at:
    https://git.drupalcode.org/project/block_class/-/settings/repository
    (I'm getting a 404)
    Otherwise I would have done it myself already πŸ˜…

    See the very clear DO documentation: Maintainership: Setting a default branch β†’
    for the detailed steps to access the repo's settings form and change the default branch, which should only take 5 minutes.

    I think this change/operation might require the user marked as the author of the module and that's why we are contacting you directly Todd (@Todd Nienkerk), but if anyone else among module maintainers would have that kind of access, some help would definitely be greatly appreciated.

    Lastly, if there is any particular reason the current default branch 8.x-1.x shouldn't be updated, please let us know and maybe we will try finding other options or solutions, but in the current state it doesn't really seem viable in terms of the amount of extra work it creates for all of us, whether creating MRs, rebasing, etc...

    Bumping ticket to Major as an attempt to attract maintainers attention: Too much extra work maintaining merge requests.

    Feel free to let us know if you have any questions or concerns on this comment, or the ticket in general, we would certainly be happy to help.
    Thanks in advance!

Production build 0.69.0 2024