I’ve recently changed some repository access permissions (from public to limited or private) and it seems, that even though I’ve updated this setting in Drone’s UI, it can’t clone from these repositories anymore.
As a sidenote, it seems that Drone completely ignores the visibility of the Gitea project the repositories are a part of - for example, having a project set to Internal results in Drone thinking it’s repositories are public, unless those repositories are explicitly set to private.
according to the change log, visibility was a brand new feature added to Gitea a week ago. New features added to Gitea don’t just automatically work with Drone. Someone needs to write code to map new Gitea fields to Drone fields. If you are interested in helping out, this is the relevant library that handles data mapping https://github.com/drone/go-scm
I’m running Gitea 1.14.1 - that’s a release from March - what you’re referring to is User visibility, and the ability to force it globally. Project/Organization visibility by contrast is a rather old feature (released March 2019).
Either way, there seems to be a completely separate issue, because my instance of Drone is configured to always authenticate with git via the DRONE_GIT_ALWAYS_AUTH env var.