-
Notifications
You must be signed in to change notification settings - Fork 8
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
Crowdin stuff #37
Crowdin stuff #37
Conversation
not sure if this is a mistake instead of using the Crowdin CLI but we'll see
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
sigh why is PR workflow refusing to work properly |
nice... |
I've labeled your PR, assigned you and requested/un-requested reviews from the relevant people automatically. If you think I did it wrong, please comment below so one of our maintainers can double-check. Thanks! |
yes, you did it wrong they already reviewed it |
This pull request has conflicts with the base branch, which is main. Please resolve them. |
uh... I kinda can't? |
Resolved conflicts! |
Now we just need to check with @KTrain5169 that all is in order and we can merge |
I need to double-check some things regarding the workflow and the necessary files (I can't remember if the crowdin.yml is supposed to be placed in the branch root or in .github and I can't check right now)
So yeah don't merge it yet I'll merge it myself in a couple of hours
|
This reverts commit 40449f7.
This reverts commit 40449f7.
Pull request template
Category
Describe changes
Added GitHub Action that automatically pulls from Crowdin and updates strings. Also adds a translation progress badge to README because why not?
Why did you do this?
Makes it easier to integrate with Crowdin. The current solution being used at StopMalwareContent (owned by Nitrrine) is apparently not the best? And using the CLI via
pnpm
may expose secrets.BREAKING CHANGES
What issues (if any) would this resolve?
Resolves #36
Extra notes?
This PR should not be merged until all secrets are set. The secrets that need to be set are the following:
contents: write
GITHUB_TOKEN should work, but if for some reason it doesn't (I can't test rn due to some factors namely requiring Crowdin strings to be not updated I think?) then a collaborator/owner of the repo needs to create a GitHub PAT with the scope selected.Checklist
Vercel will begin deploying to the Preview environment shortly after submitting this pull request. You may click on the "Visit Preview" link below to see a preview of what your changes look like.
If you updated only part of the repository such that it would not modify the website at all, you do not need to see the Vercel deployment.
You may also use the StackBlitz Codeflow button to quickview the PR in the browser and make changes at the same time if necessary.