Master MQL5 Git in MetaEditor: Branch, Commit & Push

Why You Need Version Control for Your MQL5 Code

If you've ever overwritten a working EA with a broken change and spent hours trying to undo it manually, you already know why version control matters. For years, MQL4 and MQL5 developers relied on manual backups, zip archives, or external Git repos with clunky copy-paste workflows. MetaTrader 5 build 5100 changed that by integrating Git directly into MetaEditor through a feature called Algo Forge.

This guide walks you through the exact steps to set up and use MQL5 Git inside MetaEditor — creating repositories, branching for experimental features, committing changes, and pushing to a remote server for collaboration. You don't need to install Git separately or touch a command line. By the end, you'll have a professional code management workflow that saves you from losing work and makes team projects manageable.

Prerequisites

Before you start, verify these requirements:

• MetaTrader 5 build 5100 or higher — open MT5, go to Help > About, and check the build number. If you're below 5100, update via the broker's website or the platform's built-in updater.
• MetaEditor — comes with MT5, launch it by pressing F4 in the terminal or via the Tools > MetaQuotes Language Editor menu.
• A Git remote repository — you need a hosted Git service like GitHub, GitLab, or Bitbucket. Create a free account and a new empty repository (no README or .gitignore yet, or you'll need to clone instead of push).
• Your MQL5 project files — typically an Expert Advisor, indicator, or script you want to version. Have it open in MetaEditor or saved in your MQL5/Experts/ or MQL5/Indicators/ folder.
• Optional: A Git client like GitKraken or Git Bash — not required for basic operations, but useful if you need to resolve complex merge conflicts outside MetaEditor.

Step-by-Step: Setting Up MQL5 Git in MetaEditor

Step 1: Open the Algo Forge Panel

In MetaEditor, look at the right edge of the window. You'll see a narrow vertical tab labeled Algo Forge. Click it to expand the panel. If you don't see it, go to View > Toolbars > Algo Forge to enable it. The panel shows a Git tab at the top — that's your version control dashboard.

First time? The panel will be empty. You need to initialize a repository for your project.

Step 2: Initialize a Local Git Repository

In the Algo Forge panel, click the Git tab. You'll see a Create Repository button (folder icon with a plus). Click it. A dialog appears asking for the repository location. Navigate to the root folder of your MQL5 project — for example, if your EA lives in MQL5/Experts/MyScalperEA/, select that folder. MetaEditor will create a .git subfolder there.

You can also initialize from the File > New > Repository menu. Either way, once created, the Git tab shows the repository name and a list of uncommitted files.

Step 3: Configure Your Git Identity

Before you commit, Git needs to know who you are. In MetaEditor, go to Tools > Options > Algo Forge. Under Git Settings, fill in:

Click OK. Git now knows your identity for every commit.

Step 4: Stage and Commit Your First Snapshot

Back in the Algo Forge Git tab, you'll see your project files listed under Unstaged Changes. To commit everything:

1. Click Stage All (the plus icon with two arrows) — this moves files to Staged Changes.
2. In the Commit Message field at the bottom, write a descriptive message like "Initial commit: base EA structure with entry logic".
3. Click the Commit button (checkmark icon).

Your first commit is done. The Git tab now shows your commit hash (a 40-character hex string like a1b2c3d...) and the message. You can click the commit to see the diff of changed files.

Step 5: Create a Remote Repository on GitHub

Open your browser, log into GitHub (or your preferred Git host), and create a new empty repository. Do not check "Initialize this repository with a README" — you want it empty so you can push your existing history. Copy the remote URL — it looks like https://github.com/yourusername/your-repo.git.

Step 6: Add Remote and Push

In MetaEditor's Algo Forge Git tab, click the Settings gear icon. Under Remote, paste your remote URL into the field. Click Add. You should see the remote name (typically origin) appear.

Now click the Push button (upward arrow icon). A dialog asks for your Git provider credentials. Enter your username and a personal access token (not your password — GitHub deprecated password authentication for Git operations). To generate a token: on GitHub, go to Settings > Developer settings > Personal access tokens > Tokens (classic). Create a token with repo scope. Copy it and paste it into MetaEditor's authentication dialog.

If the push succeeds, your code is now on GitHub. You can verify by refreshing your repository page in the browser.

Working with Branches

Creating a Feature Branch

Branches let you experiment without breaking the main codebase. In the Algo Forge Git tab, click the branch dropdown (it shows main or master by default). Click New Branch, name it something like feature/optimize-entry, and click Create. MetaEditor switches to that branch immediately.

Make your changes — edit your EA's input parameters, add a new indicator call, whatever. When you're ready, stage and commit as before. The commit goes to your new branch, not main.

Switching Between Branches

To go back to main, click the branch dropdown and select main. MetaEditor automatically updates the file tree to reflect that branch's state. Important: Save all open files before switching — unsaved changes in the editor won't be lost, but they can cause confusion if they conflict with the target branch.

Merging a Branch into Main

Once your feature is tested and working, merge it back. Switch to the target branch (main), then in the Git tab click Merge (the double-arrow icon). Select the source branch (e.g., feature/optimize-entry). MetaEditor attempts a fast-forward merge. If both branches modified the same lines, you get a merge conflict — MetaEditor marks the conflicting sections with <<<<<<< and >>>>>>> markers. Edit the file to resolve the conflict, stage it, and commit the merge.

Collaborating with a Team

When multiple developers work on the same EA, each person clones the remote repository. In MetaEditor, use File > New > Clone Repository, paste the remote URL, and choose a local folder. Every developer can create their own branches, commit locally, and push to the remote. To get teammates' changes, click Pull (downward arrow) on your current branch.

I recommend agreeing on a branching convention upfront. A simple model: main is production-ready code, develop is integration branch, and feature branches branch off develop. This keeps main clean for live trading deployments.

Tips and Best Practices from Experience

• Commit often, with small changes. A commit per logical change (e.g., "Add trailing stop logic" not "Fix everything"). This makes history readable and rollbacks trivial.
• Write meaningful commit messages. Bad: "update". Good: "Refactor entry conditions to use ATR-based volatility filter". Future you will thank yourself.
• Use a .gitignore file. MetaEditor doesn't create one automatically. Create a file named .gitignore in your repo root and add patterns for compiled files (*.ex5, *.ex4), cache files (*.cache), and log files (*.log). This keeps your repository lean.
• Test merges in a separate branch first. Before merging a feature branch into main, create a temporary merge branch, test the compiled EA in the Strategy Tester, and delete the temp branch if it works.
• Tag releases. After a stable version passes backtesting, create a tag (in Algo Forge, click the tag icon). Name it v1.2.0 or similar. Tags make it easy to deploy specific versions to your live VPS.
• Back up your remote repository. Git is distributed, but your remote is the single source of truth for your team. Periodically clone it to a separate location.

Common Mistakes and Troubleshooting

Mistake: Pushing with the Wrong Credentials

Symptom: Push fails with "Authentication failed" or "403". Fix: Generate a new personal access token on your Git provider and use it in MetaEditor's authentication dialog. Ensure the token has repo scope. If you're using two-factor authentication, tokens are mandatory.

Mistake: Forgetting to Stage Files Before Commit

Symptom: Commit succeeds but some changed files aren't included. Fix: Always check the Unstaged Changes list before committing. Use Stage All if you want everything, or stage individual files by clicking the plus icon next to each.

Mistake: Merge Conflicts That Won't Resolve

Symptom: MetaEditor shows conflict markers but you're unsure which version to keep. Fix: Open the conflicted file in MetaEditor. Look for <<<<<<< HEAD (your current branch) and >>>>>>> branch-name. Decide which lines to keep, delete the markers, save, stage, and commit. If conflicts are complex, consider using an external merge tool like Meld or GitKraken — just configure it in Tools > Options > Algo Forge > External Diff Tool.

Mistake: Accidental Commits to Main Instead of a Branch

Symptom: You committed directly to main but meant to work on a feature branch. Fix: Create a new branch from main at the current commit — that branch will contain your changes. Then reset main to the previous commit using Reset in Algo Forge (use Soft Reset to keep changes staged). This is safe if no one else has pulled from main.

Mistake: Platform Version Too Old

Symptom: Algo Forge tab doesn't appear or Git functions are missing. Fix: Update to MT5 build 5100 or later. If your broker doesn't offer the latest build, download the standalone MetaTrader 5 installer from the MetaQuotes website and install it alongside your broker's version — you can use the same login credentials.

Summary

MQL5 Git integration through Algo Forge turns MetaEditor into a competent version control environment. You can initialize repositories, create branches for experimental features, commit incremental changes, and push to remote servers for backup and collaboration. The workflow mirrors standard Git, but stays inside your development tool — no terminal needed.

Start small: commit your current EA project today, create a branch for your next optimization, and push it to a private GitHub repository. Once you experience the safety net of version control, you'll wonder how you managed without it. The next step is to explore the Developer Hub tab in Algo Forge, which provides a marketplace for sharing and discovering MQL5 components — but that's a topic for another guide.