refactor(forges/github): move GITHUB_API_MERGE_BATCH_SIZE into forges/github#2881
Merged
Merged
Conversation
setchy
approved these changes
May 12, 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
2 participants
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.
Summary
Small follow-up to #2874. The
GITHUB_API_MERGE_BATCH_SIZEconstant only governs GitHub's GraphQL enrichment batching, but it was sitting on the sharedConstantsobject — implying every forge cares about it. Move it next to its sole consumer (forges/github/enrich.ts) and import directly from the test.Test plan
pnpm exec tsc --noEmit— cleanpnpm lint— cleanpnpm exec vitest --run src/renderer/utils/forges/github/enrich.test.ts src/renderer/utils/notifications/notifications.test.ts— passes