Version control for EAs: a simple setup
Posted: Mon Nov 02, 2026 8:17 pm
EA code changes over time, and without version control it's hard to know which version made which trades. A simple setup helps.
Basics:
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?
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.
- 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.
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?