How do large dev teams use LocaLazy without overwriting each other's work?

Set up

We’re currently using a standard automated setup of LocaLazy similar to what is detailed in this blog post.

Essentially, we have a develop branch and we create feature branches from that branch. We’re using GitHub Actions to automatically upload any new keys/changes that are made to our source language files when a PR is opened against develop (upload only occurs if changes are made to en files).

Problem

This works well if only one developer is making a change to our en source language files at a time.
But when we have multiple PRs open against develop that each makes updates to the source language files, we end up with inconsistent results in LocaLazy.

Question

How do large dev teams using LocaLazy deal with this problem of having multiple PRs open at the same time that each makes changes to source language files?