Developing FreeCAD with GitKraken

Foreword
FreeCAD uses Git to manage its source code. This document is a cursory introduction to GitKraken, a graphical user interface to Git. GitKraken is proprietary software that is free to use for non-commercial use; you don't need GitKraken to develop code for FreeCAD but many developers like it, and find it useful to manage their development. FreeCAD doesn't endorse GitKraken but we hope a guide like this one shows users how easy it is to set up the development environment and encourages more people to contribute.

For more information on general Git usage from the command line see Source code management, and the online Pro Git book. To compile FreeCAD see Compiling.

Introduction
Git is a powerful revision control system commonly used to track computer code development. Although it is a complex system, you usually only need some background information on how it works, and to know a few terminal commands. A graphical user interface (GUI) eases the learning curve. GitKraken is a proprietary program that is free to use for non-commercial use that runs on the Electron framework, which means it is cross platform and can be used the same in Linux, MacOS, and Windows.

Setting up Git development
There are different ways to download GitKraken depending on your operating system. In Linux distributions, sometimes you can get it from the package manager.

  Download GitKraken.  In your web browser go to: https://github.com/FreeCAD/FreeCAD.  Click the Fork button. This will clone the repository to your own account. In other words the URL to access your fork will be: https://github.com/GITHUBUSERNAME/FreeCAD.git   Open GitKraken, go to, and enter this address.  GitKraken will now your personal repository.

Please read the difference between origin vs. upstream remote repository. Essentially, your fork of FreeCAD is the repository, while the official FreeCAD repository is. You now need to set the upstream accordingly.  Go to, or press the + combination in your keyboard. Enter the following to set up your remote repository. git remote add upstream https://github.com/FreeCAD/FreeCAD.git   Now check the remote branches you have set: git remote -v

You should see something like this in the terminal:  origin	https://github.com/foobar/FreeCAD (fetch) origin	https://github.com/foobar/FreeCAD (push) upstream	https://github.com/FreeCAD/FreeCAD.git (fetch) upstream	https://github.com/FreeCAD/FreeCAD.git (push)  Switch back to GitKraken interface. On the left side of the screen you will see a sidebar with a section labeled Local; double click on the branch so you switch to it. In the command line, this is equivalent to git checkout master </li>  Click on the Push icon on the top right side of the interface. This will push your Local master to your Remote origin master</li> </ol>

The GitKraken interface
For more information consult the GitKraken Getting started guide.



In the image, the remote the Local master and Remote origin master branches are three commits behind the Remote upstream master, that is, the official FreeCAD source code. This is indicated by the icons being three steps behind in the chain that represents the commit history of the master branch. See Rebasing to update the branches that are behind.

Rebasing

 * Checkout the Local master branch by double clicking on it
 * Move the mouse to the last upstream commit, right click, and choose Rebase master onto upstream/master
 * Now press the Push button . This pushes from your Local master to the Remote origin master.



Branches
Branches are a feature that makes Git powerful compared to other revision systems. Branches aren't complete forks, but rather define snapshots where a version of the code starts diverging from the master branch. Whenever you want to modify the FreeCAD code, first create a branch, then make changes, and then merge your commits back to the master branch. With Git it is simple to create, merge and delete branches when you no longer need them. Please read Branching and Merging to understand more about this process in GitKraken.


 * 1) Make sure you currently have the master branch active (double click on it, ). In GitKraken the Local master branch should be highlighted in green.
 * 2) Click the Branch button to create a new branch and enter its new name.

Making pull requests
Pull requests (PRs) are necessary to merge the code in a branch in your local repository with the code in the repository. To summarize the process, once you've modified your branch, you need to push it to your GitHub fork, and from there make a pull request to. GitKraken saves you some clicks to easily create pull requests instead of using GitHub's interface.

Steps in GitKraken:
 * Find you local branch on the interface and make sure it's active (double click on it).
 * Right click the branch name and find the option to Push <your-branch-name> and start a pull request.
 * GitKraken will open a dialog that asks you to confirm the repository which your branch will use to pull and push. It will then push your local branch to that remote repository.




 * GitKraken will ask you what you want to call the remote branch. The default name is the same name that the branch has locally in your computer.


 * GitKraken then opens up another dialog asking the repositories and branches to merge, and the direction (from and to).
 * You normally want to merge from the remote origin <your-branch-name> to the remote upstream master branch . Be sure to enter a good title for the pull request, and write a more descriptive paragraph if your changes are significant. Consult the official documentation of GitKraken for more information.



Resolving merge conflicts
GitKraken has a special merge conflict tool that is only accessible in the GitKraken Pro version. However, there are workarounds to use external tools for merging.
 * GitKraken compatible external merge tools: Beyond Compare, FileMerge, Kaleidoscope, KDiff, Araxis, P4Merge
 * If none of the above options work for you, it's possible to specify External merge and diff tools within the configuration file in your user's home directory.

Squashing commits
As a revision control system Git encourages making many commits to keep track of your changes; however, if you have too many small changes the commit history may look a bit messy. Squashing is condensing various commits into only one commit. From the GitKraken manual, squashing is available for commits that meet the following requirements:
 * You need to select at least two commits to squash.
 * The youngest commit, by commit date, is also the current HEAD commit.
 * Genealogically consecutive.
 * Chronologically consecutive.
 * The oldest commit in the list has a parent.

If all these conditions are met, the Squash option appears when you right click the commit node. See Squash.gif

Following other FreeCAD repositories
You can use GitKraken to follow the personal FreeCAD forks of other developers; in this way you can see how they write code and commit changes to their own branches before they submit pull requests to the upstream repository.
 * 1) In the left side panel next to the Remote category, press the + sign.
 * 2) A dialogue will come up to enter the name of the repository that you want to add. Recommended remotes are from the main FreeCAD developers and known contributors: wmayer, yorikvanhavre, ickby, sliptonic, kkremitzki, etc.
 * 3) Press Add Remote.

Now whenever new commits are made, or branches are rebased, by the authors of those repositories, you will see their commit history in a graphical way.

Related

 * Source code management
 * Developing FreeCAD with KDevelop