negative pull requests #2208
Okay, that's weird, now it's gone for me too.
It's possible this might happen temporarily when the cache is not yet updated.
I've had this since Nov 12, 2025, 23:12 GMT+1 until now.
Hm that's interesting, feel free to comment when it happens again. Will be nice to know what the state of the cache at that point is then.
Same issue with https://codeberg.org/yuki0iq/statusline/pulls since 2025年11月15日 05:43:58 +01:00 (datetime of PR 3 merge) and it still shows -1 now
upd: it disappeared after opening another pull...
There were some other reports and this resulted in forgejo/forgejo!10130 and forgejo/forgejo!10127 - I'll try to get it deployed on the next Codeberg deployment.
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?