There is an issue in the translation, can you see the Discussion page and fix it? Note that in most other languages, expected is generated first randomly, and then the input is generated from it (so the tests don't use a reference solution).

Approved

Approved :)

When you publish a translation and want it to be reviewed for approval, post a suggestion in kata's Discourse page to give it more visibility.

As I told you, you need to publish a new fork and make the description in your fork match the current one. Once a merge conflict appears, it is impossible for a translation to be approved, updating it doesn't work.

Approved :)

No problem, it's not your fault.

You need to publish a new fork, this is mandatory once you have a merge conflict, the translation cannot be approved anymore.

Click on fork at the top right, then save a new fork. You need to make some change or it won't be accepted (just add or remove a space anywhere and it's fine).

It looks like it's just the bolding of "Examples". I tried removing it like the Julia translation and see the "diff" header go away in my translatons tab. Wish I could just see the actual git diff. Hopefully that's the fix? Sorry for the hassle.

Here you have another merge conflict (that's the problem with old translations...). Do the same as I told you in "Don't give me fixe" (you need to update the current translation for it to match with the specifications of go translation, just like you did before, but making sure you conserve the new informations that were introduced).

It's a recurring problem with translations that have been awaiting for approval for a long time. Once you update the translation (in a new fork), I'll approve it.

There is a merge description conflict (which means the description has been changed since you published your translation). You need to make a new fork to your translation (this is mandatory to solve the conflict), grab the current description and update the description in your fork accordingly (to get the last version of the description, do like if you created a new translation in any language, and copy the description from the tab description into yours). I hop it's clear, otherwise ask here.

bumped to go 1.18

bumped to go 1.18

updated to go 1.18.

totally fair, reduced to 100. also bumped it to go 1.18 while I was in there.

Last thing: 1000 tests are in general unnecessary, the standard is 100. It may depend, but here you are printing the input on each test (which itself is nice and user friendly) so one can experience full buffer issues in the browser. Most languages only do 30 tests. You should reduce to 100 tests IMO.

Thanks for the feedback akar-0. That makes sense. I've reduced the random numbers as requested. You're right, it was overkill.

Please let me know if there's anything I can improve or do differently.