lancet 0.4.1

Lancet

LANCET

From http://en.wikipedia.org/wiki/Scalpel:

A scalpel, or lancet, is a small and extremely sharp bladed instrument used for surgery, anatomical dissection, and various arts and crafts (called a hobby knife).

Lancet is a command line utility to streamline the various activities related to the development and maintenance of a software package.

• Free software: MIT license

• Documentation: http://lancet.rtfd.org

Installation

Check out the documentation.

Getting started

Once installed, set up the initial configuration by running:

lancet setup

For each not-yet-configured project, you can then run:

cd path/to/project
lancet init

This creates a new project-level configuration file that can be shared across different users (and thus commited to source control).

TODO

A lot of commands are still missing, as for example:

• pr: to open a new pull-request and update the tracker accordingly.

• review: to streamline the whole reviewing process (pulling, linting,diffs,…).

• merge: to help in getting a more strict merge process in place (and cleanup afterwards). Can include rebasing helpers.

• Other issue tracker/Harvest interaction utilities (list, search, comment, …)

History

0.4.1 - 2015-01-05

• Update requirements.

0.4 - 2015-01-05

Warning

If your setup includes remote configured to be accessed over SSH, you may need to reinstall libgit2 with brew reinstall libgit2 --with-libssh2.

• Added facilities to integrate with the current shell, for stuff like cd’ing to other directories or activating virtual environments.

• Added a --version option to lancet.

• Fetch latest changes from origin before creating new working branches (#1).

• Added an activate command to cd to the project directory and (optionally) activate a virtual environment.

• Added the harvest-projects and harvest-tasks commands to list projects/tasks IDs from Harvest.

• Added an init command to create project-level configuration files (#2).

0.3 - 2014-12-30

• Handle unassigned issues (#5).

• Avoid logging out the web user when accessign the JIRA API (#4).

• Initial documentation stub (#3).