# -*- coding: utf-8 -*-
from setuptools import setup

packages = \
['PyGitUp', 'PyGitUp.tests']

package_data = \
{'': ['*']}

install_requires = \
['GitPython>=3.0.0,<4.0.0',
 'click>=7.0,<8.0',
 'colorama>=0.4.0,<0.5.0',
 'six>=1.10.0,<2.0.0',
 'termcolor>=1.1.0,<2.0.0']

entry_points = \
{'console_scripts': ['git-up = PyGitUp.gitup:run']}

setup_kwargs = {
    'name': 'git-up',
    'version': '2.0.1',
    'description': "A python implementation of 'git up'",
    'long_description': 'PyGitUp |Version| |Build Status| |Coverage Status|\n==================================================\n\n|PyGitUp|_ is a Python port of\n`aanand/git-up <https://github.com/aanand/git-up/>`__. It not only\nfully covers the abilities of git-up and should be a drop-in replacement,\nbut also extends it slightly.\n\n.. |PyGitUp| replace:: ``PyGitUp``\n.. _PyGitUp: https://github.com/msiemens/PyGitUp\n\nWhy use ``git up``?\n-------------------\n\n    git pull has two problems:\n\n    * It merges upstream changes by default, when it\'s really more polite to `rebase\n      over them <http://gitready.com/advanced/2009/02/11/pull-with-rebase.html>`__,\n      unless your collaborators enjoy a commit graph that looks like bedhead.\n\n    * It only updates the branch you\'re currently on, which means git push will\n      shout at you for being behind on branches you don\'t particularly care about\n      right now.\n\n    (https://github.com/aanand/git-up/)\n\nDemonstration\n-------------\n\n.. image:: http://i.imgur.com/EC3pvYu.gif\n\nWhy use the Python port?\n------------------------\n\nI wasn\'t able to use the original ``git-up``, because I didn\'t want to install\na whole Ruby suite just for `git-up` and even with Ruby installed, there were\nsome problems running on my Windows machine. So, my reasons for writing\nand using this port are:\n\n1. Windows support.\n2. Written in Python ;)\n\nHow do I install it?\n--------------------\n\n1. Install ``git-up`` via `pip <https://pip.pypa.io/en/latest/installing.html>`__: ``$ pip install git-up``\n2. ``cd`` to your project\'s directory.\n3. Run ``git up`` and enjoy!\n\nNote for Windows users:\n~~~~~~~~~~~~~~~~~~~~~~~\n\nSee `these instructions <http://stackoverflow.com/q/4750806/997063>`__\nfor installing pip, if you haven\'t already installed it. And don\'t forget\nto either:\n\n- make your ``Python/Scripts`` and ``Python/Lib/site-packages`` writable for\n  you,\n- run ``pip`` with admin privileges\n- or use ``pip install --user git-up`` and add ``%APPDATA%/Python/Scripts``\n  to ``%PATH%``.\n\nOtherwise pip will refuse to install ``git-up`` due to ``Access denied`` errors.\n\nPython version compatibility:\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\nPython 3.5, 3.6, 3.7 and 3.8 are supported :)\n\nOptions and Configuration\n-------------------------\n\nCommand Line Arguments\n~~~~~~~~~~~~~~~~~~~~~~\n\n- ``git up -h`` shows a help message.\n\n- ``git up --quiet`` suppresses all output except for error messages.\n\n- ``git up --no-fetch`` skips fetching the remote and rebases all local branches.\n\n- ``git up --version`` shows the current version and optionally checks for\n  updates (see below).\n\nConfiguration\n~~~~~~~~~~~~~\n\nTo configure ``PyGitUp``, you can set options in your git config. Run\n``git config [--global] git-up.[name] [value]`` to set one of these\noptions:\n\n-  ``git-up.fetch.prune [*true*|false]``: If set to ``true``,\n   ``PyGitUp`` will append the ``--prune``\\ option to ``git fetch`` and\n   thus remove any remote tracking branches which no longer exist on\n   the remote (see `git fetch\n   --help <http://linux.die.net/man/1/git-fetch>`__).\n\n-  ``git-up.fetch.all [true|*false*]``: If set to ``false``, ``PyGitUp``\n   will only fetch remotes for which there is at least one local\n   tracking branch. Setting this option will make ``git up`` always fetch\n   from all remotes, which is useful if e.g. you use a remote to push to\n   your CI system but never check those branches out.\n\n- ``git-up.push.auto [true|*false*]``: Push the current branch after\n  rebasing and fast-forwarding.\n\n- ``git-up.push.all [true|*false*]``: Push all branches when auto-pushing.\n\n- ``git-up.push.tags [true|*false*]``: Push tags when auto-pushing.\n\n-  ``git-up.rebase.arguments [string]``: If set, ``PyGitUp`` will use\n   this string as additional arguments when calling ``git rebase``.\n   Example: ``--preserve-merges`` to recreate merge commits in the\n   rebased branch.\n\n-  ``git-up.rebase.auto [*true*|false]``: If set to ``false``,\n   ``PyGitUp`` won\'t rebase your branches for you but notify you that\n   they diverged. This can be useful if you have a lot of in-progress\n   work that you don\'t want to deal with at once, but still want to\n   update other branches.\n\n-  ``git-up.rebase.log-hook [cmd]``: Runs ``cmd`` every time a branch\n   is rebased or fast-forwarded, with the old head as ``$1`` and the new\n   head as ``$2``. This can be used to view logs or diffs of incoming\n   changes. Example:\n   ``echo "changes on $1:"; git log --oneline --decorate $1..$2``.\n\n- ``git-up.rebase.show-hashes [true|*false*]``: If set to ``true``,\n  ``PyGitUp`` will show the hashes of the current commit (or the point\n  where the rebase starts) and the target commit like ``git pull`` does.\n\nNew in v1.0.0:\n~~~~~~~~~~~~~~\n\n- ``git-up.updates.check [*true*|false]``: When running ``git up --version``,\n  it shows the version number and checks for updates. If you feel\n  uncomfortable with it, just set it to ``false`` to turn off the checks.\n\nCredits\n-------\n\nThe original ``git-up`` has been written by aanand:\n`aanand/git-up/ <https://github.com/aanand/git-up/>`__.\n\n\nChangelog\n---------\n\nv2.0.1 (*2020-08-26*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Update dependencies\n\nv2.0.0 (*2020-08-15*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Drop Python 2 support in order to fix `Issue 102 <https://github.com/msiemens/PyGitUp/issues/102>`_\n- Drop Ruby Bundler integration\n- Migrate tests to ``py.test``\n\nv1.6.1 (*2018-12-12*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Upgrade to click>=7.0.0. Thanks `@no-preserve-root <https://github.com/no-preserve-root>`_\n  for `Pull Request #87 <https://github.com/msiemens/PyGitUp/pull/87>`_.\n\nv1.6.0 (*2018-10-26*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Skip stashing changes when possible. Thanks `@Chronial <https://github.com/Chronial>`_\n  for `Pull Request #86 <https://github.com/msiemens/PyGitUp/pull/86>`_.\n- Added faster fast-forward on branches that are not checked out. Thanks `@Chronial <https://github.com/Chronial>`_\n  for `Pull Request #83 <https://github.com/msiemens/PyGitUp/pull/83>`_.\n\nv1.5.2 (*2018-09-28*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Fixed version requirement for Click dependency (`#82 <https://github.com/msiemens/PyGitUp/issues/82>`__).\n\nv1.5.1 (*2018-09-13*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Fixed crash on Cygwin with rebase log hook enabled (`#80 <https://github.com/msiemens/PyGitUp/issues/80>`__).\n\nv1.5.0 (*2018-04-26*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Added auto-push support. Thanks `@WoLpH <https://github.com/WoLpH>`_\n  for `Pull Request #74 <https://github.com/msiemens/PyGitUp/pull/74>`_.\n\nv1.4.7 (*2018-04-07*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Added shorthand commandline arguments (``-V, -q, -h``, see `#73 <https://github.com/msiemens/PyGitUp/issues/73>`__).\n\nv1.4.6 (*2017-12-19*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- 3rd party dependencies have been updated (see `#65 <https://github.com/msiemens/PyGitUp/issues/65>`__).\n\nv1.4.5 (*2017-01-02*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Fixed problems when working with branches containing hash signs in their name\n  (`#55 <https://github.com/msiemens/PyGitUp/issues/55>`__).\n- No longer installs a now unneeded script on ``pip install``. Thanks `@ekohl <https://github.com/ekohl>`_\n  for `Pull Request #60 <https://github.com/msiemens/PyGitUp/pull/60>`_.\n\nv1.4.4 (*2016-11-30*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Fixed a bug when working with ``git worktree`` (`#58 <https://github.com/msiemens/PyGitUp/issues/58>`__).\n\nv1.4.3 (*2016-11-22*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Fixed a bug with GitPython <= 2.0.8 (`#56 <https://github.com/msiemens/PyGitUp/issues/56>`__, `#57 <https://github.com/msiemens/PyGitUp/issues/57>`__).\n\nv1.4.2 (*2016-09-29*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Switched the command line argument parsing library (`#53 <https://github.com/msiemens/PyGitUp/issues/53>`__).\n\nv1.4.1 (*2016-08-02*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Include tests in PyPI distribution (`#51 <https://github.com/msiemens/PyGitUp/issues/51>`__).\n\nv1.4.0 (*2016-02-29*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- 3rd party dependencies have been updated.\n- Dependencies on 3rd party libraries have been loosened to better interact with other installed packages.\n  Thanks `MaximilianR <https://github.com/MaximilianR>`_ for `Pull Request #45 <https://github.com/msiemens/PyGitUp/pull/45>`_.\n- Added an command line argument to turn of fetching (``--no-fetch``). Thanks `@buoto <https://github.com/buoto>`_\n  for `Pull Request #46 <https://github.com/msiemens/PyGitUp/pull/46>`_.\n- Don\'t show a stacktrace anymore when stashing fails (`#35 <https://github.com/msiemens/PyGitUp/issues/35>`_).\n- Fixed a bug that cuased problems with submodules if the submodule had unstashed changes/ Thanks\n  `@Javex <https://github.com/Javex>`_ for `Pull Request #27 <https://github.com/msiemens/PyGitUp/pull/27>`_.\n\nv1.3.1 (*2015-08-31*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Fixed a bug when showing the version on Python 3 `#34 <https://github.com/msiemens/PyGitUp/issues/34>`__.\n\nv1.3.0 (*2015-04-08*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Support for Python 3 has been added. Thanks `@r4ts0n <https://github.com/r4ts0n>`_\n  for `Pull Request #23 <https://github.com/msiemens/PyGitUp/pull/23>`_\n  and `@Byron <https://github.com/Byron>`_ for quickly merging a Pull Request\n  in `GitPython <https://github.com/gitpython-developers/GitPython>`_\n  and releasing a new version on which this release depends.\n\nv1.2.2 (*2015-02-23*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Now updates submodules when called from ``git submodule foreach`` (`#8 <https://github.com/msiemens/PyGitUp/issues/8>`__).\n\nv1.2.1 (*2014-12-16*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Fixed a problem with ``setuptools 8.x`` (`#19 <https://github.com/msiemens/PyGitUp/issues/19>`__).\n- 3rd party dependencies have been updated\n\nv1.2.0 (*2014-12-10*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Added an option to show hashes when fast-forwarding/rebasing like ``git pull``\n  does (``git-up.rebase.show-hashes``).\n- Fixed a bug when having branches with both local tracking branches and\n  remote tracking branches (`#17 <https://github.com/msiemens/PyGitUp/issues/17>`__).\n\nv1.1.5 (*2014-11-19*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- 3rd party dependencies have been updated to fix a problem with a 3rd party\n  library (`#18 <https://github.com/msiemens/PyGitUp/issues/18>`__).\n\nv1.1.4 (*2014-04-18*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Fixed some typos in README and ``PyGitUp`` output.\n- 3rd party dependencies have been updated.\n\nv1.1.3 (*2014-03-23*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- ``ahead of upstream`` messages are now cyan (see `aanand/git-up#60 <https://github.com/aanand/git-up/issues/60>`__).\n- Fixed problem when using % in the log hook (`#11 <https://github.com/msiemens/PyGitUp/issues/11>`__).\n\nv1.1.2 (*2013-10-08*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Fixed problems with the dependency declaration.\n\nv1.1.1 (*2013-10-07*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Fix for `#7 <https://github.com/msiemens/PyGitUp/issues/7>`__\n  (AttributeError: \'GitUp\' object has no attribute \'git\') introduced by\n  v1.1.0.\n\nv1.1.0 (*2013-10-07*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Prior to v1.1.0, ``PyGitUp`` tried to guess the upstream branch for a local\n  branch by looking for a branch on any remote with the same name. With v1.1.0,\n  ``PyGitUp`` stops guessing and uses the upstream branch config instead.\n\n  This by the way fixes issue `#6 <https://github.com/msiemens/PyGitUp/issues/6>`__\n  (``git up`` doesn\'t work with local only branches).\n\n  **Note:**\n  This change may break setups, where a local branch accidently has\n  the same name as a remote branch without any tracking information set. Prior\n  to v1.1.0, ``git up`` would still fetch and rebase from the remote branch.\n  If you run into troubles with such a setup, setting tracking information\n  using ``git branch -u <remote>/<remote branch> <local branch>`` should help.\n\n- 3rd party dependencies have been updated.\n\n- Allows to run ``git up --version`` from non-git dirs, too.\n\nv1.0.0 (*2013-09-05*)\n~~~~~~~~~~~~~~~~~~~~~\n\nFinally ``PyGitUp`` reaches 1.0.0. You can consider it stable now :)\n\n- Added a comprehensive test suite, now with a coverage of about 90%.\n- Lots of code cleanup.\n- Added option ``-h`` to display a help screen (``--help`` **won\'t** work, because\n  ``git`` catches this option and handles it before ``PyGitUp`` can do).\n- Added option ``--version`` to show, what version of ``PyGitUp`` is running.\n  Also checks for updates (can be disabled, see configuration).\n- Added option ``--quiet`` to be quiet and only display error messages.\n\nv0.2.3 (*2013-06-05*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Fixed issue `#4 <https://github.com/msiemens/PyGitUp/issues/4>`__ (ugly\n  exception if remote branch has been deleted).\n\nv0.2.2 (*2013-05-04*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Fixed issue `#3 <https://github.com/msiemens/PyGitUp/issues/3>`__ (didn\'t\n  return to previous branch).\n\n\nv0.2.1 (*2013-03-18*)\n~~~~~~~~~~~~~~~~~~~~~\n\n- Fixed problem: check-bundler.rb has not been installed when installing via\n  PyPI (problems with setup.py).\n\nv0.2 (*2013-03-18*)\n~~~~~~~~~~~~~~~~~~~\n\n- Incorporated `aanand/git-up#41 <https://github\n  .com/aanand/git-up/pull/41>`__: Support for ``bundle install --local`` and\n  ``rbenv rehash``.\n- Fixed issue `#1 <https://github.com/msiemens/PyGitUp/issues/1>`__ (strange\n  output buffering when having multiple remotes to fetch from).\n- Some under-the-hood improvements.\n\nv0.1 (*2013-03-14*)\n~~~~~~~~~~~~~~~~~~~\n\n- Initial Release\n\n.. |Build Status| image:: https://img.shields.io/azure-devops/build/msiemens/3e5baa75-12ec-43ac-9728-89823ee8c7e2/1.svg?style=flat-square\n   :target: https://dev.azure.com/msiemens/github/_build?definitionId=1\n\n.. |Coverage Status| image:: http://img.shields.io/coveralls/msiemens/PyGitUp/master.svg?style=flat-square\n  :target: https://coveralls.io/r/msiemens/PyGitUp\n\n.. |Version| image:: http://img.shields.io/pypi/v/git-up.svg?style=flat-square\n  :target: https://pypi.python.org/pypi/git-up\n',
    'author': 'Markus Siemens',
    'author_email': 'markus@m-siemens.de',
    'maintainer': None,
    'maintainer_email': None,
    'url': 'https://github.com/msiemens/PyGitUp',
    'packages': packages,
    'package_data': package_data,
    'install_requires': install_requires,
    'entry_points': entry_points,
    'python_requires': '>=3.5,<4.0',
}


setup(**setup_kwargs)
