# How to use the changelog generator

It is recommended to use the master branch of integration to get the latest
fixes for the generator. This does not influence what versions you can query.

```
cd integration
git checkout master
cd extra/changelog-generator
```

## Setup

Make sure you have one directory that contains a copy of all the repositories
for Mender. They should also be up to date using `git fetch`.

## Running

```
./changelog-generator --base-dir <dir-with-repos> <old-version>..<new-version>
```

The generator will figure out which versions from each microservice to
query. Either version could be a build tag or an actual version.

# How to use the changelog generator

It is recommended to use the master branch of integration to get the latest
fixes for the generator. This does not influence what versions you can query.

```
cd integration
git checkout master
cd extra/changelog-generator
```

## Setup

Make sure you have one directory that contains a copy of all the repositories
for Mender. They should also be up to date using `git fetch --tags`.

## Running

```
./changelog-generator --base-dir <dir-with-repos> <old-version>..<new-version>
```

The generator will figure out which versions from each microservice to
query. Either version could be a build tag or an actual version.

Make sure build tags are included in changelog-generator instructions.
Make sure build tags are included in changelog-generator instructions.

They are usually not on a branch, and hence won't be fetched by Git
without the --tags switch.

Changelog: None

Signed-off-by: Kristian Amlie <505e66ae45028a0596c853559221f0b72c1cee21@northern.tech>
