So this is more a problem for repos that have lived a long time already on github? It guess it should impede someone using their account as a staging point for migrating from Smalltalkhub projects to a community github repo. Although an alternate way to consider this is that the forwarding submerges a problem to be forgotten until it causes a mystery problem later on. Forking the repo back into your account and deleting the "master" branch might be fail-fast way to expose and fix issues. (emphasis on the "might" - I'm not sure of all the trade-offs) cheers -ben On Thu, 11 Oct 2018 at 14:36, Norbert Hartl <norbert@hartl.name> wrote:
Well, you can but then the access is not forwarded anymore to the repo youâve transferred. Transferring and forking makes everyone link something they maybe donât want. Transferring and creating a new one with the same name brings all request to the former to your new repo which is unlikely to be wanted.
Norbert
Am 11.10.2018 um 07:49 schrieb Esteban Lorenzano <estebanlm@gmail.com>:
Why not?
On 10 Oct 2018, at 17:55, Norbert Hartl <norbert@hartl.name> wrote:
No, that you cannot
Am 10.10.2018 um 16:36 schrieb Sean P. DeNigris <sean@clipperadams.com :
NorbertHartl wrote
The rest is provided by github as long as you do not create a new repository with the same name.
Can you still fork the transferred repo in your personal account? I wasn't sure, which is why I didn't handle Artefact this way.
----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html