<commit_before># bmp v0.0.2

> Update version without hassle

`bmp` is a command line tool for updating the version number in source files.

# Motivation

It's common to have the version number of the library written in multiple places in a repository, e.g. meta files, documetation, source code, etc.

If the version number of the library written more than 1 place, updating these numbers in every release is very boring, very much error prone chore. `bmp` helps that situation with simple config file `.bmp.yml` which can track every occurence of the version number in a repository and updates every occurence consistently when you want to update it.

# Install

```sh
deno install --allow-read=. --allow-write=. https://deno.land/x/bmp@0.0.2/cli.ts
```

This installs `bmp` command.

# Usage

Hit the command in a repository you want to mange version numbers with `bmp`.

```
bmp init
```

This creates config file like the below:

.bmp.yml

```yaml
version: 0.0.0
commit: 'chore: bump version to %.%.%'
files:
  README.md: v%.%.%
```

- `version` is the current version of your repository. You need to update this to the actuall current version number.
- `commit` is the commit message which is used when you perform the command `bmp -c`, which commits with appropriate commit message, and cut the tag.
- `files` contains the version number patterns in files. If your README.md file contains `my-library v1.2.3`, then you need to set this property to `README.md: my-library v%.%.%`. (As you can see `%.%.%` part represents the version number)

Then you need to modify this file to fit the reality of your repository. It might be something like the below:

```yaml
version: 0.4.3
commit: 'chore: bump version to v%.%.%'<commit_msg>docs: fix init command in README.md<commit_after># bmp v0.0.2

> Update version without hassle

`bmp` is a command line tool for updating the version number in source files.

# Motivation

It's common to have the version number of the library written in multiple places in a repository, e.g. meta files, documetation, source code, etc.

If the version number of the library written more than 1 place, updating these numbers in every release is very boring, very much error prone chore. `bmp` helps that situation with simple config file `.bmp.yml` which can track every occurence of the version number in a repository and updates every occurence consistently when you want to update it.

# Install

```sh
deno install --allow-read=. --allow-write=. https://deno.land/x/bmp@0.0.2/cli.ts
```

This installs `bmp` command.

# Usage

Hit the command in a repository you want to mange version numbers with `bmp`.

```
bmp --init
```

This creates config file like the below:

.bmp.yml

```yaml
version: 0.0.0
commit: 'chore: bump version to %.%.%'
files:
  README.md: v%.%.%
```

- `version` is the current version of your repository. You need to update this to the actuall current version number.
- `commit` is the commit message which is used when you perform the command `bmp -c`, which commits with appropriate commit message, and cut the tag.
- `files` contains the version number patterns in files. If your README.md file contains `my-library v1.2.3`, then you need to set this property to `README.md: my-library v%.%.%`. (As you can see `%.%.%` part represents the version number)

Then you need to modify this file to fit the reality of your repository. It might be something like the below:

```yaml
version: 0.4.3
commit: 'chore: bump version to v%.%.%'
{'fraction_non_alphanumeric': 0.09335624284077892, 'fraction_numerical': 0.009163802978235968, 'mean_word_length': 3.885314685314685, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 5, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5335615', 'n_tokens_mistral': 1047, 'n_tokens_neox': 1002, 'n_words': 524}