A git fixture using the fixtures API for writing tests for tools that use git.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Darragh Bailey bb831cb4c4 Move commit creation code to GitTree class 4 days ago
doc Merge "Initial fixture for git" 11 months ago
fixtures_git Move commit creation code to GitTree class 4 days ago
tests Split code for reuse and refactor for code style 4 days ago
.gitignore Initial fixture for git 11 months ago
.gitreview OpenDev Migration Patch 1 month ago
.stestr.conf Initial fixture for git 11 months ago
.zuul.yaml Fix jobs 6 days ago
DESCRIPTION Initial project files for fixtures-git 1 year ago
LICENSE Initial project files for fixtures-git 1 year ago
README.rst Remove those copy words occured twice times in README.rst 4 months ago
requirements.txt Initial fixture for git 11 months ago
setup.cfg Initial project files for fixtures-git 1 year ago
setup.py Initial project files for fixtures-git 1 year ago
test-requirements.txt Fix jobs 6 days ago
tox.ini Initial fixture for git 11 months ago

README.rst

What is fixtures-git?

Fixtures git is an open source Python library that adheres to the fixtures API defined by https://pypi.python.org/pypi/fixtures

It was initially developed as part of git-upstream tests to make it easy to construct git repositories with various layouts rather than trying to mock/stub git's behaviour.

It is intended to allow developers to define a git repo layout using a list definition of the commit nodes.

To install:

See also https://pypi.python.org/pypi/fixtures-git

You can also install directly from source:

Developers

Bug reports:

Repository:

Cloning:

or

A virtual environment is recommended for development. For example, git-upstream may be installed from the top level directory:

Patches are submitted via Gerrit at:

Please do not submit GitHub pull requests, they will be automatically closed.

More details on how you can contribute is available on the wiki at:

Writing a patch

All code submissions must be pep8 and pyflakes clean. CI will automatically reject them if they are not. The easiest way to do that is to run tox before submitting code for review in Gerrit. It will run pep8 and pyflakes in the same manner as the automated test suite that will run on proposed patchsets.

Support

Is via the git-upstream community which is found on the #git-upstream channel on chat.freenode.net

You can also join via this IRC URL or use the Freenode IRC webchat.