“Sync to GitHub” warns: Repository Has Different History

[stevgon]

I’ve only pushed to this repository using the Sync to GitHub dialog. It had been syncing normally, but a couple of hours ago I received this warning:

The commit listed under “Commits that will be lost:” (dated 10/26/2025) is actually the initial commit created when the repository was first made by the app.

[AshishKumar4]

I see, that might be due to the template files being modified. In the app's DO based git, only app's core file changes are tracked. And upon any export API call (github export or git clone), the whole app's DO git is rebased over the latest template code with updated bootstrap/package.json files.
Thus, if any changes have been done to the template files (including dynamic ones like bootstrap or package.json), it might show out of sync.
But I think it should be safe to force push - You can verify by directly cloning the app locally instead of pushing to github, and then checking the git history of it and all core files, and then maybe running it locally to verify it looks and works exactly it should, which I expect it would

[stevgon]

Thanks! The force push worked fine.

From a vibe coding perspective though, that warning can feel a bit intimidating — it really looks like something might break.