You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When this tool was first created, github organizations did not exist, thus a normal account was created. I wonder if it would make sense to to convert it into an organization. I think it would make administration easier. We could also globally disable the running of actions for the forked repos...
I don't know if there are any big differences in the API implementation, I would think not. Let me know what you think.
The text was updated successfully, but these errors were encountered:
My first understanding is that an organisation can not commit submitted translations (on behalf of an submitter). And do a pull request. (I guess they assume real persons are behind these actions).
So probably we need still a GitHub user account for committing and pull requests? It means, we keep the burden of sharing its authentication details between us(the maintainers).
Probably we can replace the account that is used to clone the repositories into. This makes it easier for you and me to delete old or broken repositories from it.
Not sure what https://github.com/KnpLabs/php-github-api library can handle, but probably it assumes a user and not an organisation? Probably fine to let it clone into an organisation by an user triggering these actions. There I see no issues.
So my summary is now: Having an organisation makes it easier to cleanup old or broken repositories? but the user account is then still needed for committing? Could already be worth the hassle.
When this tool was first created, github organizations did not exist, thus a normal account was created. I wonder if it would make sense to to convert it into an organization. I think it would make administration easier. We could also globally disable the running of actions for the forked repos...
I don't know if there are any big differences in the API implementation, I would think not. Let me know what you think.
The text was updated successfully, but these errors were encountered: