Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Mac OS X Objective-C Framework for git repositories.

branch: master

This branch is 0 commits ahead and 0 commits behind master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 Documentation
Octocat-spinner-32 Git.xcodeproj
Octocat-spinner-32 Resource
Octocat-spinner-32 Source
Octocat-spinner-32 Test
Octocat-spinner-32 Vendor
Octocat-spinner-32 Website @ 5448095
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .gitmodules
Octocat-spinner-32 README.md
Octocat-spinner-32 Rakefile
README.md

Git.framework - Mac OS X GIT Repository Framework

An implementation of Git in Objective-C & Foundation framework for embedding in Mac OS X and potentially iPhone OS Applications.

Supported Features

The currently supported features of the project are

  • Reading objects, both loose and packed
  • Resolving refs from .git/refs
  • Reading branches, both local and remote

Planned Features

Features which will be implemented at some point (in no particular order)

  • Rev-list Support
  • Pulling changes from a remote repository via either ssh:// or git://
  • Pushing changes to a remote repository via ssh://
  • Mutable objects to enable writing new objects to the repository
  • Manipulation of the Index/Stage
  • ... and much much more*

Additionally features from CocoaGit which are not yet supported will be evaluated and migrated into this project.

*maybe, as and when things are thought of, suggested, or otherwise materialize, terms and conditions may apply, see binary for details

Running the Test Suite

The test suite requires MacRuby 0.5 and Bacon and can be run either through Xcode or rake in the Terminal. So far tests have been run using MacRuby r3090 and Bacon v0.9.

Be sure to install Bacon via: 'sudo macgem install bacon'

Code Formatting and Style

I've tried to keep the code formatting and style unified within the project and with the current body of code this should be reasonably easy to follow. To aid in keeping the tabs/spaces under control there is a pre-commit hook which can be installed via

$ rake check_tabs:install_hook

if you don't have a pre-commit hook already then this one will be installed, if you do then the script contents will be printed and you will need to merge them manually. This will cause a commit were there are tabs in the files being committed to fail. If you want to check the staged files or Source/ contents for tabs you can use either of the following

$ rake check_tabs:source
$ rake check_tabs:staged

and any offending lines will be printed.

BridgeSupport

The addition of any C level constants which need to be exposed to a bridged language such as MacRuby or PyObjC will require the regeneration of the BridgeSupport files. The headers containing the constants or functions to be exposed will need to be marked as public in the Git target and then the bridgesupport:generate rake task will need to be run.

Documentation of Code

All headers need to be documented using the style currently in use. Documentation is generated using the Doyxgen tool and is then post-processed by the Documentation/doxyclean project into the final format.

Licence

Released under the terms of the MIT licence, details of which are below

Copyright (c) 2009 Geoff Garside

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
Something went wrong with that request. Please try again.