Does this work?

HAHA

Closed means either approved or rejected. In this case, approved.
Published means it's just sitting there, not approved or rejected.
With forking, leave the description alone except fix merge conflicts using those <<<<, ||||, and >>>> markers.

Interesting. I'm pretty sure I didn't get credit, as the translation is now under "Closed" on my profile, rather than "Published." Not sure if there's a way to check?

@Steffan153 I did try to fork it, but it always seemed to grab the old description and it wasn't going to fix the problem. When you say "fork it," can you be more specific about what and how to fork? I'd love to avoid this issue in the future. :-)

To fix merge conflicts, you have to fork it. The conflicts will remain if you don't. @kodejuice just did it for you.
The credit should still go to you.

Error: "Description cannot be approved, recent changes from related record must be merged first."

You didn't fork the translation so the author had to do it himself, maybe?

Can you explain the intention behind deprecating my fork and publishing your own?

Man... this UI is so confusing. It looks like I can't create a new translation now that one for TypeScript exists. Trying to create a fork didn't seem to solve the problem either. Any tips are welcome.

I copied the raw description off the current kata and pasted it into this one, hopefully that fixes the issue?

still giving the same error....just create a new translation instead of editing

Updated, I think. LMK if that didn't work.

Error: "Description cannot be approved, recent changes from related record must be merged first."

update the description, the original has been modified

Figured it out and fixed the tests. It was missing an it block.

I'm a bit confused, could you help out? I don't see how it has failed tests... This is my first time trying to provide a translation.

has failed tests