The setup-ruby action was choking on the explicit Docker container image we were using in crowdin-pull. The only reason we were doing that was to run everything as root, b/c the crowdin action adds files owned by root, leading to permissions errors when we later move things around. This PR just uses sudo chown (which apparently works?!) to get the same effect.
The setup-ruby action was choking on the explicit Docker container image we were using in crowdin-pull. The only reason we were doing that was to run everything as root, b/c the crowdin action adds files owned by root, leading to permissions errors when we later move things around. This PR just uses
sudo chown(which apparently works?!) to get the same effect.