Skip to content

Instantly share code, notes, and snippets.

@haydenflinner

haydenflinner/gist:a60abe2d2a1d666d8c8d25f26aaf4a5c

Forked from jagregory/gist:710671
Created September 21, 2025 01:05
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save haydenflinner/a60abe2d2a1d666d8c8d25f26aaf4a5c to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save haydenflinner/a60abe2d2a1d666d8c8d25f26aaf4a5c to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. @jagregory jagregory created this gist Nov 22, 2010.
    28 changes: 28 additions & 0 deletions gistfile1.txt
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,28 @@
    So you've cloned somebody's repo from github, but now you want to fork it and contribute back. Never fear!

    Technically, when you fork "origin" should be your fork and "upstream" should be the project you forked; however, if you're willing to break this convention then it's easy.

    * Off the top of my head *

    1. Fork their repo on Github
    2. In your local, add a new remote to your fork; then fetch it, and push your changes up to it

    git remote add my-fork [email protected]
    git fetch my-fork
    git push my-fork

    Otherwise, if you want to follow convention:

    1. Fork their repo on Github
    2. In your local, rename your origin remote to upstream

    git remote rename origin upstream

    3. Add a new origin

    git remote add origin [email protected]

    4. Fetch & push

    git fetch origin
    git push origin