Understand GitHub, files and versions
Know which repository your project uses and inspect the code behind the preview.
Connect the correct repository
Code projects use a GitHub connection for their repository. Authorize the requested account and repository access, then check the repository shown in your project. If an organization restricts app access, its administrator may need to approve it.
The file view helps you inspect the application source. A page in the preview is produced by routes and components in that source; a file name alone does not prove a page works. Check both the relevant code and the rendered result.
Verify a change
If repository access fails, resolve that connection before treating the change as saved to GitHub. Do not rely on an unfinished chat task as a completed revision.
- Wait for the coding task to finish and read its outcome.
- Open the changed files and confirm they describe the requested behavior.
- Check the linked repository and its latest revision.
- Open the preview and test the actual interaction, including navigation to another page.
Restore deliberately
Use the project’s version history to select an earlier result and restore it. Restoration affects the application source and needs to complete before you check the repository and preview again.
Restoring code is not a database backup or a reversal of actions in external services. If a change modified real data, review that data separately. Avoid editing the same repository elsewhere while a restoration is running.