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

Instructions for Gitlab:
https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or...

Comments

paulocs created an issue. See original summary.

chris matthews’s picture

thomwilhelm’s picture

StatusFileSize
new107.7 KB

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

dydave’s picture

Priority: Normal » Major
Status: Active » Needs work

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!

trackleft2’s picture

Title: Set default branch to 2.0.x » Set default branch to 4.0.x

Update the title to use the new correct default version.

trackleft2’s picture

Version: 2.0.x-dev » 4.0.x-dev
trackleft2’s picture

trackleft2’s picture

Issue summary: View changes
berenddeboer’s picture

Assigned: Unassigned » berenddeboer
Status: Needs work » Needs review

I've changed this, did this work? And why 2.0.x and not 4.0.x??

berenddeboer’s picture

Ah yes, just reading the title update, have now set it to 4.0.x.

dydave’s picture

Status: Needs review » Fixed

Nice one Berend (@berenddeboer)!

Thanks a lot! 👍

I "think" it works 🟢: Browsing to:
https://git.drupalcode.org/project/block_class
Shows the 4.0.x branch selected by default! 🥳

oh! and I've seen you've added me as Maintainer in the Gitlab project repo!! 🤩

Thanks you so much for your help and the prompt reply!! 🙏
That's super nice! 😊

We should have tried reaching you ages ago 😅

Since I think we should have answered the initial request in this ticket, marking it as Fixed, for now 🥳
That's a very pleasant unexpected surprise, to be able to cross this one off of our list 😆

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.