Discussing the article: "Moving to MQL5 Algo Forge (Part 4): Working with Versions and Releases"
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 4): Working with Versions and Releases.
The experiment with connecting the SmartATR library to the SimpleCandles Expert Advisor clearly demonstrated that the straightforward approach through simple cloning is not always convenient, especially when the code requires modifications. We instead followed the correct workflow: we created a fork, which became our personal copy of someone else's repository for fixing bugs and making modifications, while preserving the option to later propose these changes to the author via a Pull Request.
Despite certain limitations we encountered within the MetaEditor interface, combining it with the MQL5 Algo Forge web interface allowed us to successfully complete the entire chain of actions — from cloning to committing edits and finally linking the project with an external library. Thus, we not only solved a specific task but also examined a universal template for integrating any third-party components.
In today's article, we will take a closer look at the stage of publishing the edits made in the repository, a certain set of changes that form a complete solution, whether it's adding new functionality to a project or fixing a discovered issue. This is the process of committing or releasing a new product version. We will see how to organize this process and what capabilities MQL5 Algo Forge provides for it.
Author: Yuriy Bykov