Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Translated how-to-label-an-issue.md #41

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

the-coder-dude
Copy link

Did Hindi translation of full-page, suggestions are welcome

@the-coder-dude the-coder-dude changed the title Updated how-to-label-an-issue.md Translated how-to-label-an-issue.md Feb 9, 2020
@the-coder-dude the-coder-dude mentioned this pull request Feb 9, 2020
62 tasks
@the-coder-dude
Copy link
Author

@SatyaRF @sakshamtaneja21 @arshadkazmi42 Anyone free? 😥

@arshadkazmi42
Copy link
Contributor

@prateekpardeshi I will review it ASAP. Don't worry, your work will not be wasted. Whatever PRs comes it gets reviewed for sure.

@the-coder-dude
Copy link
Author

@arshadkazmi42 Hope that you are free tomorrow 😐

Copy link
Contributor

@arshadkazmi42 arshadkazmi42 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good start.
added review till line 28.
Let's get these fixed then we will continue with the further review.

docs/contributing/how-to-label-an-issue.md Outdated Show resolved Hide resolved
docs/contributing/how-to-label-an-issue.md Outdated Show resolved Hide resolved
docs/contributing/how-to-label-an-issue.md Outdated Show resolved Hide resolved
docs/contributing/how-to-label-an-issue.md Outdated Show resolved Hide resolved
docs/contributing/how-to-label-an-issue.md Outdated Show resolved Hide resolved
docs/contributing/how-to-label-an-issue.md Outdated Show resolved Hide resolved
docs/contributing/how-to-label-an-issue.md Outdated Show resolved Hide resolved
docs/contributing/how-to-label-an-issue.md Outdated Show resolved Hide resolved
docs/contributing/how-to-label-an-issue.md Outdated Show resolved Hide resolved
docs/contributing/how-to-label-an-issue.md Outdated Show resolved Hide resolved
@the-coder-dude
Copy link
Author

The requested changes have been made

@arshadkazmi42
Copy link
Contributor

@prateekpardeshi you missed a couple of feedbacks and there few issues with fixes. I have added comments for all those.
Also, do not resolve the feedback reviews. Reviewer will check the fix and then resolve the feedback.
You can read more about our review process here

@arshadkazmi42
Copy link
Contributor

@the-coder-dude are you still working on this?

@the-coder-dude
Copy link
Author

@arshadkazmi42 I already made the changes back in Feb

@the-coder-dude
Copy link
Author

@arshadkazmi42 Finally all issues have been resolved successfully

@arshadkazmi42
Copy link
Contributor

@the-coder-dude 1 review is still pending. please check above for the unresolved feedbacks.

also, do not mark reviews as resolved. i will do it after cross checking the fix

@the-coder-dude
Copy link
Author

I will check ASAP

Copy link
Contributor

@arshadkazmi42 arshadkazmi42 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done with rest of the file review.
Lets get these fixed. Once these are fixed, this will be go to be merged


Ideally, every issue should have a single `type:` label applied to it. Optionally a `status:` label or other labels may also be applied.
आदर्श रूप से, हर इशू सिंगल होना चाहिए `type:` उस पर लेबल लगाया होगा। वैकल्पिक रूप से ए `status:` लेबल या अन्य लेबल भी लगाए जा सकते हैं।
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

से ए => से ek


The broad steps to labelling an issue are:
किसी इशू को लेबल करने के लिए व्यापक चरण हैं:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

व्यापक चरण -> too complex. Can we use some simple word here so it will be easy to understand


The rest of this document will describe how to choose the right labels for an issue.
इस दस्तावेज़ के बाकी का वर्णन करेगा कि किसी इशू के लिए सही लेबल कैसे चुनें।
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

वर्णन करेगा कि => वर्णन ye batayega कि


### Find an issue that you're interested in
### कोई ऐसा इशू खोजें जिसमें आपकी रुचि हो
[Gatsby के issues सूची](https://github.com/gatsbyjs/gatsby/issues) के साथ शुरू करे और तब तक स्क्रॉल करें जब तक कि आप हाल के एक को न देखें जो आपकी रुचि को प्रभावित करता है। वैकल्पिक रूप से, आप देख सकते हैं [गैर-सूचीबद्ध इशू की सूची](https://github.com/gatsbyjs/gatsby/issues?q=is%3Aopen+is%3Aissue+no%3Alabel).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

के issues सूची => के इशूज़ की सूची


### Find an issue that you're interested in
### कोई ऐसा इशू खोजें जिसमें आपकी रुचि हो
[Gatsby के issues सूची](https://github.com/gatsbyjs/gatsby/issues) के साथ शुरू करे और तब तक स्क्रॉल करें जब तक कि आप हाल के एक को न देखें जो आपकी रुचि को प्रभावित करता है। वैकल्पिक रूप से, आप देख सकते हैं [गैर-सूचीबद्ध इशू की सूची](https://github.com/gatsbyjs/gatsby/issues?q=is%3Aopen+is%3Aissue+no%3Alabel).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add a line break at line 44


- An issue describing a bug without clear steps to reproduce could be labelled with `status: needs reproduction`
- एक बग का वर्णन करने वाला एक इशू जहां बग को पुन: उत्पन्न करने के लिए कदम हैं _और_ आपने स्थानीय रूप से कोड चलाया है और त्रुटि को स्वयं लेबल किया जा सकता है। `status: confirmed`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

स्वयं लेबल किया जा सकता है। `status: confirmed`

=>

स्वयं `status: confirmed` लेबल किया जा सकता है। 


- An issue describing a bug without clear steps to reproduce could be labelled with `status: needs reproduction`
- एक बग का वर्णन करने वाला एक इशू जहां बग को पुन: उत्पन्न करने के लिए कदम हैं _और_ आपने स्थानीय रूप से कोड चलाया है और त्रुटि को स्वयं लेबल किया जा सकता है। `status: confirmed`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

त्रुटि => एरर


### Finish
और आपने कल लिया! आप इसे एक दिन कह सकते हैं या किसी अन्य इशू को लेबल करने के लिए पहले चरण पर वापस जा सकते हैं।
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

कल => कर

## Conclusion

Labelling issues is a great way to help out on the Gatsby project regardless of your experience level.
अपने अनुभव के स्तर की परवाह किए बिना Gatby परियोजना पर हेल्प करने के लिए लेबलिंग इशू एक शानदार तरीका है।
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gatby => Gatsby

## Conclusion

Labelling issues is a great way to help out on the Gatsby project regardless of your experience level.
अपने अनुभव के स्तर की परवाह किए बिना Gatby परियोजना पर हेल्प करने के लिए लेबलिंग इशू एक शानदार तरीका है।
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

परियोजना => प्रोजेक्ट

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants