Allmychanges

Here we instantly see how stale our environments.

Other changes

* Added option `--version`.
* Option `--config` was removed and now you have to pass token
via `--token` option or through `AMCH_TOKEN` environment variable.
* Command `export` was renamed to `pull` and it's parameter
`--output` was renamed to `--filename`.
* Command `import` was renamed to `push` and it's parameter
`--input` was renamed to `--filename`.

Major changes

* Now projects can be pushed to the server without source
URL or even name. But they will require further tuning
in HTML interface.
* Commands `push`, `tag`, `track` and `untrack` now require valid
authentication. This also means that corresponding methods
of Python API also fail without authentication.

Fixes

* API base url scheme was changed from `http` to `https` to fix
POST requests.

API Changes

* Function get_tags now returns iterable over all tags instead
of limited list of 10 tags.

Experimetal "tags" feature

This is not in AllMyChanges.com's interface yet, but
it's API now allows to tag some versions which you are
using in some projects. For that purpose, three additional
commands were added:

tag

This command tags given project version:


$ amch tag python/django 1.8.10 allmychanges.com


This command tells allmychanges, that I want to tag Django 1.8.10
with tag `allmychanges.com`. After this, a `tags` or `versions`
commands could provide this information.

tags

This command shows list of tags along with tagged projects.
Consider I runned a command from the section above. Than `tags`
output will be:


$ amch tags
allmychanges.com: python/django:1.8.10


versions

The other way to use information about tags is to view which versions
for the project exists:


$ amch versions python/django