Skip to content

Instantly share code, notes, and snippets.

View tzinsky's full-sized avatar

Tim Zinsky tzinsky

1 follower · 1 following
View GitHub Profile
@tzinsky
tzinsky / Python3 Virtualenv Setup.md
Created March 17, 2022 03:53 — forked from pandafulmanda/Python3 Virtualenv Setup.md
Setting up and using Python3 Virtualenv on Mac

Python3 Virtualenv Setup

Requirements
  • Python 3
  • Pip 3
$ brew install python3
@tzinsky
tzinsky / switch-local-git-repo-to-fork.md
Last active May 10, 2022 17:48 — forked from ElectricRCAircraftGuy/switch-local-git-repo-to-fork.md
How to move to a fork after cloning

If you are like me you find yourself cloning a repo, making some proposed changes and then deciding to later contributing back using the GitHub Flow convention. Below is a set of instructions I've developed for myself on how to deal with this scenario and an explanation of why it matters based on jagregory's gist.

To follow GitHub flow you should really have created a fork initially as a public representation of the forked repository and the clone that instead. My understanding is that the typical setup would have your local repository pointing to your fork as origin and the original forked repository as upstream so that you can use these keywords in other git commands.

  1. Clone some repo (you've probably already done this step).

    git clone git@github...some-repo.git