Mrugesh Mohapatra

@tugkankibar thanks for reporting the issue and this PR. I am blocking this while we come to a consensus on the main issue, meanwhile please feel free to work on...

> We could write an action that runs when new files are added on `main` and have that action trigger the Crowdin upload/download flows. > If we'd rather just have...

I guess so. To be clear, if I understand this correctly: 1. Once the said workflow fails, we need the languages to catch up before deploying. While the languages can...

Yup - while the platform is hosted by Discourse, we do have the ability to use our theme on top of it for visual things. Interested contributors should look at...

You should reach out to the [contributor's chat](https://discord.gg/PRyKn3Vbay) for more help. Goodluck.

It's either waiting for review or blocked. All issues and PRs can have only one status at a time.

There are two ways to do this: - You can address any pending review commits and land this on a branch other than `main` on the main repo. That is,...

Yes - that is correct, and this workflow will then be limited to not being available to PRs. That is we can disable the `on: pull-request` even for a while...

I am not sure I understand this correctly. We already have Cypress workflows, and they work on PRs. Are we mistakenly confusing `on: pull_request` & `on: pull_request_target` events? The simplest...

@freeCodeCamp/dev-team 🤷🏽