Undo an AI EA change cleanly: a practical version-control habit

AI-assisted editing is easier to explore when returning to a known version takes one deliberate step. A dated copy helps, but a change history also explains which lines were altered and why. That turns experimentation into a manageable workflow.

Save the starting point

Before asking for a change, record the source version, input preset and compile result. MetaEditor provides project and source-control facilities; a private repository or local version-control workflow can also serve this purpose. Choose access settings appropriate for purchased source.

Keep one purpose per change

An illustrative change might add a session label without altering entry rules. Save that separately from a later lot-sizing modification. Smaller changes make it easier to understand a difference in the log and to undo only the unwanted part.

Match source and executable

After compiling, record which source revision produced the EX5 that you load. Restoring an older MQ5 file does not replace an already compiled EX5 automatically. Check the loaded file and inputs before interpreting another test.

Ask AI for a change summary

Request a list of modified functions, expected behaviour and a short verification plan. Review the actual diff as well as the explanation. Keep credentials and private account records out of commits, and do not publish purchased source merely to obtain a backup.

MetaEditor projects and source control

Back to top