-
Notifications
You must be signed in to change notification settings - Fork 174
Accessibility #279
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
Accessibility #279
Conversation
Deploy preview for tr-reactjs ready! Built with commit 8dcfce1 |
Hi @alioguzhan, |
Hi @fatmabadri You don't need to make assignments. Since we are only 2 (@yunusemredilber and I), we can manage that process internally. Thanks for your interest. |
I have one more suggestion. I think there are a lot more commits than necessary for this translation. To keep the commit history clear, It might make sense to do "Squash and Merge" at the end. What do you think @alioguzhan ? |
Yes. That makes sense. Let's squash and merge once this is ready to merge @yunusemredilber Since you are translating one document, it is better if you keep it under one commit or two (with later updates). @fatmabadri |
Hi @alioguzhan. I have asked to be enabled to add the reviewer myself when making a PR not to make an assignment or something else. This is my last translation. I am not interested to join you internally since you are only two people, managed to the end and the Turkish translation is almost done. Thank you. |
@fatmabadri I thought you were mentioning picking a user from maintainers to review this PR. I didn't think that you would want to assign yourself as a reviewer to your own Pull Request. Someone else has to be a reviewer for our own PR's. A second or third eye re-views the work that has been done and checks if this is appropriate to be merged. This is the idea about Pull Request and Review process. Thanks for your work and translation. I will review it as soon as I have some spare time. |
@alioguzhan, |
It is one document but it is a quite long one. Translations were made in the different days. Multiple commits were done in order to keep the translated part protected . @alioguzhan |
It is totally fine if this is your preferred way. As I said, we can squash and merge. No problem at all.
I see. So this brings us to my previous answer. Since we do not know who is available or not, It becomes uncertain who will be reviewing some particular PR. If the contributors would have permission to add reviewers, it would be a Sorry for the misunderstanding. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the translation. See my comments, please.
Review the suggested changes
Thanks for the translation. (Forgot to write this message earlier today) |
No description provided.