Extend metadata.json with commit/branch/tag field about aiidalab HOT 5 CLOSED

I believe the issue is fixed in #80. I am going to close it.

from aiidalab.

Actually, I guess it would make most sense to put this information not in the metadata.json, but rather in the apps.json from the aiidalab-registry.

from aiidalab.

Mentioning @csadorf and @yakutovicha.

This change, or something equivalent, is a necessity for me before I can continue to move the aiidalab-optimade repository over to materialscloud-org as discussed with @giovannipizzi.

from aiidalab.

I'd prefer to use URIs to indicate the exact location and potential reference (branch) for this, see my comment on the related PR: aiidalab/aiidalab-registry#43 (review)

from aiidalab.

The final design:

An app registry entry is defined via a URL that references a git repository that contains an app. The URL must be of the form: <base_url>[@<ref>], where <base_url> must be a URL that points to a valid git repository and within the optional second part of the URL must be a git-reference that is valid for the referenced git repository.

from aiidalab.