Discussing the article: "Beyond Clone and Commit: The Advanced Side of MQL5 Algo Forge"

New comment

Check out the new article: Beyond Clone and Commit: The Advanced Side of MQL5 Algo Forge.

We map the parts of Algo Forge that impact day-to-day MQL5 work: opening repos in MetaEditor, README translation, Units, branch/tag protection, browser patching, packages, and CI on a Windows host. The article shows exact settings, required runner labels, and how to gate merges on builds. You leave with reproducible steps to protect code, automate compiles, and ship artifacts.

The existing material on MQL5 Algo Forge covers the basics: creating a repository, committing from MetaEditor, pushing, pulling and branching. This article covers what comes after that. I went through the platform feature by feature and checked each one against the live instance, because Algo Forge is built on Forgejo, and what Forgejo documents is not always what this instance has switched on.

What follows is a practical map of the parts that matter for MQL5 development, including three additions MetaQuotes built for this community and a few limits worth knowing before they cost you time. Where a feature needs setup, such as the CI pipeline that compiles .mq5 files and fails the build on errors, I show the steps and the output.


Author: Shahzaib

Hello, and thank you for the article, very useful.

I have a question about webhooks. I had been using them (my Telegram bot sent notifications), but a few weeks ago the notifications stopped. When I try to open settings/hooks in my repository and /user/settings/hooks at account level, I only get a plain “Forbidden” page:

image


Even though I’m the owner and logged in.
Do webhooks still work for you? I wonder if they were restricted after you tested them in August, or if something needs to be enabled on the account. Thanks!
New comment