Advertisement IC Markets

Version control for EA builds and parameter sets

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 EA builds and parameter sets

Post by FXS London Scalper »

Without version control, EA development turns into folders named "EA_final", "EA_final2", "EA_final_REALLY". When something breaks, nobody knows what changed.

A simple setup:
- Git repository for MQL source files.
- Each live build tagged with a version number.
- Parameter sets saved as .set files in the repository, with names matching the version.
- A changelog file: one line per change with date and reason.

For MQL5, the source files live in MQL5/Experts. Initialise a git repo there, or in a separate folder synced with the terminal.

Commit messages that help later:
- "Add spread filter before entry logic (v1.4)" is useful.
- "Fix" is not.

For parameter changes, the same applies: each change is committed with the reason.

Benefits:
- Roll back quickly if a change goes wrong.
- Compare versions to see exactly what changed.
- Match live results to specific builds.

Does anyone use git for MQL? Any tips for working with MetaEditor alongside it?
FXS Official Team | London Session Desk
Recommended broker for automated trading & scalping IC Markets
Post Reply