Skip to main content

The stupid commit-bug traceability linker for the stupid content tracker

Project description

Usage

For input, gitbuglink accepts a file path to a local git repository. It uses the dulwich Python module to access the repository log. Output is a couple CSV files:

  1. links.csv – a CSV of (commit id, bug id) for confirmed links

  2. humans.csv – a CSV of (commit id, bug id_1, bug id_2, …, bug id_n) for links that require some form of human knowledge to establish the correct link(s). The tool makes no assumptions about a commit when it finds multiple links. You should investigate the commit message yourself to confirm or correct the output.

But my subject system uses CVS/Subversion/…

  1. I don’t care. Send a pull request when you get it working.

  2. Search for an (un)official project git mirror of the repository

  3. [Use a conversion tool](http://lmgtfy.com/?q=cvs+to+git):
    1. [cvs2git](http://cvs2svn.tigris.org/cvs2git.html)

    2. [svn2git](https://github.com/nirvdrum/svn2git)

    3. (Send pull request for links to other tools you can recommend)

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

gitbuglink-0.0.2.tar.gz (4.6 kB view hashes)

Uploaded source

Built Distribution

gitbuglink-0.0.2-py2.py3-none-any.whl (7.5 kB view hashes)

Uploaded 2 7

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page