Ahjo

Initialize dummy file from Alembic
When initializing a new project, Ahjo creates a dummy file under `/alembic/versions`. This will make sure directory `/alembic/versions` is added to version control even though project has no Alembic migrations. It is a pain if this directory is lost, since Alembic actions require the existence of such directory.

Bug fix: Inform user if Alembic version table is empty
In previous versions, fetching Alembic version from empty Alembic version table caused Ahjo to crash. In this version, instead of crashing, Ahjo informs user that Alembic version table is empty and there are no deployed revisions.

Command listing available actions
With command `ahjo list` you can view all available actions and their descriptions.

Action name from function name
In older versions of Ahjo, action name had to be given as parameter to action decorator.

action(name='test', affects_database=False, dependencies=['deploy'])
def test_action(context):
print("Its working!")

In this version, if action name is not explicitly defined, the action will have the same name as the decorated function.
Underscones are interpret as hyphen. If the name of the decorated function is `test_action`, the action will be named `test-action`.

action(affects_database=False, dependencies=['deploy'])
def test(context):
print("Its working!")

Bug fix: Extended property name and value length when queried from database

Convert extended property names and values to VARCHAR(8000) when fetching them from database.

Bug Fix: Documented extended properties can contain non-ASCII characters
Action `update-file-obj-prop` stores all extended properties of objects in schemas listed in variable `metadata_allowed_schemas`. Extended properties are stored to JSON files with encoding UTF-8. These files can contain non-ASCII characters.

Improvements to handling of extended properties (Sql Server)
Ahjo includes an action that stores extended properties into files. At the end of `deploy` action, these documented extended properties are updated to database. Documented and updated schemas can be controlled with variable `metadata_allowed_schemas`.

Older versions of Ahjo supported documenting and updating only extended properties with name "Description". In this version, the name restriction is removed and all extended properties can be documented and updated. To better support documenting multiple extended properties, the file format is changed from CSV to JSON.

Action `update-csv-obj-prop` is renamed to `update-file-obj-prop`.

Remove `ahjo_path` from Context
`ahjo_path` is removed from Context class. If you need the path to packages' root, you can import it from context module.

from ahjo.context import AHJO_PATH

`ahjo_path` parameter is removed from function `operations.tsql.db_object_properties.update_db_object_properties`.

Fetch "Git version" with `git describe` command
At the end of `deploy` action, the current remote repository url (origin), branch name and commit hash are stored to database.
In older versions of Ahjo, this table had three columns:
- `Repository`
- `Branch`
- `Commit_hash`

In this version, the `Commit_hash` column has been renamed to `Commit` and the column now stores "Git version"- a "human-readable" object name that identifies commit or tag. This object is fetched with command `git describe --always --tags`.
Ahjo automatically renames the `Commit_hash` column, when `deploy` action is run.