Mention proc-receive in text for dashboard.resync_all_hooks func

[strk]

That hook is the one required for AGit workflow, or clients will get:

remote: error: cannot find hook 'proc-receive'

For the record: I tried creating this PR using AGit but GitHub doesn't suppor it... how long should we wait before Gitea development is moved to a Gitea instance ?

[silverwind]

For the record: I tried creating this PR using AGit but GitHub doesn't suppor it... how long should we wait before Gitea development is moved to a Gitea instance ?

Last I checked, gitea.com was not performing as well as github.com at least for european users, it often had multi-second page load times, so I refrained from using it. Also remember the barrier of entry for new users is much lower on github.com where everyone already has an account.

[lunny]

For the record: I tried creating this PR using AGit but GitHub doesn't suppor it... how long should we wait before Gitea development is moved to a Gitea instance ?

Last I checked, gitea.com was not performing as well as github.com at least for european users, it often had multi-second page load times, so I refrained from using it. Also remember the barrier of entry for new users is much lower on github.com where everyone already has an account.

Could you evaluate it again now? I believe the performance should be fast enough at this point. Since gitea.com already supports logging in directly with GitHub OAuth2, I think it’s a good time to proceed with the migration.

[wxiaoguang]

Since gitea.com already supports logging in directly with GitHub OAuth2, I think it’s a good time to proceed with the migration.

It is not able to remember the login, makes it very annoying to use.

[lunny]

Since gitea.com already supports logging in directly with GitHub OAuth2, I think it’s a good time to proceed with the migration.

It is not able to remember the login, makes it very annoying to use.

Which service is failing to remember the login — Gitea.com or GitHub’s OAuth2? I’m unable to reproduce the issue on my side, so could you please open an issue with more details so we can investigate it further?

[wxiaoguang]

Don't you see this? OIDC users don't stay logged in #28394

[strk]

Last I checked, gitea.com was not performing as well as github.com at least for european users, it often had multi-second page load times, so I refrained from using it.

Wouldn't this be an opportunity to improve performance in Gitea ?

Also remember the barrier of entry for new users is much lower on github.com where everyone already has an account.

If I recall correctly Gitea does support login-via-github

[silverwind]

Could you evaluate it again now? I believe the performance should be fast enough at this point.

It is certainly better than before, but it's still not quite the level as snappiness I'd expect. Here comparing repo home page:

• gitea.com takes 650ms to deliver the HTML response with 200ms TCP latency
• github.com takes 85ms to deliver the HTML response with 32ms TCP latency
• my local gitea instance takes 26ms to deliver the HTML response with 0ms TCP latency

So gitea.com takes ~350ms just to render the HTML body. The bigger a gitea instance gets the slower it gets to render body, which should not be.