Documentation to Renaming repositories added into Tips & Tricks section.
Isn't that achievable via the issue git repo? Not everyone using pagure will use fedmsg and datagrepper :s
I don't see project ID in the issue tickets. I thought fedmsg for a new project is always being sent so I thought this is not such a big deal.
fedmsg messages are sent, but this recipe won't work on pagure instances not using fedmsg :(
ah ok. Well not sure. how to get the project ID by another way.
you can use Pagure API for that : '''curl -L https://pagure.io/api/0/namespace/projectname | jq '.id''''
pretty please pagure-ci rebuild
I know this is outdated/abandoned, but just as a general form thing, couldn't we use $OLDREPO and $NEWREPO (respectively) for the names, just to make it 1000% clear to users that they shouldn't literally type (or copy-paste) things like move-repo and move-repo-new into their commands?
$OLDREPO
$NEWREPO
move-repo
move-repo-new
It seems way too easy to mistake a string like move-repo-new as a command you're sending to Pagure, rather than a placeholder repo name.
This project has moved to https://forge.fedoraproject.org/apps/pagure. As part of the migration, all open pull requests on pagure.io have been closed. If you'd like to continue working on this, please fork the repository on the new forge and re-submit your PR there.
Pull-Request has been closed by ryanlerch
Documentation to Renaming repositories added into Tips & Tricks section.