Discussing the article: "Publish Your Article Code to MQL5 Algo Forge in 10 Minutes: A Step-by-Step Guide"
Именование
Use the name we give you. If you don't have a name yet, stick to a clear pattern:
[Тип материала]-[ID статьи]-[Краткая тема]
For example: Article-21732-Code-Tears-And-Algo-Forge. Such a name immediately links the project to the article and makes it easier to navigate.
Please do not make this a mandatory standard for people who have their own ideas about how to organise repositories.
My idea is like this. I have created an organisation where repositories related to one series of articles will be collected. It's like a "folder" that wraps related repositories, adds context, and allows you to give the repositories concise names. You open the organisation, and it neatly collects all the repositories related to a series of articles (and only them).
[Тип материала]-[ID статьи]-[Краткая тема]
For example: Article-21732-Code-Tears-And-Algo-Forge. This name immediately links the project to the article and makes it easier to navigate.
My situation is like this:
- One repository can be developed sequentially across multiple articles.
- Several repositories can participate in one article.
So this scheme does not work for me at all.
The idea itself is good and will work fine for most authors (I think). But I ask for permission not to follow it, if a person can reasonably explain why it is not suitable for him/her.
Типизация
- Empty - if an article has many files that need to be compiled separately....
You can split them into several repositories (often).
As an idea for those who have enough enthusiasm and discipline to bother.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
Check out the new article: Publish Your Article Code to MQL5 Algo Forge in 10 Minutes: A Step-by-Step Guide.
Is your article already published in MQL5? Then take the next step: turn the code from the article into a full-fledged project in MQL5 Algo Forge. Do not leave the source files only in an archive. Move them to the repository so that readers see the current version of the project, a clear file structure, a change history, and a clear description. Algo Forge is based on Git, but the main Git actions are already built into the MetaEditor interface, and README.md becomes the face of the project.
Prepare your MQL5 login, all files from the article, and a completed README.md. Do not postpone publishing your project until later. Create it now while you have all the code, settings, and supporting materials at your fingertips.
Take just a few simple steps to publish your project to the repository. Publishing your code will take no more than 10 minutes, and you will forget about messy archives, while your project will be stored and updated in the cloud.
Author: MetaQuotes