Hi
> Right - nice catch. I don't think there are any valid use cases for this code
now. And there is also similar code in the web
> templates.
>
> Please consider
https://kallithea-scm.org/repos/kallithea-incoming/changeset/ab8e9f05241a .
Thanks for the correction code.
I have applied this
On 09/05/2023 16:04, toras wrote:
> I propose
https://kallithea-scm.org/repos/kallithea-incoming/changeset/dee1b60bad29621882eb769eb5bc8707647ccf1d
.
As far as I have tried, I believe this change fixes the new owner to
operate correctly. (Both from the web and from the API.)
Thanks for
Hi.
Thank you for confirming.
> I propose
https://kallithea-scm.org/repos/kallithea-incoming/changeset/dee1b60bad29621882eb769eb5bc8707647ccf1d
.
As far as I have tried, I believe this change fixes the new owner to operate
correctly. (Both from the web and from the API.)
> I propose
On 07/05/2023 17:37, toras wrote:
Commit abc29122c7f2 has been addressed to allow repository group owner
changes.
I think the owner change itself is working.
However, for non-admin users, the permission evaluation in the
repository group seems to be incorrect.
For example, if you try to
Hi.
Commit abc29122c7f2 has been addressed to allow repository group owner changes.
I think the owner change itself is working.
However, for non-admin users, the permission evaluation in the repository group
seems to be incorrect.
For example, if you try to create a repository in that