Version Control and Rollback

Applies to: App Generation projects that use the SaaS Engine template

AppWizzy uses Git checkpoints for generated application source. These checkpoints help you save and restore code changes.

A project version is not a VM snapshot or database backup.

Create a version

  1. Open Edit via Chat or Code Editor.
  2. Finish one related set of changes.
  3. Test the affected application workflow.
  4. Select the main Save button.
  5. Enter a clear version message.
  6. Confirm the save.

The save commits current source changes to the ai-dev branch. It also sends the commit to the internal project repository.

If GitHub is connected, AppWizzy attempts to send the commit to GitHub.

Saving one file inside Code Editor creates a separate commit for that file.

Review version history

Open the clock icon in the AI Engineer header. The Version History panel lists saved commits from ai-dev.

Each entry shows a commit identifier, time, and message. The newest entry represents the current saved source version.

Use specific messages, such as Add invoice approval flow. Avoid messages such as changes or update.

Roll back to an earlier version

  1. Save current work when you might need it again.
  2. Open Version History.
  3. Find the required earlier version.
  4. Select Rollback to this version.
  5. Review the version message.
  6. Confirm the rollback.
  7. Wait for the source operation to finish.
  8. Reload and test the application.

Rollback removes later tracked changes from the working result. It also removes untracked workspace files.

AppWizzy creates a new revert commit. It keeps the earlier history instead of deleting it.

The rollback sends the new commit to the internal repository. It also attempts a GitHub push when GitHub is connected.

What rollback does not restore

Rollback does not restore these items:

  • database records or database structure already applied.
  • uploaded files outside the repository.
  • environment variables and secrets.
  • installed operating-system packages.
  • terminal history or browser profiles.
  • the complete VM disk.

A rolled-back migration file does not reverse an applied database migration automatically. Review database changes separately.

Pull external changes

Use Pull Latest in Version History to load GitHub ai-dev changes when GitHub is connected.

This action discards unsaved tracked changes before the pull. Save required work first.

Read GitHub Integration for the complete branch workflow.

If the rollback does not fix the issue

Review build logs and application logs. A code rollback can still require dependency installation, migration work, or a service restart.

Use Activity and Logs and Troubleshooting AppWizzy Projects for diagnosis.