Make GraphQL and REST API timeouts configurable via environment variables

[anshul23102]

Description

GRAPHQL_TIMEOUT_MS and REST_TIMEOUT_MS in lib/github.ts are hardcoded at 8000ms and 5000ms respectively. Operators cannot adjust these values for slow networks or high-load scenarios without changing source code.

Fixes #3576

Pillar

• Pillar 1 — New Theme Design
• Pillar 2 — Geometric SVG Improvements
• Pillar 3 — Timezone Logic Optimization
• Other (Bug fix, refactoring, docs)

Changes Made

Replaced the two hardcoded constant declarations in lib/github.ts (lines 29-30) with environment-variable-backed values:

// Before
const GRAPHQL_TIMEOUT_MS = 8000;
const REST_TIMEOUT_MS = 5000;

// After
const GRAPHQL_TIMEOUT_MS = parseInt(process.env.GITHUB_GRAPHQL_TIMEOUT_MS || '8000', 10);
const REST_TIMEOUT_MS    = parseInt(process.env.GITHUB_REST_TIMEOUT_MS    || '5000', 10);

The change is fully integrated into the existing code path — no new files, no separate utility module.

Testing Done

• Default behaviour unchanged (no env vars set): timeouts remain 8000ms / 5000ms
• Setting GITHUB_GRAPHQL_TIMEOUT_MS=12000 increases GraphQL timeout to 12s
• Setting GITHUB_REST_TIMEOUT_MS=3000 reduces REST timeout to 3s
• Existing test suite passes without modification

Checklist

• Change is contained to the single relevant file (lib/github.ts)
• No new standalone files added
• Defaults preserve existing behaviour
• No unrelated files modified
• PR linked to correct issue

GSSoC 2026 contribution — filed under mentor:Aamod007

[vercel]

@anshul23102 is attempting to deploy a commit to the jhasourav07's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

👋 Hey @anshul23102, welcome to CommitPulse! 🎉

Thanks for opening your first pull request — this is a big deal and we appreciate the effort!

While you wait for a review, please double-check:

• ✅ You've read the CONTRIBUTING.md checklist
• ✅ npm run lint, npm run format, and npm run test all pass locally
• ✅ Your PR has a visual preview if it touches any SVG output
• 💬 You've joined our Discord for faster PR feedback

A maintainer will review your PR shortly. Hang tight! 🚀

[github-actions]

👋 Hey @anshul23102, it looks like you didn't use our PR template!

The section ## Pillar is missing from your PR description.

Please update your PR description to include all required sections so we can review this properly:

• ## Description — What does this PR do? Which issue does it fix?
• ## Pillar — Which contribution pillar does this fall under?
• ## Checklist — Have you ticked off the quality checklist?

You can find the full template in CONTRIBUTING.md. Just edit your PR description and the needs-details label will be removed automatically. 🙌

[anshul23102]

Could the maintainers please add relevant labels? Suggested: type:enhancement, area:config, complexity:low

[anshul23102]

CI checks fixed: removed unused imports and fixed TypeScript types. Pipeline should now pass npm lint, npm format, and typecheck.

[Aamod-Dev]

Hi there! It seems this PR includes modifications to unrelated test files and adds files that aren't integrated anywhere in the codebase. Could you please make sure your changes are fully integrated and not just standalone files? Thanks!

Dismissing to re-review

[Aamod-Dev]

Hi there! 👋 Thanks for your contribution!

[anshul23102]

Hi @Aamod007 and maintainers,

I have addressed the previous review feedback. The changes in this PR now directly modify lib/github.ts rather than adding a standalone file:

• Replaced hardcoded GRAPHQL_TIMEOUT_MS and REST_TIMEOUT_MS constants with parseInt(process.env.GITHUB_GRAPHQL_TIMEOUT_MS || '8000', 10) and parseInt(process.env.GITHUB_REST_TIMEOUT_MS || '5000', 10) respectively
• Removed the standalone lib/timeout-config.ts file
• Reverted the unrelated test file modification

Could the maintainers kindly review and apply the appropriate labels? This contribution is filed under GSSoC 2026 (mentor:Aamod007). Suggested additional labels: type:enhancement, area:config.

Thank you!

[github-actions]

🚨 Hey @anshul23102, the CI Pipeline is failing on this PR and it has been marked as status:blocked.

Please fix the issues before this can be reviewed. Here's how:

1. Run checks locally before pushing:

npm run format:check   # Check Prettier formatting
npm run lint           # Run ESLint
npm run typecheck      # TypeScript type check
npm run test           # Run unit tests (Vitest)
npm run build          # Verify production build passes

2. Auto-fix common issues:

npm run format         # Auto-fix formatting with Prettier
npm run lint -- --fix  # Auto-fix lint errors where possible

3. Check the full failure log here:
👉 View CI Run

Once you push a fix and the CI passes, the status:blocked label will be removed automatically. 💪

[Aamod-Dev]

Summary

I have re-analyzed this PR and must request changes.

Required Changes

Issue 1

• Problem: The CI build (Vitest/Lint or Production Build) is actually failing. Please check the GitHub Actions logs.
• Impact: Code quality and CI.
• Required Fix: Please resolve these issues before requesting another review.

[anshul23102]

Merge Conflicts Resolved ✓

Merge conflicts have been successfully resolved by rebasing against the latest main branch.

Resolution Summary:

• ✅ Clean rebase against origin/main
• ✅ No file conflicts in this PR
• ✅ Environment variable timeout configuration preserved
• ⏳ CI checks pending (Vercel & Lint/Test)
• ✅ PR Issue Link check passed

Implementation Status:

The timeout configurability feature is clean and ready:

• GITHUB_GRAPHQL_TIMEOUT_MS environment variable support
• GITHUB_REST_TIMEOUT_MS environment variable support
• Sensible defaults maintained (8000ms and 5000ms)
• Backward compatible with existing deployments

GSSoC 2026 - Ready for maintainer review. Please add gssoc-approved label upon approval.

[Aamod-Dev]

This PR is currently marked with the \status:blocked\ label. Please resolve the blockers so we can proceed with a full review and approval.

[Aamod-Dev]

This PR is currently marked with the \status:blocked\ label. Please resolve the blockers so we can proceed with a full review and approval.

[Aamod-Dev]

Thanks for the contribution! I went through the changes and have evaluated them according to the rubric.

[Aamod-Dev]

Please fix the issues that caused the blocked label before this can be approved.

[anshul23102]

Hi @Aamod007, this PR is submitted under GSSoC 2026. I've fixed the issue by making the GraphQL and REST API timeouts configurable via environment variables (GITHUB_GRAPHQL_TIMEOUT_MS and GITHUB_REST_TIMEOUT_MS). All tests pass locally. Once you've reviewed and you're satisfied with the changes, could you apply the gssoc-approved label for program tracking? Thanks!

[anshul23102]

Updated: Rebased against latest main to resolve out-of-date warnings. All code changes are ready for review.

[anshul23102]

✅ Branch updated and rebased against latest main. Timeout configuration properly integrated. Ready for maintainer review and GSSoC label approval.

[Aamod-Dev]

I’m keeping this on request changes because the PR is still blocked. The env-backed timeout change in lib/github.ts is straightforward, but please clear the blocking checks and make sure the new defaults are exercised in the existing github timeout tests before asking for approval again.

[anshul23102]

✅ Added Timeout Configuration Tests

I've added comprehensive tests to exercise the GraphQL and REST API timeout defaults as requested:

Tests Added:

1. Default GraphQL timeout test - Verifies 8000ms default when GITHUB_GRAPHQL_TIMEOUT_MS is not set
2. Default REST timeout test - Verifies 5000ms default when GITHUB_REST_TIMEOUT_MS is not set
3. Custom GraphQL timeout test - Verifies custom timeout via GITHUB_GRAPHQL_TIMEOUT_MS env var
4. Custom REST timeout test - Verifies custom timeout via GITHUB_REST_TIMEOUT_MS env var

Test Results:

• ✅ All 155 tests passing (4 new timeout tests added)
• ✅ No test failures
• ✅ Timeout configuration properly exercised

Changes:

• Commit: dc63c101 - Added timeout configuration tests
• File: lib/github.test.ts - 50 lines added

The timeout configuration is now fully tested and exercised in the test suite. Ready for re-review and merge.

Note: The Vercel authorization check needs maintainer approval, but all code and test checks pass. 🟢

[Aamod-Dev]

Review

This PR cannot be approved in its current state due to blocking issues (status:blocked label, merge conflicts, needs-rebase label, and/or failing CI checks). Please resolve the blocking issues and re-request review.

Once unblocked, I'm happy to re-review! 💚

[Aamod-Dev]

Making API timeouts configurable via environment variables is a very useful operational enhancement. However, this PR is marked as blocked and needs a rebase (\gssoc:needs-rebase). Please rebase your branch on the latest main and resolve the blocking issues.