open-index/open-npm huggingface dataset:
npm package: @shelf.network/changelog-cli
Description: CLI tool for changelog automation
Author: Ihor Diachenko
Latest version: 1.0.4

# Overview

CLI tool for [changelog](https://keepachangelog.com/en/1.0.0/) automation.

## Installation

```bash
# install globally:
npm i -g @shelf.network/changelog-cli

#install as a dev dependency
npm i -D @shelf.network/changelog-cli
```

## Usage

Release changes from `[Unreleased]`

```bash
changelog-cli release # use version from package.json

# or

changelog-cli release 1.0.1
```

Get release changes:

```bash
changelog-cli get latest # get the latest release changes
changelog-cli get 1.0.1  # get a specific release
```

Custom changelog location:

```bash
changelog-cli -f ./nested/CHANGELOG.md get latest
```
npm package: @shelf.network/imgproxy
Description: NodeJS client library to generate imgproxy urls
Author: Koen Punt
Latest version: 1.0.0

# @shelf.network/imgproxy

Fork of [imgproxy](https://github.com/DarthSim/imgproxy) optimized for front-end bundle size.
Signature of links is removed.

## Usage

```ts
import Imgproxy, { Gravity } from 'imgproxy';

const imgproxy = new Imgproxy({
  baseUrl: 'https://imgproxy.example.com'
});

imgproxy
  .builder()
  .resize('fill', 300, 200, 0)
  .gravity(Gravity.north_east)
  .dpr(2)
  .generateUrl('https://example.com/path/to/image.jpg');
```

## Contributing

1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Added some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request

## License

This project is licensed under the [MIT License](LICENSE.md).
npm package: @shelf.network/jira-cli
Description: CLI tool for Jira automation
Author: Ihor Diachenko
Latest version: 1.0.2

# Overview

CLI tool for Jira x GitLab automation.

## Installation

```bash
# install globally:
npm i -g @shelf.network/jira-cli

#install as a dev dependency
npm i -D @shelf.network/jira-cli
```

## JIRA API Access

Jira connection options must be specified in the following env variables:

```bash
export JIRA_HOST="..." # your Jira domain
export JIRA_USERNAME="..." # your Jira username
export JIRA_TOKEN="..." # Jira API token, get it here: https://id.atlassian.com/manage/api-tokens
export JIRA_PROJECT_ID="2131231" # Get it from Chrome DevTools, hacker
```

## Usage

Transition all issues associated with a merge requests:

```bash
jira-cli transition "WIP: [SHF-1, SHF-2] Moderate Bucket" # the issues go to "In Progress" column
jira-cli transition "[SHF-1, SHF-2] Moderate Bucket" # the issues go to "In Review" column
jira-cli transition --merged "[SHF-1, SHF-2] Moderate Bucket" # the issues go to "QA Pending" column
```

Create a Jira release, move all associated issues to "Done":

```bash
jira-cli release "Admin Panel" "v13.0.0"
```