Source code management/de

Einführung
Das Haupt Quellcode Verwaltungswerkzeug für das FreeCAD Projekt ist Git, das in den meisten Betriebssystemen einfach über einen Paketmanager oder direkt von der Website von Git installiert werden kann. Es wird empfohlen, sich mit Git vertraut zu machen, bevor du direkt mit dem FreeCAD Quellcode arbeitest. Besuche die Seite Git Dokumentation für das Referenzhandbuch sowie das Pro Git Buch, um zu lernen, das System allgemein zu nutzen. Das vorliegende Dokument konzentriert sich auf die Verwendung von Git für die FreeCAD Entwicklung. Die Kompilierung von FreeCAD ist unter Kompilieren beschrieben.

Während Git in erster Linie eine Terminalanwendung ist, gibt es viele grafische Anwendungen, die die Arbeit mit Zweigen, das Anwenden von Patches und das Senden von Pull Anfragen an einen Master Zweig erleichtern. Beispiele sind gitk (die erste entwickelte grafische Benutzeroberfläche),gitg (Gnome),qgit (Qt), tig (Ncurses), git-cola und GitKraken (proprietär). Eine kurze Einführung in dieses Werkzeug findest Du unter Entwicklung von FreeCAD mit GitKraken.

Hinweis: Wenn dir davon schwindelig wird, gibt es eine sehr gute nicht-technische Serie über die Verwendung von Git und Github mit dem Titel 'Git und Github für Dichter'.

Quellcodezugang
Jeder kann auf den FreeCAD Quellcode zugreifen und eine Kopie davon bekommen, aber nur die FreeCAD Projektmanager haben Schreibzugriff darauf. Du kannst eine Kopie des Codes erhalten, ihn studieren und nach Belieben ändern, aber wenn du möchtest, dass deine Änderungen in den offiziellen Quellcode aufgenommen werden, musst du eine "Pull Anfrage" gegen das Haupt Repositorium durchführen, damit deine Änderungen von den Verwaltern überprüft werden können. Diese Art der Entwicklung ist bekannt als der Dictator and Lieutenants Workflow, da die Kern Entwickler (Diktatoren) und betrauten Entwickler (Leutnante) den Code filtern, der von unabhängigen Entwicklern und Benutzern eingereicht wird.

Wenn deine Quellcode Änderungen signifikant sind, empfehlen wir dir, sie im Pull Request Abschnitt des FreeCAD-Forum zu erklären.



Offizielles GitHub Repositorium
Der FreeCAD Quellcode wird in Github bereitgestellt, https://github.com/FreeCAD/FreeCAD

The FreeCAD source code is hosted on Github, https://github.com/FreeCAD/FreeCAD

Um Code beitragen zu können, benötigst Du ein GitHub Konto.

In der Vergangenheit wurde der Quellcode in einem SVN Repositorium bereitgestellt, https://free-cad.svn.sourceforge.net/svnroot/free-cad. Dieser wurde am 10. Oktober 2011 mit commit 120ca87015 nach GitHub verschoben.


 * Daher gibt es viele Änderungen, die vor dieser Zeit vorgenommen wurden, die nicht in der modernen Git Commit Geschichte aufgezeichnet sind. Lies mehr dazu auf der Seite Geschichte.

Setzen des Git Benutzernamens
Entwickler sollten Code in ihr persönliches Projektarchiv mit ihrem GitHub Benutzernamen eintragen. Wenn dieser nicht bereits global gesetzt ist, kannst du ihn lokal für das aktuelle Git Projektarchiv wie folgt setzen:

Wobei deinen vollständigen Namen oder Spitznamen darstellt, der zur Identifizierung des Autors eines bestimmten Einsatzes verwendet wird, und  den Namen deines Accounts auf GitHub angibt.

Fernrepositorien
Bitte lies Was ist der Unterschied zwischen Ursprung und Upstream auf GitHub? (Stackoverflow) um den Unterschied zwischen und  im Kontext von Git zu verstehen. Dieser Abschnitt erklärt, wie man die richtigen Repositorien für die Entwicklung festlegt. Im Wesentlichen:
 * ist deine persönliche Abspaltung des offiziellen FreeCAD Repositoriums, also https://github.com/GITHUB_USERNAME/FreeCAD
 * ist das offizielle FreeCAD Repositorium, d.h. https://github.com/FreeCAD/FreeCAD

Diese Unterscheidung ist wichtig, da du zuerst Code in deine eigene Kopie des Repositoriums schreiben solltest, bevor du diese Änderungen in das offizielle Repositorium schreibst.

Basierend auf dem oben genannten, gibt es zwei Möglichkeiten, deine Git Entwicklungsumgebung einzurichten:
 * 1. Methode: Verzweigung auf GitHub und klone deine Verzweigung lokal
 * 2. Methode: Klone FreeCAD direkt auf deinen lokalen Rechner und passe die entfernten Server an

Wir empfehlen die 1. Methode, weil sie einen Schritt schneller ist.

1. Methode: Verzweigung auf GitHub und klone deine Abspaltung lokal
Zuerst teile das FreeCAD Repositorium in GitHub ab, dann klone diese persönliche Abspaltung auf deinen Computer, und schließlich lege das Repositorium fest.
 * Anmelden auf dein GitHub Konto.
 * Gehe zum offiziellen FreeCAD Repositorium: https://github.com/FreeCAD/FreeCAD
 * Drücke oben rechts auf der Seite die Taste "Fork". Dadurch wird eine persönliche Kopie des FreeCAD Repositoriums unter deinem GitHub Benutzernamen erstellt:
 * Klone auf deinem Rechner deine neu erstellte FreeCAD Fork. Er wird in einem Verzeichnis erstellt.


 * Sobald der Download abgeschlossen ist, gib das neue Quellverzeichnis ein und lege das Repositorium fest.


 * Bestätige deine Fernrepositorien mit ; die Ausgabe sollte ähnlich wie diese sein


 * Jetzt kann die Entwicklung beginnen.

2. Methode: Klone FreeCAD direkt auf deinen lokalen Rechner
Zuerst wirst du das FreeCAD Repositorium in GitHub abspalten (engl.:fork ‚Gabel‘), jedoch wirst du das ursprüngliche FreeCAD Repositorium auf deinen lokalen Rechner klonen und dann deine Fernbedienungen über das Terminal ändern.
 * Anmelden auf dein GitHub Konto.
 * Gehe zum offiziellen FreeCAD Repositorium: https://github.com/FreeCAD/FreeCAD
 * Klicke oben rechts auf der Seite auf die "Fork" Schaltfläche. Dadurch wird eine persönliche Kopie des FreeCAD Repositoriums unter deinem GitHub Benutzernamen erstellt:
 * Klone das ursprüngliche FreeCAD Repositorium. Es wird in einem Verzeichnis erstellt.


 * Sobald das Herunterladen abgeschlossen ist, gib das neue Quellverzeichnis ein und lege das s Repositorium fest.


 * Richte dann das Repositorium ein.


 * Bestätige deine Fernrepositorien mit ; die Ausgabe sollte ähnlich wie diese sein


 * Jetzt kann die Entwicklung beginnen.

Wenn die Fernrepositorien aus irgendeinem Grund zwar existieren, aber auf die falsche Adresse verweisen, kannst du die Situation durch Umbenennen des Namens des entfernten Repositoriums beheben. Beispielsweise sollte auf deine persönliche Abspaltung zeigen; wenn er auf das ursprüngliche FreeCAD Repositorium zeigt, ändere den Namen dieses Fernrepositoriums in  und füge das s Repositorium manuell hinzu.

Du kannst auch weitere Informationen mit dem Schlüsselwort anzeigen.

Verzweigung
Anstatt an der Masterversion des Codes zu arbeiten, empfiehlt die bewährte Methode mit Git die Erstellung eines neuen Zweiges, wann immer du an einer neuen Funktion arbeiten willst. Zweige sind kostengünstig, sie kopieren nicht den gesamten Quellcode Baum, sondern erzeugen lediglich einen Zeitpunkt, an dem Sie Code schreiben werden; daher helfen Zweige dabei, die laufende Arbeit vom Hauptcode getrennt zu halten.

Die Verwendung eines neuen Zweigs erfolgt in zwei Schritten: Zuerst erstellest du den Zweig, und dann wechselst du zu ihm:

Führe alternativ beide Schritte mit einer einzigen Anweisung aus:

Jetzt kannst du Zweige mit ändern, wann immer du daran arbeiten musst. Um die Zweige in deinem Projekt und dem aktuellen Zweig zu sehen, verwende die Operation allein oder füge  oder  für weitere Informationen hinzu:

Nachdem du Änderungen vorgenommen und diese Änderungen übertragen hast, verwende die Operation mit den folgenden Optionen, um die Zweige zu visualisieren

Übergeben
Sobald du dich in einem neuen Zweig befindest, bearbeite die gewünschten Quelldateien mit einem Texteditor. Um zu sehen, welche Dateien geändert wurden, verwende die Operationen und ; wenn du mit den Änderungen zufrieden bist, speichere die Änderungen mit der Operation :

Unlike SVN, you need to specifically tell which files to commit; use the option to save changes in all files that were altered. Your text editor, for example, or, will open to allow you to write a commit message.

Alternatively add the message in the commit itself:

If you create new files or directories, you must use the operation first to add them to the local repository before committing the changes.

Where can be any directory or file.

Writing good commit messages
You should try to work in small steps, that is, commit often, after a small addition in your code. If you cannot summarize your changes in one sentence, then it has probably been too long since you made a commit.

For big changes, it is important that you have helpful and useful descriptions of your work. FreeCAD has adopted a format mentioned in the Pro Git book, which consists of a short message, and then a larger descriptive paragraph.

If you are doing a lot of related work in a branch, you should make many small commits (see a forum post). When you want to merge those changes into the master branch, you should issue

um die einzelnen Übergabe Meldungen zu sehen. Dann kannst du eine Nachricht von hoher Qualität schreiben, wenn eine Zusammenführung durchgeführt wird.

When you merge to master use the option and commit with your quality commit message. This will allow you to be very liberal with your commits and help to provide a good level of detail in commit messages without so many distinct descriptions.

Squashing commits
Squashing refers to the process of combining various consecutive commits into one. This may be desirable if you made many small commits that you want to present as a single commit, for example, when changing a single variable, correcting spelling mistakes, and adjusting the spacing of the code. You should squash only small commits to a single file; big changes to the code across multiple files should contain the full commit history.

With you can see many commits in sequence, with the newest commit on top. In this example, starting from "feature A" many commits are made to implement "feature B"; we would like to squash all commits belonging to "feature B" into one.

Use the operation with the  or  option to select various commits and squash them. Use the hash of the commit just before the first one that you want to squash, in this case the one corresponding to "feature A".

(TIP: If you know how many commits you want to edit, you can use to work on the last  commits)

The command line editor, like or, will open to show you the commits again, now with the older commit on top. Before each commit, the word will be shown. Delete the word, and write the word or just the letter  instead, with the exception of the first entry; this commit is the oldest one, so all future commits will be squashed into it.

Save the file and close the editor.

The editor will open up again. Now you can add a longer message that describes all changes as if they were a single commit. Save the file and close the editor once more. This will finish combining those commits into one, with the new commit message that you wrote.

You can use again to observe the new commit history. In this case only a single commit for "feature B" will appear, on top of the unmodified commit for "feature A".

When coding for FreeCAD, we ask that you begin each commit message with the module that it affects. For example, a commit message for a change to sketcher might be: Sketcher: make straight lines curve a bit

Straight lines are sort of ugly, so this commit adds a little bit of curvature to them, so they are more visually pleasing. They also sparkle some, and change colors over time.

Fixes bug #1234.

Your PR will be easier to review, and faster to be merged, if you are careful to use rebase to structure and describe your commits before submitting.

Pushing your work to your GitHub repository
The local branches in your computer aren't automatically synchronized with the remote servers that you have specified as or  (see Remote repositories); you have to explicitly push the branches to the remote servers, for which you must have write access. Once you do this, the branches become public, and available for review by other developers.

For FreeCAD, you should push your local branch to the remote repository, that is,. You need to enter your username and password every time you push, unless you have set up Credential caching. Please read Pushing commits to a remote repository for more information.

When you work with a single branch, you may need to interactively rebase, squash, and fix commits many times. In this case, your branch history will not be simple, and you will not be able to push it to the remote repository. You may get a message like the following, saying that it is not possible to do a "fast-forward" push.

In order to finally push your branch to the remote repository you need to "force push" it. This will completely overwrite your remote branch with the actual branch that you have offline.

The regular developer doesn't have write access to the repository https://github.com/FreeCAD/FreeCAD, therefore, you should never push code to this remote server.

Rebasing from upstream
While you work on your own branch, the official FreeCAD code keeps "moving forward" with commits from other developers, and thus starts diverging from the code that you have in your personal fork.

.-A origin/myNewBranch / -o---Z FreeCAD upstream/master

Therefore, when you are ready to merge your branch to the main FreeCAD repository, you must "rebase" your own copy of the repository, so that it is as close as possible to the official repository. See Git Branching - Rebasing for more information.

This will download the code from the branch of the  repository (the official FreeCAD source), and will merge it with your current branch, so that your changes will appear on top of the latest official code. If nobody modified the same files that you did, then the merge will succeed without problems. If some files were changed at the same time by different people, there may be a conflict that needs to be resolved.

.-A' origin/myNewBranch / -o---Z FreeCAD upstream/master

To summarize, you need to be in the appropriate branch, rebase the upstream code, and then proceed with the push.

The operation is equivalent to a  followed by a. When the option is used, instead of doing a simple, it runs the  operation.

Merging the branch (pull request)
Once you have committed your changes locally, rebased your branch from the upstream repository, and pushed your branch online, you can initiate a "pull request". A pull request tells the administrators of the official FreeCAD repository that you want to merge the new code in your branch with the official code.

To recap, the development process looks like this:
 * 1) Fork FreeCAD and get a local copy of that fork.
 * 2) Create a branch on your fork and change to that branch.
 * 3) Code! Commit and much or as little as you like, writing good commit messages to keep track of what you are doing.
 * 4) When you are satisfied with your work, use  (where n is the total number of commits you've made) to collapse your commits into a logical set with good commit messages (each message should begin with the name of the module it affects, e.g. "Sketcher: make straight lines curve a bit").
 * 5) Use GitHub to submit your code as a "Pull Request (PR)" as described below.

As soon as you push the code to your repository, GitHub will give you the option of comparing and creating a pull request against the  repository. By pressing you will open an interface that will allow you to pick which repository is the "base", target of the merge, and which is the "head", your additional code. A quick check will be done by the system telling you if there are no conflicts with the files that you modified; if you worked on files that nobody has touched, your branch will be able to merge cleanly.

GitHub will show you a text editor so you can write a message documenting your changes: this editor will be pre-filled with a welcome message (that you can delete), a checklist (that you should go through), and a reminder to document your change on the wiki when it's accepted. To use the checklist, go through each item in turn and change the to  to indicate that you've done that step. GitHub will also display the number of commits in your branch, the number of files that were modified, and a view showing you the differences between the "base" and the "head" so that everybody can immediately see your intended modifications. Double-check these for things like stray blank lines you didn't mean to add, or huge formatting changes that your IDE decided to make behind your back.

Click to proceed. A message will appear indicating that some checks need to be done on the code. This is a system that compiles FreeCAD automatically and runs the unit tests. If the tests pass, the pull request will have a better chance of being merged into the main code, otherwise a report will be made indicating the errors encountered. See FreeCAD pull requests.

Some checks haven’t completed yet


 * continuous-integration/travis-ci/pr Pending — The Travis CI build is in progress |Required|

If the tests succeed, you will see a message such as the following

All checks have passed


 * continuous-integration/travis-ci/pr — The Travis CI build passed |Required|

This branch has no conflicts with the base branch Only those with write access to this repository can merge pull requests.

Now you must wait for the administrators to merge your branch; you will be notified when this happens.

If you wish, you may delete the branch that was just merged, or even your entire FreeCAD fork, as your own code is already included at the end of the master branch.

you may continue working on the same branch while you wait for merge approval; if you  again, a second merge commit will be queued in the same pull request, and another automated test will be done. That is, while your merges aren't yet approved by the administrators, you may keep pushing changes to your repository, and this will queue those commits in the same pull request to the  repository. Using a single pull request to queue many individual commits is often desirable for small changes. For big additions to the source code, you should create another branch, develop your features there, and then submit a separate pull request for this branch.

The pull request interface can be used whenever you want to submit code from your own repositories to another repository in GitHub. You can use it to merge code in the opposite direction as well, from other people's branches to your own, or even between your own branches. In the last case, since you own the branches, the merges can be approved by yourself immediately.

Das GitHub Repositorium auf dem neuesten Stand halten
Once you've forked FreeCAD, your personal repository exists independently from the original. When the original repository has new commits, GitHub will inform you that your personal repository is behind in number of commits:

In similar way, if you created a development branch with new code, GitHub will inform you that this branch is ahead in number of commits; that is, this branch has changes that haven't been merged into the official FreeCAD repository:

While developing, both cases are possible, as your own branch may lack commits made by other developers, but include new commits by you:

When developing code it is recommended that you rebase the branch in which you are currently working, as that will put your branch always ahead of the FreeCAD master code.

As for your original branch, it will never be automatically updated by GitHub; this is something that you must do yourself. Switch to the branch, then  from  (which performs a  and ), and then push this updated  branch to your remote  repository.

After this is done, GitHub will let you know that your are synchronized with the repository.

Now that your is up to date, you may decide to switch to it, and delete the other branch that you used previously to develop a feature.

To delete the branch in the remote repository, you can use the  operation. Normally, you push a local branch; this creates a remote branch with the same name as your local branch.

However, if you use the notation, the local branch is created in the remote repository under a different name:

Daher kannst du den entfernte Fernzweig löschen, indem du einen leeren lokale Zweig schiebst:

Now that you only have an up-to-date, you can create a new branch, and repeat the steps of changing files, committing, pushing, submitting a pull request, merging, and updating.

If you don't want to delete your already custom branch, you may force updating it to be equal to the updated ; then you can do whatever you want with it, including adding more commits and pushing it to the remote repository.

Hard resetting a branch like this is usually not needed. In most cases, you want to follow the sequence of creating a new branch, committing changes, pushing those changes, merging the branch, and then deleting the branch.

Suchen
Some handy tools to help you find what you're looking for:

Dateinamen suchen
Use to search the repository for file that contains a certain string in a filename. The example below will return all instances of the files that contain the 'dxf' in their filenames.

Suche nach einer Zeichenkette
Use to search the repository for file that contains a certain string with the files themselves. The example below will return all instances of the files that contain the 'dxf' within each and every file.

Auflösen von Zusammenführungskonflikten
Merging branches with, or rebasing your branch with , will occasionally present conflicts, as files may have been modified by another author at the same time. If this happens you should see the changes of both sides, the other author's, and your own, and then make a decision on how to include both sets of changes in the best way possible. This is normally a manual process that cannot be automated; the programmer must understand the code, and decide what code to move, re-write, or drop to solve the conflict.

Sobald ein Konflikt auftritt, kann eine Meldung wie diese erscheinen.

If a specialized diff tool is installed and configured for Git, for example, Gnome's Meld, the conflict can be examined and solved by using the operation.

The Meld tool normally displays three columns; the two columns on the sides display the two conflicting files, while the column on the middle displays the new code that will be saved and committed finally. Therefore, this central column should be edited in a way that it integrates the code of both side columns. Once the conflict is solved and the new source code (the central column) is saved, the Meld tool can be closed. Then the or  operation can continue.

For more information on merging and solving conflicts see:
 * How merge conflicts are presented with.
 * Basic merge conflicts and Git Tools - Advanced Merging.
 * Resolving a merge conflict using the command line.
 * External merge and diff tools to use when you encounter a Git conflict.

Änderungen untersuchen
Inspect the history of a single file through various commits with the operation:

Where can be any directory or file. Instead of, also the shorthands or  can be used.

Änderungen zwischen zwei Zweigen untersuchen
Inspect the changes between two branches with the and  operations with the names of the branches:

The operation shows the commits, while  shows the actual changes in the files.

Dateien und Verzeichnisse zurücksetzen
If you accidentally made modifications to a file or directory, you may want to completely revert these changes, to get the previous state of the source code.

This can be done quickly using the operation:

This will restore the (a file or a directory) to the state it is at the tip of the branch, discarding changes that haven't been committed. If is the single dot, it will restore all files in the current directory.

If you have accidentally added files and directories you can use the operation:

This will forcefully delete all files and directories that are not being tracked by the repository, that is, those that have not been included previously with the  operation.

To completely reset the repository, losing all uncommitted modifications, use the operation:

Where is the the tip of the  repository. Another commit can also be used.

The operation also reverts changes. However, this command does this by adding another commit to the history; in many cases this is not desired.

Beschneiden alter Zweige
If you have committed many branches to the repository, you may wish to remove these branches from your local system as they have already been merged. The branch in the repository online can be deleted immediately after merging. Then you can remove the local references to that branch, using the or  options to the  and  operations.

Schließlich kannst du die Zweige lokal löschen

It is also a good practice to do garbage collection after a while, by using the operation. This will cleanup unnecessary files, and compress local file revisions, in order to optimize local disk usage of the repository.

Arbeiten mit Patches
Obwohl Git Ihnen dir erlaubt, verschiedene Code Zweige mit zusammenzuführen (in deinem Computer) oder einer Pull Anfrage (Fernrepositorium) gibt es Zeiten, in denen es wünschenswert sein kann, einen traditionellen "Patch" zu erstellen, der als Anhang per Email verschickt werden kann. Der folgende Arbeitsablauf erklärt, wie dies zu tun ist.

Patches erstellen

 * You should be developing your new code in a secondary branch of your repository, and not in the master branch. So the first step is to make sure you are in the correct branch.


 * Now use against the master branch, and use the  option to redirect the result to standard output; then redirect the standard output to a file, which for convenience is created above the source code directory.


 * Eine andere Methode ist

The number of circumflex carets or the number  indicate the number of commits that should be considered, that is,  or  will create three patches for three commits.

This will create a patch or series of patches with the following naming convention

where is a number from  to, and the commit message forms the majority of the file name, for example,

Patches anwenden
Git can merge patches or diffs. To know more about this process read Applying patches with Git.

Wenn du die Patch Datei bereits in deinem System hast, wende sie einfach an.

You can use to download a patch from a website, and then apply it through.

Add or  at the end of the URL of a GitHub commit, pull request, or compare view so that the website shows you the plain text view of that page.
 * Regular commit page: https://github.com/FreeCAD/FreeCAD/commit/c476589652a0f67b544735740e20ff702e8d0621
 * Diff page: https://github.com/FreeCAD/FreeCAD/commit/c476589652a0f67b544735740e20ff702e8d0621.diff
 * Patch page: https://github.com/FreeCAD/FreeCAD/commit/c476589652a0f67b544735740e20ff702e8d0621.patch

You can point to a particular commit patch in the repository, and pipe it directly to  to apply the patch.

curl https://github.com/FreeCAD/FreeCAD/commit/c476589652a0f67b544735740e20ff702e8d0621.patch | git apply -

Einen Patch rückgängig machen
When you apply a patch you modify some files. However, these modifications aren't permanent until you commit the changes. Therefore, if you want to revert a patch use the following instructions.

This will revert the changes applied, if you still have access to the original patch file.

Alternatively, this will remove non-committed changes to the branch.

Stashing git commits
Say that you're working on a branch and you find yourself making some modifications to the source that are out of the scope of your current branch; in other words, those changes would be better in another branch instead of the current one. The command can be used to temporarily store those uncommitted local changes.

If in the future you want to use those commits, you can "pop" the commits out of the stash, and into your working branch.

Or if you decide that you don't like those saved commits anymore, you may drop the commits from the stash entirely.

You can list multiple stash commits with

To learn more, read Useful tricks you might not know about Git stash.

GitHub Anfragen lokal herausfinden
Checkout GitHub pull requests locally

Blaming
Add content from https://forum.freecadweb.org/viewtopic.php?f=23&t=55943&p=481483#p481287

Bisect
is a method to find the specific commit that introduced a bug.

You need to find 2 commits:
 * a good commit (for example ) before the system broke
 * a bad commit (for example ) after the system broke.

Then enter this from the terminal:

Result: will check out the mid point between the two commits.

Next step is to Build and test the code. If the system works, continue the process by typing:

Repeat previous step of building the code and testing it.

If the system is broken, type

Repeat previous steps applying good or bad depending on the outcome of your tests.

Eventually, git will tell you that is the first bad commit.

Note: takes a long time if good and bad are far apart.

FreeCAD Revisionsnummer
In contrast to subversion, which uses a consecutive number for its revisions, Git produces SHA-1 hash values with every commit. A hash value is a long alphanumeric string that looks like this

Letzte Revisionsnummer
To find the latest revision number of a particular branch use the operation with the  option. Give the name of the branch, remote repository, tag, or a special pointer like, to indicate the last commit in that particular object.

Or browse the repository on GitHub, and read the amount of commits reported in the particular branch.

Revisionsnummer eines bestimmten Commit Hashes
Since the hash is an alphanumeric string it is not very useful to decide if a certain commit is older or newer than another hash. To find the revision number of a particular hash, again use the operation; the input can be the full hash, or a partial hash that is unique, usually the first 7 digits are enough.

Revisions Hash einer bestimmten Commit Nummer
If we have the commit number, say, 15000, and we want to find the corresponding hash, we need to calculate the number of commits since this point until the last commit. First, get the latest commit number.

Then subtract the commit that we want.

Then use the operation to show all commits and hashes. The option jumps the difference in commits that we calculated so that we go directly to the hash that we are looking for.

Since the log may show you two close commits, confirm it's the right commit number. If it's off by one, just pick the next commit in the sequence (before or after) and check again.


 * Show the commits immediately before a particular commit in GitHub: in the address bar of the browser, change the word to  to show a list.
 * Finding the revision number of the commit
 * Finding the revision number of the commit
 * Finding the corresponding hash value to a particular commit number

Revisionsnummer in der FreeCAD Oberfläche
Die Versionsnummer, die mit dem Std Über Werkzeug angezeigt wird, ist in definiert, was zur Kompilierzeit erstellt wird, wenn das Werkzeug  ausgeführt wird. Lies Versionsnummer aus der Git Quelle extrahieren für weitere Informationen.

Hinzufügen weiterer (Fern) Repositorien
Mehrere Mitarbeiter des FreeCAD Projekts haben ihre eigenen Git Repositorien, in denen sie ihre Arbeit aufbauen oder neue Ideen ausprobieren, bevor sie bereit sind, in den offiziellen Quellcode aufgenommen zu werden. Vielleicht möchtest du ihre Quellen bekommen, um ihren Code selbst zu testen, wenn sie eine Pull Anfrage stellen.

Verwende den Befehl  Befehl, um diese anderen Repositorien hinzuzufügen, so dass du deren Code  und  kannst.

Lass uns zum Beispiel Bernds Fernrepositorium hinzufügen:

Der Befehl lädt die Referenzen von diesem Fernrepositorium herunter.

Liste alle Zweige in deinem eigenen Repositorium und die von deinen hinzugefügten Fernen auf. Bernds Zweige werden als angezeigt.

Lass uns nun eine zusammenfassende Liste der letzten 10 Commits von bernds Zweig ansehen.

Jetzt können wir den gewünschte Zweig zur Inspektion herausfinden.

Dann können wir einen lokalen Zweig erstellen, der auf dem entfernten Zweig basiert. Diesen lokalen Zweig können wir modifizieren und unseren eigenen Code hinzufügen.

Du kannst den des neu erhaltenen Zweigs auf den  Zweig umstellen, um sicherzustellen, dass er den neuesten Code verwendet. Wenn es Konflikte gibt, müssen diese an diesem Punkt gelöst werden.

Der neue Zweig ist bereit, modifiziert und kompiliert zu werden, wie in Kompilieren beschrieben.

Besuche die Entwicklungsabteilung des FreeCAD Forums, um mehr über die Entwicklung zu erfahren.

Weiterführende Literatur

 * FreeCAD mit GitKraken entwickeln, eine Anleitung zur Verwendung einer grafischen Oberfläche mit Git.
 * Git für die Faulpelze, eine sehr prägnante Anleitung zu den wichtigsten Befehlen von.
 * Das Pro Git Buch, ein quelloffenes Buch, das dich über Git lehrt; es ist in elektronischer und gedruckter Version erhältlich.
 * Der Visual Git Leitfaden, eine Referenz mit Diagrammen, die die häufigsten Operationen mit Git erklären.
 * Git Tutorium für Anfänger: Kommandozeilen Grundlagen, Video von Corey Schafer.
 * Einführung in Git - Kernkonzepte, Video von David Mahler.