Dear Community:
The Openpilot Community needs your help to continue to keep opc.ai's lights on and support the path to Workbench v0.2. With only a one person crew and without commercial funding it's not always financially feasible to fund these services out of pocket. Please consider becoming a Patreon supporter of the Openpilot Community project and receive exclusive perks and benefits!
Become a patreon Learn more Maybe Later

cmma
Mar 01·2 min read

Understanding Github forks and Branches.

So you have tried the official OP and now you want to try the gimmicks, optimization done by community's forks but do not know how Github forks works in general. So following i will give example to understand almost everything as far as branches and forks goes.

Username:

  • Every Github user has a username which is linked within url itself example:
    github.com/commaai

      Please note after github.com there is commaai(which is username)
    

Repo:

  • after username in link it comes with repo name so openpilot is repo name
    github.com/commaai/openpilot

Branches:

  • As default you will be on release2 branch however if you want to let's say switch to devel which gets the latest fixes and sometime bugs then you will need branch name. In order to see all of the branches that users has and see which has been recently updated you will click on braches on github repo following i will give default url where you will replace username.
    https://github.com/username/openpilot/branches
    official comma repo branches
    https://github.com/commaai/openpilot/branches

So now you know the branches name and want to switch to devel you will just use the following AIO script.

cd /data && rm -rf openpilot* && git clone https://github.com/username/openpilot && cd openpilot && git checkout branchname && reboot

now devel AIO script

cd /data && rm -rf openpilot* && git clone https://github.com/commaai/openpilot && cd openpilot && git checkout devel && reboot