Mention proc-receive in text for dashboard.resync_all_hooks func #35991
Conversation
That hook is the one required for AGit workflow, or clients will get: remote: error: cannot find hook 'proc-receive'
GiteaBot
added
the
lgtm/need 2
github-actions
bot
added
modifies/translation
docs-update-needed
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. |
GiteaBot
added
lgtm/need 1
It is not able to remember the login, makes it very annoying to use. |
GiteaBot
added
lgtm/done
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? |
|
Don't you see this? OIDC users don't stay logged in #28394 |
* giteaofficial/main: Fix various permission & login related bugs (go-gitea#36002) Allow empty commit when merging pull request with squash style (go-gitea#35989) [skip ci] Updated translations via Crowdin Mention proc-receive in text for dashboard.resync_all_hooks func (go-gitea#35991) Update JS deps (go-gitea#35978) wiki: reuse selectable style for wiki (go-gitea#35990)
7 participants
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 ?