LGTM.
but I was wondering if we still need to have the account details on the root level of the object and if we can somehow have this universally to be able to add integrations without changing this code here?
LGTM.
but I was wondering if we still need to have the account details on the root level of the object and if we can somehow have this universally to be able to add integrations without changing this code here?
but I was wondering if we still need to have the account details on the root level of the object and if we can somehow have this universally to be able to add integrations without changing this code here?
Yes, I would like this refactored soon. It should be possible to add arbitrary accounts. Unfortunately, all code relying on this is currently using the root-level properties.
> but I was wondering if we still need to have the account details on the root level of the object and if we can somehow have this universally to be able to add integrations without changing this code here?
Yes, I would like this refactored soon. It should be possible to add arbitrary accounts. Unfortunately, all code relying on this is currently using the root-level properties.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Allows to add Gitea account information to contributor profiles.
LGTM.
but I was wondering if we still need to have the account details on the root level of the object and if we can somehow have this universally to be able to add integrations without changing this code here?
Yes, I would like this refactored soon. It should be possible to add arbitrary accounts. Unfortunately, all code relying on this is currently using the root-level properties.