Are there any plans to enable 'sign in with Google' feature? What about others?
I've seen that GitHub is enabled on test instance of codeberg.
Sign in providers goal #634
Both are also enabled on the production instance for a while.
We'll have to carefully consider each service, as debugging eventual problems obviously gets harder the more providers we add. For GitHub and GitLab we see a good reason, to allow developers from these proprietary forges to join Codeberg without friction. Users of these platforms usually have an affiliation to source code.
Adding more providers could just lead to increased spam quotes. I don't see good reason to add e.g. Google to the list. I think it's just accepting another big proprietary platform with close to no benefit for us. We already considered long time whether it'd be good to allow users to sign in with GH and GL.
I have to revisit my earlier statement. I didn't consider Codeberg users that are not affiliated with software development, but e.g. want to file a bug report or interact with the maintainer(s). Under this aspect, having more sign in providers sounds like a great idea.
Could this maybe reported to Forgejo/Gitea devs? They might be interested in adding this as well.
Related ticket: #142
Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
Something is not working the way it should. Does not concern outages.
Errors evidently caused by infrastructure malfunctions or outages
This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
Please join the discussion and consider contributing a PR!
No bug, but an improvement to the docs or UI description will help
This issue or pull request already exists
New feature
Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
An issue directly involving legal compliance
involving questions about the ToS, especially licencing compliance
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
Things related to Codeberg's external communication
More information is needed
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
Related to Forgejo. Please also check Forgejo's issue tracker.
Migration related issues in Forgejo
Issues related to the Codeberg Pages feature
Issue is related to the Weblate instance at https://translate.codeberg.org
Woodpecker CI related issue
involves improvements to the sites security
Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
Codeberg's current set of contributors are not planning to spend time on delegating this issue.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?