Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Translate situation report to Russian
See original GitHub issueThe narrative from 2020-03-05 should be translated to Russian. A branch exists as sit-rep_ru where this can be done, and the file to translate is ncov_sit-rep_ru_2020-03-05.md (you can translate in this file directly). The file is here: https://github.com/nextstrain/ncov/blob/sit-rep_ru/narratives/ncov_sit-rep_ru_2020-03-05.md
Note this file is in Markdown - it’s important not to change any links!
Comments to help with translation are noted in comment symbols like <!-- Comment -->
You can preview your changes (after pushing) here: https://nextstrain.org/community/narratives/nextstrain/ncov@sit-rep_ru/sit-rep/ru/2020-03-05
Please remember to push often as multiple people may be working on this translation!
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:15 (15 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
yes, can do within an hour!
Hi @cassiawag. My last translation was overwritten by dtaliun because I believe the version of that user didn’t contain my changes. Could you please advise how should I make the changes so that they appear in the main branch? I still have the following message when I’m editing the file: “You’re editing a file in a project you don’t have write access to. Submitting a change to this file will write it to a new branch in your fork frogtraveler/ncov, so you can send a pull request.” – Update: I gained the ability to commit now, no worries.