Repository navigation
docs: use Graph Data Council naming - #24
Merged
Merged
Conversation
prrao87
approved these changes
Oct 25, 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.
The repository and documentation site still refer to the council by its former name. Introduce “The Graph Data Council (GDC), formerly known as the Linked Data Benchmark Council (LDBC)” on the first mention in each affected document, then use GDC throughout its remaining prose, headings, link labels and benchmark disclaimers.
Updates the root README, Python development guide, and Read the Docs home, Cypher and benchmark pages. Canonical repository URLs, generated benchmark results and existing benchmark section anchors are preserved. Source/test identifiers and implementation comments are outside this documentation-only change.
Validation:
git diff --check HEAD^passed.uv run --project docs --locked zensical build --strictpassed in the working checkout and a fresh clone at exact commit07398a0e3298093993efcc7182bef1f6fce4f086.Remote-team reproducibility: passed for this documentation-only scope using the committed docs lockfile and documented build command. Requires uv and Python 3.12 or newer; no credentials, datasets, models, private artifacts or application services are needed. No dependency or build configuration changes.
Engine tests and runtime documentation snippets were not rerun; executable content is unchanged and no locally compiled extension is available. Hosted Read the Docs publication is unverified and awaits merge/build. This PR does not change benchmark measurements or runtime behavior.