Forking private git repo in github.com

I wonder if this is possible.

I have a “starter project” in github (private repository). What I like to do is create customerA repo (also private) but it should be forked from the “starter project”. My idea is that Customer B, Customer C, all could have their own private repo and if I fix a bug which are generic in the “starter project”, I can then pull the bug fix to all my customer easily.

  • Eclipse + Maven Plugin + EGit Plugin = Checkout from GitHub a specific Branche and Tag?
  • Starting vim-fugitive from command line
  • Create Openshift app using branch from existing repository (with `rhc create`)
  • undoing accidental git merge without regressing history
  • Unable to checkout git submodule path
  • How to take local working directory to any git revision irrespective of its branch after remote changes?
  • I have not found anyway to solve this. Currently I solved this via cloning the sampe private project.. is it a git issue or github.com issue?

    any work around?

  • Cygwin ssh key added, but Git permission denied (publickey)
  • Can I add a file to one of my GitHub repositories without cloning / pulling from it?
  • Push to GitLab repository within CI server (deploy keys)
  • “Migrating” existing Git repository to Gerrit Code Revision
  • Speeding up Jenkins build
  • Attaching network storage to a Docker container for Gitlab (ssh issue)
  • 2 Solutions collect form web for “Forking private git repo in github.com”

    This is what branches are for. Each customer gets a branch, problem solved.

    But… if each customer’s repository is in a separate account, you can just use the usual git tools to share changes. As an example:

    $ git clone git@github.com:client/your-project
    $ cd your-project
    $ git remote add original git@github.com:you/your-project
    $ git fetch original
    $ git cherry-pick <change from original>
    $ git merge <whatever>
    $ git rebase <whatever>
    $ git push origin
    

    etc.

    Github’s web UI is just a convenience for the common cases. If you need to do something uncommon, just use your usual git tools. Github does not care.

    For Git, cloning is the same as forking, or to be more precise: Git doesn’t know forking, that’s a github thing. Technically all forks are simply clones with different owners.

    So if you’d clone your starter project for three customers you effectively have a single repository with multiple branches because each fork is a branch. Maybe you should look into using submodules for your starter project and include it in each customer repository?

    Git Baby is a git and github fan, let's start git clone.