Release 0.20.0

Release notes

Remove 0pdd

Use separate docker worker for serving docs

Allow `./workflows robot` to run updated `.bats` files

Use `bats-core` instead of `bats` [#135]

Display only the last installed version of Elegant Git

Run tests on multiple Bash and Git versions

Pass `git clone` arguments to `git-elegant clone-repository`

Restore line with `git clone` in `clone-repository` command

Add `actualize-work` command

Actualize work based on what a user requests

Use the latest version of the default branch commits

Release 0.19.0

Release notes

User-related improvements

Standardize wording across all documents

Add logic of protecting branches

Configure `core.editor` for each repository

Improve acquiring logic

Introduce Elegant Git badge

Don't set protected branches in global configuration

Make the default development branch configurable

Development improvements

Print error with a relevant command for docs generation

Run tests based on sources modifications

Release 0.18.1

Release notes

Use Bash pattern matching instead of `sed` in `show-commands`

Read multi slash branch names when `deliver-work` [#255]

Prevent "binary operator expected" error

Release 0.18.0

Release notes

Elegant Git updates

Actualize the configuration approach docs

Start work from the alternative branch

Support offline mode for `start-work`

Support local branches in `accept-work` command

Add `show-workflows` command

Add `make-workflow` command

Add `polish-workflow` command

Open a given workflows file when `polish-workflow`

Development improvements

Generate docs using Python instead of Bash

Unify the assertions look for all tests

Release 0.17.0

Release notes

Support untagged repository during the release process [#240]

Show release notes for a repository without tags

Configure signature for a repository [#11]

Add Zsh completion [#230]

Use unambiguous algorithm to complete remote branches

Prevent "not a git repository" warning

Abort signature configuration if there is no key [#243]

Development improvements

Remove unsupported `-nw` option from Bash completion

Make `git for-each-ref` more developer-friendly

Release 0.16.0

Release notes

Apply preserves stash after rerun of failed command

Apply preserves branch after rerun of failed command

Document pipes

Support active rebase process during `deliver-work` execution

Support active rebase process during `accept-work` execution [#146]

Support workflows from repository subtrees

Display current state of WIP with `show-work` command [#231]

Make Elegant Git working with unavailable remote [#116]

Add initial commit after initialization of the repository

Use the latest changes of the `master` branch during pruning repository

Prevent "not a git repository" error during initiating a repository

Development improvements

Add first contribution greetings

Release 0.15.0

Release notes

Add the ability to polish current work

Apply only created stashes automatically

Rename `commands` command to `show-commands`

Remove useless branches in a repository

Remove remote branches only for `origin` after accepting work [#171]

Development imporvements

Use `vi` as the default editor during testing and debugging

Don't ask issue number in the pull request template

`acquire-git` command, small improvements

Release notes

Use `<h3>` HTML tag to format header linei of release notes

Make Git configuration reusable [#177]

Introduce `acquire-git` command [#177]

Simplify the configuration process [#177]

Prevent "git-elegant: command not found" error on Brew

Add smart functions detection during installation

Refresh current index before trying to stash changes

Check both stashed and unstashed changes before making auto-stash

Introduce workflows

Release notes

Introduce workflows [#192]

Use original `git`'s exit code when deliver work

Don't suppress a `git push` output when deliver work

Skip workflows if needed [#192]

Add `--help` and `--no-workflows` for all commands

Internal changes

Define workflows for the project

`deliver-work` enhancements

Release notes

Use existing upstream branch if available when `deliver-work` [#207]

Open URLs from push output if they are available [#165]

Don't add `show-release-notes` call to the release notes