You can find that you have migration scripts to deploy, but the changes within those scripts have already been made to your development database. In this scenario, you can choose to mark those scripts as deployed. This will update the record of which scripts have been run inside the migration log table within the development database, without executing that script against the database.

This can be achieved by clicking the Mark as Deployed button in the script editor. Note that you will no longer see this option if you've deployed the project with the script included.

Once the migration has been marked as deployed, click Refresh. This will verify that your development database and SQL Change Automation project are now in sync.