

GitHub pull requests These are preferred by the developers due to rich GitHub code review functionality, but are more complicated to create than patches. There are 2 main ways to submit bug fixes, modifications or enhancements for review: Name your working branch after the bug or feature - e.g. Non-Committers should always work in their own working branch specific to the bug or feature being worked on, not the master or maint branch. The packaging repos gnucash-on-… have only a master branch. master New features, dependencies, and their documentation should be based on this branch. Bugfixes, translations, and improvements to the documentation should usually be applied on this branch. Maint(enance) is the default branch in git. There are 2 important branches in our repositories for the program and docs: These are updated from the primary repository by commit hooks, so barring technical problems changes appear in these repositories within a few seconds of being committed to the primary repository. Our public repositories are mirrored on Github: for code, documentation and for the website. We manage our code and documentation sources in Git. Windows or Mac only GitHub Desktop SourceTree, and While pure git has only a command line interace (CLI) there are several GUIs available for git, for example:
#Gnucash source code manual
Will show you the manual page of that command. Will give you a list of common commands and If you know nothing about version control, read Getting Started - About Version Control.Īnother good place to start is Good Resources for Learning Git and GitHub - especially if you want to use GitHub for #Pull Requests.

#Gnucash source code for free
In particular, Pro Git by Scott Chacon is available in several languages for free online reading at Git Book. You can get the latest version for your system and read a rich variety of online documentation at Git's Home. Git is a distributed version control system (VCS) originally developed by Linus Torvalds for managing Linux source code without requiring a central server. 5.7 Prepare for your next working branch.5.4 Push Back To Your Personal Repository.5.3 Sync your local master or maint from upstream (Pull Requests).5.1 Create a working-branch (Pull Requests).4.4 Sync your local master or maint from origin (Patches).2 What does that have to do with Gnucash?.
