-
-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Discussion] Gitea/Forgejo #154
Comments
Aside: since I'm spamming the repo, thought I'd also at least take a moment to thank you, @thomiceli, for making this. I've wanted exactly this product Forever™ (it seems like). 😭 |
I did not mess with Forgejo yet, but I guess since it's a fork, the oauth system works as same as Gitea, so it's more like a semantic problem ? |
Correct. I have my Opengist using my Forgejo for auth and it works 100% as expected. :) |
I opened a PR that let the server admin decide what name the button should have. I think it's ok for server admins to know that Gitea and Forgejo can be used interchangeably as long as the APIs do not break compatibility. And when that happens we have to implement another integration anyway 🤷♂️. |
I don't really know the best way to handle this...but thought I would bring it up for discussion.
Context
Forgejo is a soft-fork of Gitea. They provide a justification for existing:
Why did you open this discussion issue, @wkeiuluf?
As you may or may not know, users aren't always the brightest. Seeing "login with gitea" might be confusing to a user (not the admin setting everything up, but one of their users) that is like "hey, what's gitea?"
Basically, I think it would be nice to have an aliased set of
GITEA
stuff but withFORGEJO
in place. But that might not be the cleanest way to handle it. Hell, people reading this may even just think "you're dumb, who cares" and that's fine, too; that's why I opened up a discussion for this. 😅Another idea: maybe just change the button to "login with git" or something?
Anyway, just curious other people's thoughts on it.
The text was updated successfully, but these errors were encountered: