Configuration File Is Invalid Issue 7 Crowdin Github Action Github I created a sample public repo and corresponding sample public crowdin project to try it out, but ran into an error: configuration file is invalid. check the following parameters in your configuration file: required option 'project id' is missing in the configuration file. required option 'api token' is missing in the configuration file. It seems that you have not created a crowdin.yml configuration file with the specified source and translation paths. please see the configuration file documentation.
Configuration File Is Invalid Issue 7 Crowdin Github Action Github I am getting configuration file doesn't exist. run the 'crowdin init' to generate configuration skeleton when trying to run the pre translation command with the github action. Replace the source and translation paths with the actual paths to your source and translation files. by default, the action will look for the crowdin.yml file in the root of the repository. you can specify a different path using the config option. Configuration file is invalid. check the following parameters in your configuration file: required option 'api token' is missing required option 'project id' is missing. Error is: “no sources found for ‘xxxxx’ pattern. check the source paths in your configuration file” this workflow worked fine until about 4 months ago, then started silently failing… thanks….
Github Crowdin Github Action A Github Action To Manage And Configuration file is invalid. check the following parameters in your configuration file: required option 'api token' is missing required option 'project id' is missing. Error is: “no sources found for ‘xxxxx’ pattern. check the source paths in your configuration file” this workflow worked fine until about 4 months ago, then started silently failing… thanks…. Try github action! an alternative to using this integration is the official crowdin github action, which allows you to more flexibly configure workflows and fully control security and access to the repo, since you do not need to authorize a github account in third party services. If your workflow file specifies the config property, you'll need to add the following to your crowdin configuration file (e.g. crowdin.yml): when the workflow runs, the real values of your token and project id will be injected into the config using the secrets in the environment. Mostly, in this kind of situation, you’d need to have two separate configuration files, one for vcs integration and another for cli. however, you can use a single configuration file for both cases. The crowdin.yml file contains a description of the resources to be managed and the api credentials (project id, api token, base path, base url). this means that it's not safe to commit this file to the code repository because the api key would be accessible to other users.
Configuration File Is Invalid Issue 7 Crowdin Github Action Github Try github action! an alternative to using this integration is the official crowdin github action, which allows you to more flexibly configure workflows and fully control security and access to the repo, since you do not need to authorize a github account in third party services. If your workflow file specifies the config property, you'll need to add the following to your crowdin configuration file (e.g. crowdin.yml): when the workflow runs, the real values of your token and project id will be injected into the config using the secrets in the environment. Mostly, in this kind of situation, you’d need to have two separate configuration files, one for vcs integration and another for cli. however, you can use a single configuration file for both cases. The crowdin.yml file contains a description of the resources to be managed and the api credentials (project id, api token, base path, base url). this means that it's not safe to commit this file to the code repository because the api key would be accessible to other users.
Comments are closed.