Skip to content

Cache safe GitHub GETs in self-host runtime #1839

Description

@oktofeesh1

Summary

Self-hosted workers can repeat safe GitHub REST reads during webhook bursts and re-gate sweeps, especially branch-protection required-status reads. Add shared caching and single-flight for safe GitHub GETs across Octokit and raw backfill paths.

Scope

  • Cache safe GitHub REST GETs by caller identity, URL, and response-shaping headers.
  • Coalesce identical cold misses so concurrent jobs do not stampede GitHub.
  • Use short TTLs for hot PR/check/status reads and longer TTLs for stable metadata and branch-protection reads.
  • Expose cache counters in Prometheus and the self-host Grafana dashboard.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions