Add Persian translation

[jamalkaksouri]

In accordance with the guidelines outlined in the contributing file, the Persian translation of this repository has been completed.

[abhinav]

@jamalkaksouri the PR is still broken:

All the PR needs is a new entry added to the README linking to your translation.
Everything else should remain unchanged.

[mway]

Hey @jamalkaksouri, thanks for the translation!

You don't need to include style_ir.md here; only include the change to README.md with the link to jamalkaksouri/uber-go-guide-ir. You can replace style.md with the translated version in your own repository (but if you'd prefer to keep the English style.md and add the translated version in style_ir.md, that's OK too).

See the most recent translation update, #157, as well as the repository that it links to, as an example.

[jamalkaksouri]

Hello @mway,

I want to express my gratitude for your guidance. As per your recommendation, I replaced the Persian translation in the style.md file. However, it appears that it automatically reverted back to its English equivalent. In the repository #157 many files and folders were not included, despite my previous attempts with this method, and the tests did not pass. Did I make a mistake?

[abhinav]

Hey, @jamalkaksouri, thanks for the translation. Our build process might be getting in the way a little.

First, just to clarify: @mway suggested not to modify the style.md in this repository, but you're free to modify or replace style.md in your translation repository (jamalkaksouri/uber-go-guide-ir).

Now, the reason that style.md reverted back to English is because of our build setup. We have the actual style guide contents inside the src directory. Afterwards, a CI Job merges the contents of the src directory into the style.md (relevant part).

Typically, translation repositories aren't forks. They just translate the contents and have their own history. I think you're running into this problem because your repository is a fork -- so it's making it difficult to keep the style.md unchanged while still making a PR for the README. There are a couple ways you could go about fixing this.

First option is: keep the repository a fork, but make the README PR from "before" the translation. Something like this:

# assuming there's an 'upstream' git remote pointing to uber-go/guide
git checkout -b add-translation upstream/master
vim README.md  #  add your translation to the README
git add README.md
git commit
# make a pull request with this branch

Then for your translation on master (not on this branch), disable the CI job (delete the ci.yml file) and the src directory. Your translation will be maintained in the style.md and you can update it as needed. (You can revert the "Auto-update style.md" commit when you do that.)

Second option is: use the fork only to add an entry to the README. Create a separate repository for the translation.
To do this:

• Rename jamalkaksouri/uber-go-guide-ir back to jamalkaksouri/uber-go-guide
• Create a new repository jamalkaksouri/uber-go-guide-ir, and copy the CODE_OF_CONDUCT, LICENSE, and README to it, along with your translation.
• Go back to your fork (jamalkaksouri/uber-go-guide), and make a Pull Request adding a link to jamalkaksouri/uber-go-guide-ir to the README.

Hope this helps!

[abhinav]

Relatedly, @mway, we may want a section in the CONTRIBUTING.md about contributing translations.

[mway]

Agreed, I think that would be good.

[jamalkaksouri]

Thank you @abhinav,

I would like to express my gratitude for your swift response and comprehensive guidance. I have implemented the second suggested approach, and the repository is now up-to-date and ready for merging.

[abhinav]

Excellent! Thanks, @jamalkaksouri.