Richard Shaw wrote on Mon, May 18, 2020: > > Seems to work for me: > > Don't know what's wrong then... I went back and re-read your first mail, it is possible it doesn't work on one of your own projects? I'm not sure how much sense there is in forking your own repo... > Ok, so this is the opposite workflow where you only clone the main repo and > create a remote for your fork. Would be nice if this was documented but > google didn't turn up anything useful for me. The only documentation I > could find still says to do the opposite. Clone your fork and add the > original as the remote (github style). Well you have to clone *something* so fedpkg would know what to fork. I've just done a "fedpkg clone" of a repo to look at it, then assumed fork would do what hitting fork does on the web ui and this is pretty close. I wouldn't want the command to change what origin is, although I'm not sure how `fedpkg push` works I intended to use plain git commands for that... OTOH something did not work, the remote was setup for ssh://any@xxxxxxxxxxxxxxxxxxxxxx/... and I had assumed there is a magic account with all ssh public keys that does redirection (like github does, everything happens under user 'git') but that didn't work; I had to change the url to specify my user. I might need to specify --user xyz next time... -- Dominique _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
