Skip to content
Snippets Groups Projects
New look: Off

We need an easier way for devs to have a public and a private fork of a single repo.

    • Closed Issue created by Nick Mathewson @nickm

    The goal

    Try creating two forks of a single repository: one public, one private. The private repository would be for working on confidential fixes; the public one for everything else.

    Specifically, I want to leave my current nickm/tor project alone, but create a private repository called nickm/tor-private that is also a fork of tpo/core/tor.

    The actuality

    Hoo boy. As near as I can tell, this is very hard to do from the web interface. I think you could do it by creating one fork, then creating another fork in another namespace, then renaming the second fork and transferring the second fork to the first namespace. But that's nontrivial and non-obvious, and requires that you have two namespaces to work with.

    Another possibility is to fork the repository via the API, which is nontrivial. I think doing it via the API may also require admin access.

    Another possibility is to create a new repository, then create a fork relationship between the parent repository and the child repository. That requires admin access.

    Suggested next steps

    If there's an easy way to do this, please let me know what it is.

    If there isn't, then could somebody with fork access please add a fork relationship from 426 (tpo/core/tor) to 628 (nickm/tor-private)? (That is, please mark my private repository has having forked from the main tor repository.)

    In either case, let's document what our preferred way to do this is.

    Edited
    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items 0

    • No child items are currently assigned. Use child items to break down this issue into smaller parts.

    Activity

    Please register or sign in to reply