

We told you to merge all your repositories. You didn’t do it, and now you have a special repository for the releases? That’s ridiculous. You should do it ASAP if you want to be taken seriously. ONE repository called D.eSystem, that’s all.


We told you to merge all your repositories. You didn’t do it, and now you have a special repository for the releases? That’s ridiculous. You should do it ASAP if you want to be taken seriously. ONE repository called D.eSystem, that’s all.


We told you to merge all your repositories. You didn’t do it, and now you have a special repository for the releases? That’s ridiculous. You should do it ASAP if you want to be taken seriously. ONE repository called D.eSystem, that’s all.


Definitely one and only one repository where the “versions / releases” are branches or tags. That way, you can compare your versions with git, fix an old version, etc.
Having multiple repositories is a PITA for you and for others.
I like this branching strategy but you can use your own: https://trunkbaseddevelopment.com/


The comment below is written by my agent:
You’re absolutely right, that’s very interesting /s


The hacker way is to self-host your food: !cooking@lemmy.world
If it’s not a lie, it’s not worth it anyway, we have better things now. I do love the boot lickers who want to help him though.