Pascal Birchler

Ideally we'd have 1 GitHub bot for all areas of our development workflow (translations, deployments, coding standards). However, for other people it might be easier if there's a single bot...

Thanks for sharing this suggestion 👍 I'm not sure if [the gettext library we use](https://github.com/php-gettext/Gettext/tree/4.x) supports that, but at first glance it looks like it at least does extract `#`...

Some providers like GitHub support both Git and SVN for the same repo. For this reason we should include the vcs type in the path

It would be nice if everything would be under `/tmp/traduttore` or something. As for the VCS type, this could be a sub folder of the repository dir, e.g. `/tmp/traduttore/github-wearerequired-traduttore/git` or...

This would only apply to a few projects when the source URL template is filled out correctly and the repository is publicly accessible.

Such a command could also include the checks from https://github.com/ePascalC/CheckPluginForTranslation

https://wp-translations.pro/ seems to support this too

Some thoughts after a quick chat yesterday: * Traduttore's main selling point is the language pack API, which is quite trivial. What if we somehow offered integrations with Transifex and...

Note that WP 5.0 with its new JSON translation files (#62) will result in a big shift once again. Right now no platform supports that format, at least not to...

Interesting: https://translationspress.com/