Skip to content
All library documents

Using Shared Projects to Link MQL5 Algo Forge Repositories

Article MQL5 articles
Read the original

Summary

This article explains a MetaEditor workflow for developing an MQL5 project that depends on code stored in a separate Algo Forge repository. It distinguishes the default mql5 repository from additional repositories, which appear as folders under Shared Projects, and demonstrates cloning a library repository and a project repository locally. The example uses a library of include files and an Expert Advisor project that consumes them.

The author describes adjusting include paths to the shared folder, using feature branches to isolate fixes, and moving completed changes through develop and main. Branches support stable releases and concurrent work, while pull requests enable review even in a solo project. The article presents a software collaboration and organization workflow rather than a trading method. Its scope is limited to repositories owned by the same developer; using another author's repository as a library is identified as a more complicated case for later discussion. No trading performance evidence is offered.

Key ideas

  • MetaEditor exposes non-default Algo Forge repositories as folders under Shared Projects.
  • A project repository can reference library code held in a separate repository by updating its include paths.
  • Feature branches isolate changes, while develop and main can separate ongoing work from stable code.
  • Pull requests provide a review step that can help catch mistakes even in solo development.
  • The demonstrated workflow covers repositories owned by one developer, not third-party library access.

Tags

Execution

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.