Import a GitHub Project to Replit and Confirm Which Revision You Publish

Importing a repository creates a Replit project with a Git revision. Publishing uses the app's current state. Record an identifiable value before publishing so you can tell whether the live site corresponds to what you reviewed.

Worked example

Look up the revision and the working tree state

git branch --show-current
git rev-parse --short=12 HEAD
git status --short

Steps

  1. Use Replit's GitHub import flow for a practice repository and record the revision you intend to test. In the Replit Shell, run the commands in the sample and check whether the workspace has uncommitted edits.
  2. Add a harmless build label such as demo-8 at a known URL or in your fixture page. Verify that the label is tied to the intended Git revision and visible in the workspace preview.
  3. Publish or republish the staging copy from the reviewed workspace. Check the published URL separately and confirm the label. Pull later Git changes and republish deliberately if your integration does not advance the deployed snapshot.

What to check

  • A clean workspace can still be on an outdated commit. Compare the printed commit with the revision you reviewed on GitHub.
  • When the workspace and published markers differ, inspect the publish status and build log before concluding the import failed.

See the Replit tool profile

References