[{"data":1,"prerenderedAt":210},["ShallowReactive",2],{"news-\u002Fnews\u002Fgithub-game-sync":3},{"id":4,"title":5,"author":6,"body":7,"date":198,"description":199,"draft":200,"extension":201,"image":202,"imageAlt":6,"imageCredit":6,"meta":203,"navigation":204,"path":205,"seo":206,"seoTitle":6,"stem":207,"tag":208,"__hash__":209},"news\u002Fnews\u002Fgithub-game-sync.md","Game Sync: your dialogues, in your GitHub repo",null,{"type":8,"value":9,"toc":189},"minimark",[10,14,18,25,30,93,99,103,138,146,150,161,165],[11,12,5],"h1",{"id":13},"game-sync-your-dialogues-in-your-github-repo",[15,16,17],"p",{},"Until now, getting dialogue into a build meant somebody opening the Export tab, downloading JSON and committing it by hand. It gets skipped, the build ships last week's lines, and nobody can tell what the writers changed. Game Sync does that step for you. Connect a game to a GitHub repository once, and LoreHub writes its dialogues into a folder there and opens a pull request with the changes. Your programmers review it and merge it like any other change. Writers don't need a GitHub account.",[15,19,20],{},[21,22],"img",{"alt":23,"src":24},"A merged pull request on GitHub titled LoreHub story update: LDOD2, opened by lorehub-syncbot, listing the updated dialogue files","\u002Fimages\u002Fnews\u002Fgithub-game-sync\u002Fgithub-pull-request.png",[26,27,29],"h2",{"id":28},"whats-new","What's new",[31,32,33,46,71,81,87],"ul",{},[34,35,36,40,41,45],"li",{},[37,38,39],"strong",{},"One pull request, kept up to date."," LoreHub commits to its own branch, ",[42,43,44],"code",{},"lorehub\u002F\u003Cgame>"," by default, and opens one pull request into your base branch. Later syncs update the same pull request until someone merges it. Nothing reaches your main branch without a person merging it.",[34,47,48,51,52,57,58,61,62,66,67,70],{},[37,49,50],{},"One readable file per dialogue."," Each dialogue is a JSON file in the ",[53,54,56],"a",{"href":55},"\u002Fdocumentation\u002Fdialogue-schema-api\u002Fexport-schema-v2","Export Schema v2",", in the folder you choose, with a ",[42,59,60],{},"README.md"," that says the folder is written by LoreHub. Dialogues in a ",[53,63,65],{"href":64},"\u002Froute-planner-guide","route scope"," go into subfolders named after their scopes, such as ",[42,68,69],{},"act-1\u002Fthe-harbour\u002Fintro.json",". The same story always gives the same files, so a diff shows only what a writer changed.",[34,72,73,76,77,80],{},[37,74,75],{},"Sync now, or on a schedule."," Press ",[37,78,79],{},"Sync now",", or let LoreHub check every hour or once a day. A sync opens or updates the pull request only when something changed.",[34,82,83,86],{},[37,84,85],{},"Only the access it needs."," LoreHub works through a GitHub app that you install on the repositories you pick. It writes only inside the chosen folder, and deletes only files it wrote itself.",[34,88,89,92],{},[37,90,91],{},"Status where writers work."," Each story card on the Stories page shows whether its game is synced, when it last synced, and whether the last sync failed.",[15,94,95],{},[21,96],{"alt":97,"src":98},"The src\u002Fstory folder of a game repository on GitHub, with one JSON file per dialogue and a README, all from the commit LoreHub story update: LDOD2","\u002Fimages\u002Fnews\u002Fgithub-game-sync\u002Fgithub-folder.png",[26,100,102],{"id":101},"how-to-use-it","How to use it",[104,105,106,117,132],"ol",{},[34,107,108,109,112,113,116],{},"Open your world's ",[37,110,111],{},"Integrations"," page and click ",[37,114,115],{},"Connect GitHub",". Install the LoreHub app on your account or organisation, and choose which repositories it can reach.",[34,118,119,120,123,124,127,128,131],{},"Under ",[37,121,122],{},"Game Sync",", click ",[37,125,126],{},"Set up sync"," next to a game. Pick the repository, the base branch and the folder, for example ",[42,129,130],{},"src\u002Fstory",", and when to sync.",[34,133,134,135,137],{},"Click ",[37,136,79],{}," and open the pull request from the link that appears.",[15,139,140,141,145],{},"The step-by-step guide covers every setting, what lands in the repository, and what to do when a sync fails: ",[53,142,144],{"href":143},"\u002Fgithub-sync-guide","Sync Your Dialogues to GitHub",".",[26,147,149],{"id":148},"good-to-know","Good to know",[31,151,152,155,158],{},[34,153,154],{},"Sync is one way, from LoreHub to GitHub. Edit the story in LoreHub: changes made to the synced files in the repository are overwritten by the next sync.",[34,156,157],{},"A dialogue without a start node can't be exported, so it is left out of the sync. The Stories page lists those dialogues so you can fix them.",[34,159,160],{},"GitHub is the only host for now.",[26,162,164],{"id":163},"try-it","Try it",[15,166,167,168,174,175,177,178,183,184,145],{},"Game Sync is available on every plan. Open your world in ",[53,169,173],{"href":170,"rel":171},"https:\u002F\u002Fapp.lorehub.app",[172],"nofollow","LoreHub",", go to ",[37,176,111],{}," and connect your repository. If something feels off, tell us on ",[53,179,182],{"href":180,"rel":181},"https:\u002F\u002Fdiscord.gg\u002FR5bhwjyGcS",[172],"Discord"," or ",[53,185,188],{"href":186,"rel":187},"https:\u002F\u002Fwww.reddit.com\u002Fr\u002Florehub",[172],"Reddit",{"title":190,"searchDepth":191,"depth":191,"links":192},"",3,[193,195,196,197],{"id":28,"depth":194,"text":29},2,{"id":101,"depth":194,"text":102},{"id":148,"depth":194,"text":149},{"id":163,"depth":194,"text":164},"2026-11-12","Connect a game to a GitHub repository and LoreHub keeps its dialogues there as JSON, delivered as a pull request your team reviews and merges like code.",false,"md","\u002Fimages\u002Fnews\u002Fgithub-game-sync\u002Fcover.png",{},true,"\u002Fnews\u002Fgithub-game-sync",{"title":5,"description":199},"news\u002Fgithub-game-sync","Release","dMZOFd1LdvzdHm5gxCzIOeWT2BZ3PYV8PxtVmglpK5A",1794849528232]