gitea

Description

When creating a release in repo, the telegram bot sends the following message:

[{owner}/{repo}] Release created: {release_title} by {publisher}

A link is added to {release_title} : https://{base_url}/{owner}/{repo}/src/{tag_name}
This is a link to the tag although a link to the release was expected: https://{base_url}/{owner}/{repo}/releases/tag/{tag_name}

https://github.com/google/starlark-go/blob/master/doc/spec.md

It should satisfy our reproducibility needs (like jsonnet) and could be easier to write agola config files.

Like in #137 we should provide build context information.

Is your feature request related to a problem? Please describe.
Ensure the README.md understandable for users of all experience levels and domain expertise.

Describe the solution you'd like
Would be great to get some feedback on the readme to flush out anything that is unclear/not obvious and or spelling/grammar mistakes. Please open a PR for review.

Currently if you try to clone a repository from github and you don't have any ssh keys configured at github, you will fail to clone and get such message:

Fatal error: fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Even Permission denied (publickey). message is not shown.

@guyzmo offered to "suggest a