---
title: "GitHub sync"
type: "glossary-term"
category: "Corpus & data pipeline"
canonical_url: "https://www.graphcanon.com/glossary/corpus-and-data/github-sync"
updated: "2026-07-09"
---

# GitHub sync

_Also known as: Refresh, Re-sync_

**GitHub sync re-fetches a tool's public GitHub facts (stars, language, last push) without re-running the language model.**

**GitHub sync** refreshes the GitHub-derived facts on an existing record - stars, forks, primary language, license, and last-push time - by re-querying the GitHub API. It does not regenerate AI summaries or edges.

Keeping this step separate from AI enrichment keeps refreshes cheap and lets facts stay current far more often than the (heavier) LLM pass.

## In GraphCanon

A tool's freshness date reflects its last GitHub sync, not its last AI enrichment. Scheduled syncs keep stars and maintenance signals current across the corpus.

## See also

- [Trending tools](/trending)

## Related terms

- [Ingest](/glossary/corpus-and-data/ingest.md)
- [Freshness](/glossary/corpus-and-data/freshness.md)
- [Metric snapshot](/glossary/corpus-and-data/metric-snapshot.md)

[Corpus & data pipeline](/glossary/corpus-and-data.md) · [All glossary terms](/glossary.md)

---

**Machine-readable endpoints**

- JSON: [`/api/graphcanon`](/api/graphcanon)
- LLM index: [/llms.txt](/llms.txt)
- Full corpus: [/llms-full.txt](/llms-full.txt)

_GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_