![]() This allows it to expose a very tight and consistent API, that completely follows Obj-C conventions and hides away the libgit2 complexity and sometimes inconsistencies. Instead of offering extensive raw bindings to libgit2, GitUpKit only uses a minimal subset of libgit2 and reimplements everything else on top of it (it has its own "rebase engine" for instance). ![]() GitUpKit has a very different goal than ObjectiveGit. This means that you can use that same GitUpKit framework to build your very own Git UI! GitUp is built as a thin layer on top of a reusable generic Git toolkit called "GitUpKit". Simply delete the "Code Signing Identity" build setting of the "Application" target to work around the issue:Īlternatively, if you do have a developer account, you can create the file "Xcode-Configurations/DEVELOPMENT_TEAM.xcconfig" with the following build setting as its content:įor a more detailed description of this, you can have a look at the comments at the end of the file "Xcode-Configurations/Base.xcconfig". IMPORTANT: If you do not have an Apple ID with a developer account for code signing Mac apps, the build will fail with a code signing error. To build GitUp yourself, simply run the command git clone -recursive in Terminal, then open the GitUp/GitUp.xcodeproj Xcode project and hit Run. ![]() ![]() You can change the update channel used by GitUp in the app preferences. b1234) are only released on the "Continuous" channel. v1.2.3) are released on the "Stable" channel, while builds tagged with a b (e.g. Read the docs and use GitHub Issues for support & feedback. Learn all about GitUp and download the latest release from. 30,000 lines of code later, GitUp reached 1.0 mid-August 2015 and was released open source as a gift to the developer community. After several months of work, it was made available in pre-release early 2015 and reached the top of Hacker News along with being featured by Product Hunt and Daring Fireball. GitUp was created by in late 2014 as a bet to reinvent the way developers interact with Git.
0 Comments
Leave a Reply. |