Problem/Motivation

When you create a new issue, there is the option audit audit 5.x-1.x-dev, from the previous project, it can also be seen on GitLab.

Steps to reproduce

Proposed resolution

Some users may think that the highest number is the latest dev-version ... Can that audit 5.x-1.x-dev branch be deleted?

Remaining tasks

User interface changes

API changes

Data model changes

Comments

ressa created an issue. See original summary.

trebormc’s picture

trebormc
Primary language Catalan
commented
Version: 1.x-dev » 5.x-1.x-dev

I tried deleting the 5.x-1.x branch and GitLab refuses with "Prevented by server hooks". The reason is the old audit 5.x-1.x-dev release from February 2007, which is still attached to that branch. This project is a recycled namespace, it was an abandoned Drupal 5 module before I took it over, so that release has nothing to do with the current code and there is no upgrade path between them.

I cannot delete the release myself, maintainers do not have that permission, so I have opened a request with the infrastructure team: https://www.drupal.org/project/infrastructure/issues/3606938

Once they remove it I should be able to delete the branch and leave the repository clean, and the 5.x-1.x-dev option should stop showing up in the version dropdown. Leaving this open until then.

ressa’s picture

ressa
he/him
commented
Status: Active » Postponed

Thank you for following up on this so quickly, and asking for assistance from the Infrastructure team in Git - (Module Audit) Delete legacy 5.x-1.x-dev release so the obsolete branch can be removed (recycled namespace) I hope it's possible. Getting things cleaned up for a fresh start would be very nice.

trebormc’s picture

trebormc
Primary language Catalan
commented

Update: the infrastructure team closed the request. Releases are never deleted from Drupal.org, dev releases included, so the old release stays and the server hook keeps blocking the branch deletion.

Nothing I can do as a maintainer for now. Once the issues for this project are moved to GitLab I will control the version options myself and I will retry removing both the option and the branch. No date for that migration yet, so I am leaving this postponed.

For the record: 1.x is the only active branch, anything under 5.x-1.x is the old unrelated module.

ressa’s picture

ressa
he/him
commented

Thank you for the update, I appreciate that you will take a look at this later, when the project is moved to GitLab.

It will be interesting to see if this is possible, since other projects who took over an old name space might want to do a clean up as well, so in that sense this project could become a pioneer.