semvec/pypi-packages huggingface dataset:
githublabelscopy 1.1.1
A tool to copy labels between repositories using Github API
License: MIT

.. image:: https://landscape.io/github/fpietka/github-labels-copy/master/landscape.svg?style=flat
   :target: https://landscape.io/github/fpietka/github-labels-copy/master
   :alt: Code Health
.. image:: https://img.shields.io/pypi/v/githublabelscopy.svg
   :target: https://pypi.python.org/pypi/githublabelscopy
   :alt: Version
.. image:: https://img.shields.io/pypi/pyversions/githublabelscopy.svg
   :target: https://pypi.python.org/pypi/githublabelscopy
   :alt: Python versions supported
.. image:: https://img.shields.io/pypi/l/githublabelscopy.svg
   :target: https://pypi.python.org/pypi/githublabelscopy
   :alt: License

==================
Github Labels Copy
==================

A tool to copy labels between repositories using Github API

Here are the actions done by this tool:

- Add missing labels
- Modify color for existing labels
- Delete labels not availlable in source repository

It can be used with either login/password or API Key.

Installation
------------

You can install it using ``pip``::

 $ pip install githublabelscopy

Usage
-----

To copy labels between two repositories::

 $ github-labels-copy myuser/source-repo myuser/target-repo

There is also two identification modes:

* --login : using your Github username, you will be prompted for your password
* --token : provide your Github token

Alternatively you can set an environment variable called ``GITHUB_API_TOKEN``. Without any identification mode specified,
it will automatically fallback on it.

You can also dump/load labels:

* --load : load labels from a previous dump (yaml file)
* --dump : dump labels into a yaml file

Options
-------

There are 3 non exclusive modes:

* -c : creates labels which don't exist on target repository
* -r : remove labels on target repository  which don't exists on source repository
* -m : modify labels which don't have the right color code on target repository

Default is full mode, which execute all those actions.
bugrest 1.1.1
Awesome minimalist command line ticket/bug tracker based on ReStructuredText
License: MIT

BugRest
#######

Friendly and very light weight tool to keep track of list of things.
Designed with bugs/tickets/GTD in mind

See some generated `Bug file`__

__ https://raw.githubusercontent.com/fdev31/loof/master/bugs.rst

Screenshot
==========

.. image:: https://github.com/fdev31/bugrest/raw/master/shot.png


Key features
============

- **CLI** (works in a terminal)
- Simple text file used as storage (**ReStructuredText**)
    - **Git, Mercurial** & co friendly
    - **Colorized** in the terminal
    - No need to edit the text file by hand
- Automatically detects the "root" folder to use by finding  .hg, .svn or other version manager folder in parent directories
- More advanced features not getting in your way if you don't need them:
    - Priorities
    - Tags
    - Attributes
    - Time tracker (counts the time spent on a given task)
- Web Server allowing **real-time read only sharing** of the list
- HTML export
- Search tool (``grep``-like)

On the technical side
---------------------

- Pure **Python**, no dependency required (Ok... ``docutils``, but misses it ? ;)
- Simple *one file* design, keeping things short
- **No database**, only the ``.rst`` file is used for storage



Usage
=====

The command line tool is `br` and works in the current directory.
If you don't like this, feel free to edit `br` file and change the following lines to absolute paths::

    BUGFILE = 'bugs.rst'
    DONEFILE = 'fixed_bugs.rst'


List bugs::

    br

Add new bug::

    br new

Delete bug number 4::

    br rm 4

Add one comment::

    br add 3

Show full description of current bugs::

    br show

Show description of some specific bug::

    br show 42

Produce an html report::

    br html > bugs.html

Start a web server on port 5555::

    br serve

Change priority of item #66 (using ``bugid`` instead of item position)::

    br set #66 priority 10