# hubot-taiga

> Send taiga commands from hubot

Latest version **1.0.1** (published 2015-10-03) · GPL-3.0 license · 0 weekly downloads

## Install

```sh
npm install hubot-taiga
pnpm add hubot-taiga
yarn add hubot-taiga
bun add hubot-taiga
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 1.0.1 |
| Published | 2015-10-03 |
| First published | 2015-10-03 |
| Weekly downloads | 0 |
| License | GPL-3.0 |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 1 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| Author | david@burkesoftware.com |
| Maintainers | bufke |
| Keywords | hubot, hubot-scripts, taiga.io |

## Links

- npm: https://www.npmjs.com/package/hubot-taiga
- Repository: https://gitlab.com/burke-software/hubot-taiga
- Homepage: https://gitlab.com/burke-software/hubot-taiga#README
- Issues: https://gitlab.com/burke-software/hubot-taiga/issues
- npm.io page: https://npm.io/package/hubot-taiga

## Dependencies (1)

- [coffee-script](https://npm.io/package/coffee-script.md) ~1.10.0

## Recent versions

- 1.0.1 (latest) — 2015-10-03
- 1.0.0 — 2015-10-03

## README

Send commands to Taiga.io from hubot

# Features

- Should work with any chat solution. Tested in Let's Chat and Slack.
- Make changes to Taiga User Stories (more coming soon) with chat commands. 
- Same syntax as Taiga [git commit messages.](https://taiga.io/support/changing-elements-status-via-commit-message/)

![Screenshot](demo.png)

# Install

hubot-taiga is in active development and not finished yet. 
Expect bugs and breaking changes until version 1.0.

1. Make sure hubot is set up and redis is working (optional)
2. Copy `taiga.coffee` to `<your hubot>/scripts/`
3. Set username/password as environment variables. I use a special Hubot user made in Taiga.io. User should have admin privledges.
`HUBOT_TAIGA_USERNAME` and `HUBOT_TAIGA_PASSWORD` and optional `HUBOT_TAIGA_PROJECT`
Or just hard code them in the file (not great for upgrading script).
4. Restart hubot

# Usage

Commands

- `taiga info` - view hubot-taiga settings
- `taiga project <project slug>` - Set project per channel
- `taiga auth <username> <password>` - Log in to post comments as your Taiga.io user
- `TG-REF Your comment` Add a comment where REF is the User Story reference.
Example `TG-123 I think this is a great idea`
and `TG-123 #done I finished it, I am the best.`

# Developing

There are many ways to work on hubot scripts. Here is how I do it.

## Docker

This method uses docker-compose

1. Clone this repo
2. Run `docker-compose run --rm hubot bash`
3. Run inside the container `bin/hubot`

## Without Docker

1. Clone this repo
2. Install a new hubot just for testing.
3. `cd` to your new hubot install
4. Set environment variables (see INSTALLATION). I write a small script for this.
5. Run hubot like `bin/hubot`
6. Test out your command. You will need to restart hubot for each change.
7. Submit a merge request with better instructions (Auto-restart? Debugging?)

---
_Source: https://npm.io/package/hubot-taiga · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._