Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Steps to reproduce:
- Click on the Edit tab for any project release with multiple branches that you maintain.
- You'll notice that the
Git branch
is disabled.
Example: https://drupal.org/node/747432
Comment | File | Size | Author |
---|---|---|---|
#7 | 0001-Issue-2127029-Use-the-right-variable-to-find-version.patch | 1.76 KB | marvil07 |
#2 | edit-release.png | 7.81 KB | andypost |
Comments
Comment #1
colanStrange. It seems to work now. I'll leave this open to see if anyone runs into the same problem.
Comment #2
andypostDefault branch change works fine, but there's no way to change release branch from
master
to7.x-1.x
I get this on Imagecache profiles module dev release https://drupal.org/node/747432 following https://drupal.org/empty-git-master instructions to remove
master
branchComment #3
andypostComment #4
tvn CreditAttribution: tvn commentedComment #5
dwwWhen I first saw the title of this issue in the queue I thought "Right, that's by design". But carefully reading the issue, you're actually talking about the edge-case where you've got releases pointing to 'master' that have a real version string (e.g. 7.x-1.x-dev) and wanting to move those to point to the corresponding named branch (7.x-1.x) once that branch exists.
Yes, there used to be special-case code in versioncontrol_release to make this possible. It was supposedly ported to D7, but probably never tested. This is a rare edge-case, so I'm not surprised it wasn't properly ported. Note that these releases only exist from before the Git migration. ;) It's no longer possible to create new releases pointing to 'master'.
Anyway, giving this a more accurate title so that it's more obvious what's actually going wrong. Technically, we should move this to the versioncontrol_project queue, since that's where versioncontrol_release lives which is where the code is that needs to be tested/fixed. However, there's some question as to what the issue workflow should be (#2129357: Suggestion to D7QA bug vetting process) so for now, I'll leave it in this queue.
Cheers,
-Derek
Comment #6
tvn CreditAttribution: tvn commentedComment #7
marvil07 CreditAttribution: marvil07 commentedAttached patch I'll be adding to 7.x-1.x.
Comment #9
marvil07 CreditAttribution: marvil07 commentedAdded.
Comment #10
drummNow deployed on Drupal.org.