This issue is now marked as stale after 90 days of inactivity, and will be closed soon. To keep it, mark it with the "no stale" label.

hi, please assign me the issue if it's available

hi, please assign me the issue if it's available

Done!

I see that the mentioned validations (write access check and checking for existing repo at the same storage namespace) occur right now only for non-bare non-readonly repos.
I guess that these checks should be added only for non-readonly bare repos?

@idanovo any reason why we didn't add namespace validation on read only repos?

@idanovo any reason why we didn't add namespace validation on read-only repos?

@N-o-Z Yes- since this is a read-only repository, there is no harm in case the storage namespace we are using is already used by another repository or if we don't have write permissions for this namespace.
We can have for example one "regular" repository for this namespace and another read-only repo(s) for this namespace.
Maybe we should document this one better as it took me some time to remember we had done it.

@idanovo any reason why we didn't add namespace validation on read-only repos?

@N-o-Z Yes- since this is a read-only repository, there is no harm in case the storage namespace we are using is already used by another repository or if we don't have write permissions for this namespace. We can have for example one "regular" repository for this namespace and another read-only repo(s) for this namespace. Maybe we should document this one better as it took me some time to remember we had done it.

@idanovo Thanks for the explanation. I believe this indeed deserves documentation

@N-o-Z #8396

I would like to understand why this is the right thing to do. Creating a bare repo is intentionally a plumbing operation, and I am afraid of limiting it, especially at this late stage.

For instance, if we make this change then restoring a repository becomes harder: I need to worry about whether dummy already exists in the repository.

This needs a few minutes of face-to-face discussion; fortunately we have some coming up this week!