chore: remove duplicate roadmap content files - #10211
Open
oscarbol09 wants to merge 1 commit into
Open
Conversation
Removes 61 content files that duplicated an existing file for the same node id, keeping only the file whose slug matches the canonical node label in the roadmap database. Also removes files for three node ids that no longer exist in the database (topic removed from roadmap). Verified against the official roadmap API: every remaining node id now maps to exactly one content file.
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
1 participant
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.
What
Removes 61 content files that were duplicates of an existing file for the same node id, keeping only the file whose slug matches the canonical node label in the roadmap database. Also removes files for three node ids that no longer exist in the database (topics removed from the roadmap).
Why
Each topic on a roadmap is linked to its content file by the node id in the file name. When a node label changes (or a sync ran twice), an outdated copy is left behind under a stale slug, e.g.:
svelte-kit@P4st_...mdduplicatedsveltekit@P4st_...md(canonical label: "SvelteKit")more-excersises@...md(typo) duplicatedmore-exercises@...md(byte-identical content)mutex@toev...mdvs canonicalconcurrent-ruby@toev...md(label: "Concurrent Ruby")amazon-rds-database@...mdvs canonicalglue-etl@...md(label: "Glue (ETL)")_nL7Wf1MG3mofKY9XwGDX,414WIX6TuK2h1jEtzRG2H(forward-deployed-engineer) andXY2l96sry3WyLzzo3KUeU(vibe-coding) were removed entirely -- those nodes no longer exist in the roadmap database.Verification
scripts/lib/slugger.ts) from the live node label fetched viahttps://roadmap.sh/api/v1-official-roadmap/<slug>.Note
A few of the deleted files carried content that is not present in the kept file (e.g.
prompt-vs-context-engineeringhad extra links;type-casting,threads,mutex,byebugdescribed different subtopics under the same node id). Since the database is the source of truth for the official roadmaps, those were removed rather than merged. Happy to salvage any of them if you prefer.