Add guidelines for changelog and group the commits
update the changelog with the latest commits since the last release
Co-authored-by: Lipis <lipiridis@gmail.com>
* .eslintrc.json is required to build using react-scripts
* Remove the extra "deps" step
This step can be done as part of the build (faster and more reliable).
* Add a GitHub Actions to build the Docker image
Make sure that "docker build" is working on every pull request before landing on master.
* Update package-lock.json
* Add .prettierrc in the Docker image to avoid warnings in the build step
* Revert "Update package-lock.json"
This reverts commit 7ef2eaadfae610771987bc8155670b895c139e7b.
* Make sure that the 'node_modules' layer can be cached
if package and package-lock.json didn't changed
* add script to calculate percentage of translation
* test translation change
* change translation
* test
* change translation
* Calculate percentages of each translation file
* test
* Calculate percentages of each translation file
* change translation
* test
* test
* Calculate percentages of each translation file
* test
* Calculate percentages of each translation file
* fix workflow
* test
* test again
* Calculate percentages of each translation file
* Calculate percentages of each translation file
* test
* refactor
* change build logic
* fix types, move English first
* docs added
* test translation file
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* test
* Calculate percentages of each translation file
* let this be the final test please
* Calculate percentages of each translation file
* test
* test
* Test
* Calculate percentages of each translation file
* test
* Calculate percentages of each translation file
* test
* Calculate percentages of each translation file
* test
* Auto commit: Calculate translation coverage
* test
* test
* test
* test
* Auto commit: Calculate translation coverage
* test
* only on master
* test
* test
* Auto commit: Calculate translation coverage
* switch to master branch
Co-authored-by: i18n automation <runner@fv-az76.2iswp1o5zimezclxzdlwqia2gf.cx.internal.cloudapp.net>
Co-authored-by: i18n automation <runner@fv-az129.idlktykl4ure3gqe2lnji05orb.cx.internal.cloudapp.net>
Co-authored-by: i18n automation <runner@fv-az76.pjgcdo5npjpenpqz2nk0ztqvxd.cx.internal.cloudapp.net>
Co-authored-by: i18n automation <runner@fv-az33.senarqq4ucbulg04aytwntvgah.cx.internal.cloudapp.net>
Co-authored-by: i18n automation <runner@fv-az51.icvemaqob4xunfekbtdiz2tu2c.cx.internal.cloudapp.net>
Co-authored-by: i18n automation <runner@fv-az78.gikxu4m3dpiulftj3bftpuu3ee.cx.internal.cloudapp.net>
Co-authored-by: i18n automation <runner@fv-az121.cqdewbghluceforu5pkvpnveec.cx.internal.cloudapp.net>
Co-authored-by: i18n automation <runner@fv-az139.jsbds1i2htye3fh1bzwbe4ugmf.cx.internal.cloudapp.net>
Co-authored-by: i18n automation <runner@fv-az50.0bg2cysi0dkefjvuua0a0kbd1h.cx.internal.cloudapp.net>
Co-authored-by: i18n automation <runner@fv-az51.nhi3in4tbx4ehjtltcwuwbwsua.cx.internal.cloudapp.net>
We have to investigate on this, because after the Typescript integration is not working anymore, so I have to deepen how we can configure the usage with TypesScript.
