gitea

• Gitea version (or commit ref): 1.14.3 + 1.15-dev
• Database (use [x]):
  • MySQL
• Can you reproduce the bug at https://try.gitea.io:
  • Yes, https://try.gitea.io/org/will-leave-owners/teams/owners = no longer accessible for me
  • No

Description

A user on Codeberg reported perse accidentally left the "Owners" team

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.

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

Is your feature request related to a problem? Please describe.
If the default branch is updated on a repo in github after it has been cloned locally into the ghorg dir and the branch didn't already exist when originally cloned, ghorg will error saying the repo does not have that branch. This typically happens when someone migrates an established repos default branch from master to main but lo