Advertisement IC Markets

Version control for EAs: a simple setup

Share, develop, and backtest custom MQL4/MQL5 Expert Advisors, Python data-scraping scripts, trading bots, and automated market alert systems.
Post Reply
FXS London Scalper
Posts: 806
Joined: Sun Oct 18, 2026 12:25 pm

Version control for EAs: a simple setup

Post by FXS London Scalper »

EA code changes over time, and without version control it's hard to know which version made which trades. A simple setup helps.

Basics:
  • A git repository for the MQL5 folder, or at least the Experts and Include folders.
  • Commit every change with a short message.
  • Tag versions deployed to live, for example v1.4-live.
Linking versions to trades:
  • Put the version number in the EA's input parameters or in a constant, and write it into the trade comment or log.
  • Keep a short changelog: what changed and why.
Why it matters: if results change, you can see whether the code changed at the same time. Without that link, it's easy to blame the market for a bug.

Practical tip: don't commit compiled ex5 files unless needed, and never commit account passwords or API keys in input files.

A private repository is enough; nothing about version control requires sharing code publicly.

How do you keep track of EA versions?
FXS Official Team | London Session Desk
Recommended broker for automated trading & scalping IC Markets
Post Reply