#6395 Merge two git repositories in Pagure
Closed: Fixed Opened by jflory7.

Related bug filed against Pagure in pagure#2624.

Summary

An unused but also inaccessible repository needs to be deleted (fedora-badges). Then, an existing repo should be renamed to the freed namespace (Fedora-Badges => fedora-badges). One playbook will need to be updated after the name change (fedora-badges-assets to be moved into fedora-badges, see discussion here).

Explanation

The unused / inaccessible repository was originally created by @aikidouke for testing the migration of Fedora Badges ticketing / design assets to Pagure. We never ended up deleting it later, and now, when we try to access it, the repository redirects to the current repository. See the Pagure bug above for more information.

It would be helpful if the old repository, fedora-badges, could be deleted. Later, we will rename the Fedora-Badges repo to fedora-badges.


Just removing the lower case project from the DB should fix the entire issue, no need for data migration of playbook change, I think :)

@pingou I think since we're looking at merging the fedora-badges-assets repo together into fedora-badges, that's why the playbook would be updated.

@pingou In the Pagure ticket, you deleted the old repo, but if I run…

git clone ssh://git@pagure.io/fedora-badges.git

…it will give me the old repo still. Is there any data lingering around still?

Ok Fedora-Badges has been renamed to fedora-badges so all existing clones need to be re-cloned.

I also adjusted playbooks/manual/push-badges.yml for the case change.

I'm not quite sure what should be done for fedora-badges-assets.

@pingou Thanks for your help. @sayanchowdhury manually deleted the repo, so this ticket is good to close. :clapper:

Metadata Update from @jflory7:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata