open-index/open-npm huggingface dataset:
npm package: @khala/todo
Description: Simple TODO terminal app.
Author: Karel Hala
Latest version: 1.5.0

# Simple todo-cli app
Sometimes you need to write simple todo from command line. This tool will allow you to do this in couple of steps.

## Installing the command line tool
If you have NPM version 5+ you don't need to install it, and you can just run
```bash
$> npx todo-cli
```

Just install this package as global dependency
```bash
$> npm install -g @khala/todo
```

And then run it
```bash
$> todo-cli
```

## Example of new todo
![TODO example](static/todo-example.gif?raw=true "TODO example")

## Running todo-cli with options
This tool recognizes 6 options

| Option | longer | Description |
|---|---|---|
| `-a` | `--add` | Add new single TODO item |
| `-l` | `--mark` | Mark some items as done |
| `-m` | `--list` | List all tasks |
| `-f` | `--file` | Path where to store todo file |
| `-h` | `--help` | Prints help for this tool |
| `-v` | `--version` | Prints version of this tool |

### Path for todo file
If you want to store todo file somewhere else than `/${HOME}/.todos` you can use this option.

This option is trying to guess where todos will be stored on your machine, you have two options

* Full path
```bash
$> todo-cli -f /home/some/path/.todos
```
* Relative path to your home, file will be stored under your home folder, plus whatever you pass to it
```bash
$> todo-cli -f some/folder
```
npm package: @khala/wildcard-release-notes
Description: Monorepo release notes based on [@khala/commit-analyzer-wildcard](https://www.npmjs.com/package/@khala/commit-analyzer-wildcard) for [semantic-release](https://github.com/semantic-release/semantic-release) package.
Author: Karel Hala
Latest version: 2.5.2

# Monorepo wild card release notes
Monorepo release notes based on [@khala/commit-analyzer-wildcard](https://www.npmjs.com/package/@khala/commit-analyzer-wildcard) for [semantic-release](https://github.com/semantic-release/semantic-release) package.

## Installation
* Using NPM
```bash
> npm install -D @khala/wildcard-release-notes
```
* Using yarn
```
> yarn add -D @khala/wildcard-release-notes
```

Then add it to your `generateNotes`options

* `package.json`
```JSON
{
  "release": {
    "generateNotes": [
      {
        "path": "@khala/wildcard-release-notes"
      }
    ]
  }
}
```

## Options
This package will assume that you want to generate release notes for packages under root folder you ran release. If you want to release packages under different folder (for instance all packages under folder `plugins`) you have to add `folder` option to `generateNotes` option. Or if you want to set this up globally add `monorepo` prop to release config.
```JSON
{
  "release": {
    "generateNotes": [
      {
        "path": "@khala/wildcard-release-notes",
        "folder": "./plugins"
      }
    ]
  }
}
```

```JSON
{
  "release": {
    "monorepo": "./plugins",
    "generateNotes": "@khala/wildcard-release-notes"
  }
}
```

If you are not using Travis as your CI environment, you can specify the repository name (GitHub) manually:

```JSON
{
  "release": {
    "generateNotes": [
      {
        "path": "@khala/wildcard-release-notes",
        "folder": "./plugins",
        "repositoryName": "organisation/repository"
      }
    ]
  }
}
```

Otherwise `env.TRAVIS_REPO_SLUG` is used automatically.