-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fatal: pathspec 'other/*.json' did not match any files #10
Comments
Turns out I needed to create a single |
Good day! That's an interesting edge case, I'll look into it 👍 |
I might have a clue of what's going on. 🤔 If a key is assigned to the "Other" platform on Lokalise, it won't be exported when the JSON file format is requested ( One potential solution is to enable the Well, alternatively the key might be assigned to multiple platforms. Hopefully it solves the issue! /cc @amira-lok |
Thanks, I've tried the
It's a bit misleading if the file linked to the "Other" platform on Lokalise itself is a PS: There's an inconsistency in the
|
I wonder if it's related to the fact that I could "fix" the web key by adding a empty en.json file into the directory, maybe similar to what @bodrovis mentioned the default file that I'd need to create would be the native one for the "other" platform? In this case I'd want both of them to be |
Yep, sorry it should be |
@dewey , would you mind getting in touch with us through Intercom? I will pick up the case there and will help you, ok? I think it is better to do it over there. |
Okay, so I can see this on Intercom, we'll try to resolve this asap |
Hey—
I'm running the following GitHub Action and I'm running into the error below. The keys on Lokalise have a file assigned, and the "other" and "web" folder were created in my repository.
Do you have a pointer on where it's going wrong there?
Thanks!
The text was updated successfully, but these errors were encountered: