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.
See the meta issue for background: #1076616: Projects should have "master" renamed to appropriate branch
In order for testbot to work, the dev release, 5.x-1.x-dev http://drupal.org/node/243803, needs to be based on a properly named development branch. The process to do that is documented at http://drupal.org/node/1127732
Comments
Comment #1
hass CreditAttribution: hass commentedAre you trying to tell me that the suxxx git migration process failed again? Feel free to tell the git migration team to fix their outstanding migration bugs.
Comment #2
Josh The Geek CreditAttribution: Josh The Geek commentedI'm not sure this should be leftovers, but at least part of the reason this didn't happen is the fact it was lost w/out any tags.
Comment #3
rfayDue to the hostile response, I've turned off automated testing on Link Checker. That resolves this issue.
All we were asking was for you to cut a reasonable branch. Geez.
Comment #4
hass CreditAttribution: hass commentedIt's not my job to fix the git migration team bugs. I have never maintained 5.x-1.x and i do not care about this branch. It could also get deleted at all.
Comment #5
Josh The Geek CreditAttribution: Josh The Geek commentedhass: This is not a bug. Testable projects now need to have a properly named branch instead of master. You can ignore now because rfay turned off testing. So, fixed.
Comment #6
hass CreditAttribution: hass commentedThe reason is - that git migration is buggy. This should have heen fixed with the migration if required. Enable testing in linkchecker! Nobody pleased you to disable it. Git migration team had all permissions. Otherwise they wouldn't have been able to remove files from my projects or alter all files to remove cvs tags as example. In this phase this should have been done, too.
Comment #7
Josh The Geek CreditAttribution: Josh The Geek commentedI can't turn testing back on, but all you need to do is
Correct me if I'm wrong, but then you can edit your release to point it at the 5.x-1.x branch. Testing should then work fine.
Comment #8
rfayJust so you know, if anything this is a bug in the PIFR testbot system.
The initial post explained exactly what to do. The instructions in #7 aren't quite right, but the original post gave the full info.
Comment #9
hass CreditAttribution: hass commentedI do not have git command line. Git migration team should have done this task for all maintainers. It's a migration bug. This was not required in past and this is why it need to be solved globally. There are no EGit docs available.
Otherwise... Delete the 1.x branch and releases for me. They are not maintained and i see no reason why i should do anything with it including tagging.
Comment #10
hass CreditAttribution: hass commentedGuys, I cannot use master as origin of 5.x-1.x. I have no clue who have destroyed this, but as said - I have NO git command on my windows box and additional to this - where the heck is the code gone that have been in 5.x-1.x-dev? If I would push master into 5.x-1.x branch I have D7 code in a D5 branch and all 5.x code is lost. Where is the 5.x-1.x-dev branch code gone? It was in CVS...
Where is a backup of these data?
Comment #11
hass CreditAttribution: hass commentedShit on the lost data.
Re-enable patch testing for linkchecker module, please. The dead branch has been added and assigned.
Comment #12
rfay@hass everybody can now turn on patch testing for their own projects (6.x+)
I don't really understand what you're after in #10 but you can turn on your own patch testing. Edit->Issues->Enable Automated testing.
Comment #13
hass CreditAttribution: hass commentedThx... This is what i searched for under automates testing... Usability issue.