Recently there was a change of ownership of a sandbox project I am working on was done. It seems to have caused problems for being able to use git on it. It looks like it is not enough to just change the "author" field of the project page for a transition to work. This due to that the username is part of both the project URL for the web and git interfaces.
See #2114933: Change ownership of sandbox project possible? for info on the ownership change and #2227449: Issue with git repository? for info on how this problem was discovered and confirmed.
My guess is that this probably was the first time a sandbox-project changed owner and this simply was an unforeseen side-effect.
Comments
Comment #1
tvn commentedComment #2
tsvenson commentedHi all,
Just wondering if there is a way to manually change the URLs so that the info in the "Version control" can work directly.
The problem is that the URLs still use the old owners account in them, but when the owner was switched the URLs wasn't updated to reflect that.
Old (still working): https://www.drupal.org/sandbox/DrupalMill/2044339
New (not working): https://www.drupal.org/sandbox/tsvenson/2044339
This is both for the project page and for all the git commands.
While it is not a big problem, when you know about it, I believe it would be nice if it could be fixed.
Comment #3
drummThe sandbox URLs are a Drupal.org customization. We do have code to update them, for when a project is promoted from a sandbox to a full project. We could expand that to run in this case, the code sets up the Git repo how it is "supposed" to look. However, except for that case, we avoid changing Git repo URLs. When a Git remote changes, that breaks everyone's clones; they have to change the remote or re-clone. We can either:
For this specific case, and any other sandboxes with the owner already changed, I can probably clean things up.
Comment #4
tsvenson commentedThanks for looking into this Neil. Would be super if the issues could be cleaned up for this and other sandbox existing in the same situation. Removing the ability change owner of sandboxes is probably the best practice as you describe it.
Would it be much work to add a simple clone-feature for these projects you think? Thus making it a smooth operation to simply hit a clone-button to create a new sandbox with the specific project as base.
Comment #5
drummI committed a change to remove the ability to change a sandbox project’s maintainer. This will likely be deployed a few days after new years.
See #1546660: Project families for a starting point for functionality related to cloning projects.