As part of Drupal.org’s increasing use of GitLab, we are looking for ways to reduce maintenance, so we have time to do the migration and for ongoing GitLab maintenance and upgrades. The most time went into Drupal.org’s database of commits/labels/etc. The Git instructions use the labels, specifically branches. Our database of those is going away.

“Branch to work from” select menu
If we want to preserve this, it would be an API request to GitLab to fetch all the branches. That would be very slow. We may want to remove this element.

Currently release branches, those with dev releases, are separated from all other branches. We do have the release branch labels in a field, we could show a menu of just the release branches. That would be loading every dev release for the project and getting field_release_vcs_label.
screenshot

“Tag for a stable release” instructions
These are shown when looking at a release branch. We can just show them all the time. It’s not a requirement to make releases from release branches. For security releases, it’s best to not do that, so a release with only the security fixes can be made.

CommentFileSizeAuthor
#3 Project Git instructions Screen Shot.png174.12 KBirinaz

Comments

drumm created an issue. See original summary.

drumm’s picture

Of the 5,000 most recent requests for these pages, ~400 were for a specific branch, about 8%. These look like they are mostly release branches.

irinaz’s picture

StatusFileSize
new174.12 KB
irinaz’s picture

Issue summary: View changes
irinaz’s picture

Issue summary: View changes
drumm’s picture

Status: Active » Needs review

Forgot I wasn't working in an issue fork, so missed the commit message.

I went with listing the release branches in the select menu.

drumm’s picture

Status: Needs review » Fixed

This has been deployed.

Status: Fixed » Closed (fixed)

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