Answer the question
In order to leave comments, you need to log in
How to arrange several different, but with the same functionality projects?
For example, there are a couple of console scripts, in PHP, in JS (for Node) that do exactly the same thing and with the same settings for launching (that is, just a version for those who use PHP and a version for Node lovers).
How best to place them? Create different repositories or keep in one, in general? In theory, the division is more correct,
but the duplication of readme.md and documentation confuses. Or should I create an additional repository for the docks?
Answer the question
In order to leave comments, you need to log in
Also for having two separate repositories - although they do the same thing, the products are still different.
Yes, and CI / CD, if there is one, it will be easier to do.
And it will be easier for contributors to roll in - not everyone knows both js and php at the same time.
The documentation can really be taken out to a separate turnip / site (I would do it myself)
As an example of a project that is made according to this logic - playwright.
The API is the same, the documentation is the same, the vendor is the same, but it is implemented in Java, Python, C#, JS, and each implementation is in its own repository.
And in order for the repositories to be more or less grouped, you can create an organization account on github
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question