Skip to content
Bugs Everywhere is a “distributed bugtracker” designed to complement distributed revision control systems
Python Shell
Find file
Latest commit b1f92d9 Jul 17, 2012 Niall Douglas (s [underscore] sourceforge {at} nedprod [dot] com) Added 'be gui' command to invoke BEurtle GUI for you.
Failed to load latest commit information.
.be Generated libbe/ was not UTF-8 aware. Jan 2, 2012
libbe Added 'be gui' command to invoke BEurtle GUI for you. Jul 17, 2012
update-copyright @ 5ab3ec3
.update-copyright.conf Transition to my external update-copyright package. Feb 16, 2012
AUTHORS Ran Feb 16, 2012
COPYING Merged with head branch Oct 1, 2009
NEWS Add --notify to `be serve`. Apr 16, 2011
be.bat Fixed missing pyyaml dependency on Windows. Now auto-downloads a copy… Aug 3, 2011


Bugs Everywhere

This is Bugs Everywhere (BE), a bugtracker built on distributed version
control.  It works with Arch, Bazaar, Darcs, Git, Mercurial, and Monotone
at the moment, but is easily extensible.  It can also function with no
VCS at all.

The idea is to package the bug information with the source code, so that
bugs can be marked "fixed" in the branches that fix them.  So, instead of
numbers, bugs have globally unique ids.

Getting BE

BE is available as a Git repository::

    $ git clone git:// be

See the homepage_ for details.  If you do branch the Git repo, you'll
need to run::

    $ make

to build some auto-generated files (e.g. ``libbe/``), and::

    $ make install

to install BE.  By default BE will install into your home directory,
but you can tweak the ``PREFIX`` variable in ``Makefile`` to install
to another location.

.. _homepage:

Getting started

To get started, you must set the bugtracker root.  Typically, you will want to
set the bug root to your project root, so that Bugs Everywhere works in any
part of your project tree.::

    $ be init -r $PROJECT_ROOT

To create bugs, use ``be new $DESCRIPTION``.  To comment on bugs, you
can can use ``be comment $BUG_ID``.  To close a bug, use
``be close $BUG_ID`` or ``be status $BUG_ID fixed``.  For more
commands, see ``be help``.  You can also look at the usage examples in


If ``be help`` isn't scratching your itch, the full documentation is
available in the doc directory as reStructuredText_ .  You can build
the full documentation with Sphinx_ , convert single files with
docutils_ , or browse through the doc directory by hand.
doc/index.txt is a good place to start.  If you do use Sphinx, you'll
need to install numpydoc_ for automatically generating API
documentation.  See the ``NumPy/SciPy documentation guide``_ for an
introduction to the syntax.

.. _reStructuredText:
.. _Sphinx:
.. _docutils:
.. _numpydoc:
.. _NumPy/SciPy documentation guide:
Something went wrong with that request. Please try again.