Discussing the article: "Moving to MQL5 Algo Forge (Part 3): Using External Repositories in Your Own Projects"
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Check out the new article: Moving to MQL5 Algo Forge (Part 3): Using External Repositories in Your Own Projects.
In the second part of our transition to MQL5 Algo Forge, we focused on solving one of the important challenges –working with multiple repositories. Using the combination of the Adwizard library project and the Simple Candles Expert Advisor, we encountered and successfully resolved issues mostly related to file inclusion paths and branch merging. We also tried to use MetaEditor tools. where possible, throughout the entire workflow, from creating a separate branch for fixes to merging it via a Pull Request. However, where MetaEditor functionality was not enough, we switched to the MQL5 Algo Forge web interface, an external Git client in Visual Studio Code, or Git console commands. This clearly demonstrated how even in individual development, you can apply Git best practices to maintain order and a clear history of changes within your project.
But that was only one side: using the storage as a "closed" ecosystem where the developer owns all the repositories used. The logical next step, and one of the main reasons for moving to Git, is the ability to fully leverage public repositories from other community members. This is where the true potential of distributed development reveals itself: the ability to easily connect and update third-party code, contribute to its improvement, and assemble complex projects from ready-made, well-tested components.
In this article, we finally turn to this promising, yet more complex, task: how to practically connect and use libraries from third-party repositories within MQL5 Algo Forge. And not "someday in the future" but right now, without waiting for further development of MetaEditor's repository tools.
Author: Yuriy Bykov