|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
ferdnyc commented 2 months ago | ||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
pingou commented 5 years ago Isn't that achievable via the issue git repo? Not everyone using pagure will use fedmsg and datagrepper :s | ||
clime commented 5 years ago 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. | ||
pingou commented 5 years ago fedmsg messages are sent, but this recipe won't work on pagure instances not using fedmsg :( | ||
clime commented 5 years ago ah ok. Well not sure. how to get the project ID by another way. | ||
darknao commented 3 years ago you can use Pagure API for that : '''curl -L https://pagure.io/api/0/namespace/projectname | jq '.id'''' | ||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
Documentation to Renaming repositories added into Tips & Tricks section.
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 tomake it 1000% clear to users that they shouldn't literally type (or copy-paste)
things like
move-repo
andmove-repo-new
into their commands?It seems way too easy to mistake a string like
move-repo-new
as a commandyou're sending to Pagure, rather than a placeholder repo name.