Split this repository into individual plugins

[Aeliot-Tm]

Pros

Automation of versioning

It permit to accept any amount of pull-requests without warring about manual updating of the version in plugin.php. Then just create release with standard functionality of Github and it will be updated automatically by Github Action. And if only one plugin updated then only one issued without affecting of others.

Automating PHAR builds & installing

It permit to automate building of PHAR file by Github Action. And it will be available in the assets of release.

So, consumers will not have to do it manually. This reduces user experience requirements and increases accessibility.

On the next step, it permit to automate the installing of plugins with the using of PHIVE (phar[dot]io). As language packs too.

Cons

Now all plugins uses make.php for he building of phar files. And you can worry about the avoiding of copy-paste of it. Then it can be put to separate repository. Regular users will not be need in it case phar files will be built automatically and they don't need to do it manually.

---

Help from my side

I quite experienced in automation and can help you for free 🙂
You can find examples in my repositories AI Auto Department Transfer Plugin and TODO Registrar.

[Aeliot-Tm]

@protich What do you think about this?

[JediKev]

@Aeliot-Tm

This is something we may consider for v2.0, so stay tuned!

Cheers.

[Aeliot-Tm]

Pay attention to project humbug/box. It helps to package phar