Steve Repsher

On second thought, you could use the [`get_home_path()`](https://codex.wordpress.org/Function_Reference/get_home_path) function: $htaccessFile = get_home_path() . '.htaccess' This function returns the path without the subfolder as desired.

What are your concerns with having it be part of the build? Maybe I can address them.

Yeah I get that. I was thinking the same, but come to the opposite conclusion. If the translations are removed from tracking, then everyone must execute the task at least...

There's a bug causing inconsistent failures (my favorite kind), so making this a draft until I figure that out.

Okay I fixed the issue with awaiting the extraction so you can test again. > Backend translations are not needed right? I think we only have those to support old...

Just for kicks I set the variable to skip and built with an empty translations directory. The build succeeds and you can fire up the UI, but there's lots of...

Yep, looks like that's what it does, but the `build-merged-translations` task uses the files in `translations/frontend` to decide which languages to merge: ```javascript gulp.task("build-merged-translations", () => gulp .src([inFrontendDir + "/*.json",...

Looking at the preceding `build-master-translation` task, it would be easier just to have that one write `build/translations/full/en.json`, and just skip English in the next task using it as the master....

Okay I didn't catch that. I can update that script to pull the core translations as well.

Okay here's what I did: - New clones will build frontend and supervisor English only (except for those inside GitHub actions) - Developer can setup multilingual builds by manually running...