mirror
/
front-end-interview-handbook
mirror of https://github.com/yangshun/front-end-interview-handbook.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update contributing guidlines for translations

This commit is contained in:
Yangshun Tay 2018-03-24 12:10:03 -07:00
parent 9bb0a694f3
commit 58aa023b3e
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CONTRIBUTING.md
View File

@ -14,7 +14,7 @@ As much as possible, try to follow the existing format of markdown and code. Any
### Translations ### Translations
Feel free to add translations for the questions and answers only. You might want to retrieve a translated copy of the questions from [the original repository] and start from there. Simply create an issue expressing interest in being a translator and you will be added to the repository. Translators have the responsibility of keeping the translated content up to date with the master copy. However, the `master` branch is protected from direct writes and translated work have to go through the Pull Request and review process before it can be merged into the repository. This is more for organizational purposes as different translators tend to have individual collaboration approach (some prefer merging, some prefer rebasing). Going through a Pull Request process will make the commit history more organized and clean. Feel free to add translations for the questions and answers only. You might want to retrieve a translated copy of the questions from [the original repository](https://github.com/h5bp/Front-end-Developer-Interview-Questions) and start from there. Simply create an issue expressing interest in being a translator and you can fork the repository and start translating. Translators have the responsibility of keeping the translated content up to date with the master copy. Translated work has to go through the Pull Request and review process before it can be merged into the repository. This is more for organizational purposes as different translators tend to have individual collaboration approach (some prefer merging, some prefer rebasing). Going through a Pull Request process will make the commit history more organized and clean.
### Code of Conduct ### Code of Conduct