Onefinity github question

Machines (Original/PRO) Controller (Buildbotics) Discussion
6

Hey Tim,

just to prevent any shyness:

Git Quick Start:

  • Download Git from the Git Download page.
    Installation depends on which Operating System you run on your PC. See:

    Under Debian GNU/Linux and many of its derivates it would go this way:
    apt-get install git git-doc

  • After installation, you would create a folder for working with Git, e.g. called ‘git’:
    e.g. mkdir git or whatever you do to create a folder on your Operating system.

  • Then you would do:

    cd git # move into the folder you created
git config --global user.name "Firstname Name" # Note: If you skip this step, git will  guess your name using your system information
git config --global user.email name@example.com # Note: If you skip this step, git will guess your e-mail address using your system information

    git clone git://github.com/OneFinityCNC/onefinity-firmware.git

That’s it, now you have a clone of the Onefinity-firmware codebase on your computer and you can start to edit it (offline).

For the next steps follow the Git Tutorial: Using Git for collaboration.

By the way, you can also have a look at Buildbotics firmware by using

    git clone git://github.com/buildbotics/bbctrl-firmware.git

Advanced Git Usage

The Pro Git Book is very good and intelligible. Advanced topics in the Pro Git Book are then

In order to contribute to a repository that is hosted on GitHub, you create an account and you “fork” the project under your username. This is not a fork in the classical meaning of the word “fork”, it’s just a work copy on the github.com site. After you’ve cloned this own work copy to your local computer (with the “clone” command shown above), you create a topic branch, you work on what you want to contribute, and when you’re done then you push your contributions to your “fork” on github.com.

Then you create a pull request on the github.com site to make the owner of the original repository aware of your contribution. This has the advantage that any user can contribute without having push access to the original repository.

If you don’t want to register at GitHub.com, you can still work on your copy of the repository and after you’re done with the work you want to contribute, you create a patch and submit it to the owner of the repository. This is the classical way (outside of github.com) if you have no push access to a repository and are not running your own git server. See git diff and git format-patch.

1 Like