fix(gitea): stop rejecting Forgejo path commit lists - #98
Merged
Merged
Conversation
◈ PR Lens
Architecture 3 components touched across 5 lanes. Data flow
View
Tip Switch GitHub to dark mode and the diagrams follow. The moving dots are this pull request's data in motion. 🪧 More tips
Thanks for using PR Lens! It's built by Coldtea, free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
oritwoen
approved these changes
Sep 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Codeberg already pages commits by path. The 501 was Gitea's broken limit leaking onto Forgejo, overkill for the host people actually use. Live check: gitea.com dumped 47 rows at limit=2, Codeberg returned 2 and a real next link.