Your IP : 216.73.216.170


Current Path : /var/www/iplanru/data/www/i-plan.ru/libraries/joomla/github/package/
Upload File :
Current File : /var/www/iplanru/data/www/i-plan.ru/libraries/joomla/github/package/data.php

<?php
/**
 * @package     Joomla.Platform
 * @subpackage  GitHub
 *
 * @copyright   Copyright (C) 2005 - 2012 Open Source Matters, Inc. All rights reserved.
 * @license     GNU General Public License version 2 or later; see LICENSE
 */

defined('JPATH_PLATFORM') or die;

/**
 * GitHub API DB class for the Joomla Platform.
 *
 * @documentation http://developer.github.com/v3/git/
 *
 * @package     Joomla.Platform
 * @subpackage  GitHub.Data
 * @since       12.3

 * http://developer.github.com/v3/git/
Git DB API

The Git Database API gives you access to read and write raw Git objects to your Git database on GitHub and to list
 * and update your references (branch heads and tags).

This basically allows you to reimplement a lot of Git functionality over our API - by creating raw objects
 * directly into the database and updating branch references you could technically do just about anything that
 * Git can do without having Git installed.

Git DB API functions will return a 409 if the git repo for a Repository is empty or unavailable.
 * This typically means it is being created still. Contact Support if this response status persists.

git db

For more information on the Git object database, please read the Git Internals chapter of the Pro Git book.

As an example, if you wanted to commit a change to a file in your repository, you would:

    get the current commit object
    retrieve the tree it points to
    retrieve the content of the blob object that tree has for that particular file path
    change the content somehow and post a new blob object with that new content, getting a blob SHA back
    post a new tree object with that file path pointer replaced with your new blob SHA getting a tree SHA back
    create a new commit object with the current commit SHA as the parent and the new tree SHA, getting a commit SHA back
    update the reference of your branch to point to the new commit SHA

It might seem complex, but it’s actually pretty simple when you understand the model and it opens up a ton of
 * things you could potentially do with the API.

 */
class JGithubPackageData extends JGithubPackage
{
	protected $name = 'Data';

	protected $packages = array(
		'blobs', 'commits', 'refs', 'tags', 'trees'
	);
}