a little confusing that all those other language files get added

a little confusing that all those other language files get added

That shouldn't have happened. I think it's because you're making your PR from the next-release branch of your fork instead of creating a new one.

That shouldn't have happened. I think it's because you're making your PR from the next-release branch of your fork instead of creating a new one.

Would you like me to test this theory? If it's true, perhaps we'll update guidance. If we could instead just merge this and go on, I'd prefer doing that this time.

A merge involving translatable files into next-release triggers a job (if actions are enabled) that updates the .po files. I had a look at your repo's actions and it's what happened. I don't think there'll be a problem merging this as it is.

Yeah, maybe we should recommend creating a new branch to make PRs from. It's recommended practice in general but no harm in spelling it out.

the same changes came in on PR 1150 just now, if that's easier.