TL Localization - Chapter 6, section 3 - part 2 (1,599 words) #52
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mind-blast
reviewed
Feb 16, 2018
|
|
||
| When you go to open a Pull Request, there is a box at the top of the page that specifies which branch you're requesting to pull to and which you're requesting to pull from. | ||
| If you hit the ``Edit'' button at the right of that box you can change not only the branches but also which fork. | ||
| Kapag ikaw ay nagbubukas ng isang Kahilingan na Pull, may isang kahon sa itaas ng pahina na tumutukoy kung aling branch ang hinihingan mo na maka-pull at kung saan hinihiling mo na mag-pull. |
There was a problem hiding this comment.
Kapag ikaw ay nagbubukas to Kapag ikaw ay pumunta upang bumukas ng
mind-blast
reviewed
Feb 16, 2018
| When you go to open a Pull Request, there is a box at the top of the page that specifies which branch you're requesting to pull to and which you're requesting to pull from. | ||
| If you hit the ``Edit'' button at the right of that box you can change not only the branches but also which fork. | ||
| Kapag ikaw ay nagbubukas ng isang Kahilingan na Pull, may isang kahon sa itaas ng pahina na tumutukoy kung aling branch ang hinihingan mo na maka-pull at kung saan hinihiling mo na mag-pull. | ||
| Kung pindutin mo ang ``Edit'' na pindutan sa kanan ng kahon na iyon, maaari kang magbago hindi lamang sa mga branch kundi rin sa kung anong fork. |
There was a problem hiding this comment.
Kung pindutin mo ang to Kung pinindot mo ang
mind-blast
reviewed
Feb 16, 2018
| [[_pr_targets]] | ||
| .Manually change the Pull Request target fork and branch. | ||
| image::images/maint-04-target.png[PR targets] | ||
| .Baguhin nang mano-mano ang fork na target ng Kahilingan na Pull at branch. |
There was a problem hiding this comment.
Baguhin nang mano-mano ang fork na target ng Kahilingan na Pull at branch. to Mano-manong baguhin ang Kahilingan ng Pull na target ang fork at branch
mind-blast
reviewed
Feb 16, 2018
| Dito maaari kang medyo madaling magtukoy upang pagsamahin ang iyong bagong branch sa ibang Kahilingan na Pull o ibang fork ng proyekto. | ||
|
|
||
| ==== Mentions and Notifications | ||
| ==== Mga Pagbanggit at Abiso |
mind-blast
reviewed
Feb 16, 2018
| ==== Mga Pagbanggit at Abiso | ||
|
|
||
| GitHub also has a pretty nice notifications system built in that can come in handy when you have questions or need feedback from specific individuals or teams. | ||
| Mayroon ding magandang built on na sistema ng mga abiso ang GitHub na magagamit kapag ikaw ay may mga tanong o kailangan na katugunan mula sa tiyak na mga indibidwal o koponan. |
mind-blast
reviewed
Feb 16, 2018
| Mayroon ding magandang built on na sistema ng mga abiso ang GitHub na magagamit kapag ikaw ay may mga tanong o kailangan na katugunan mula sa tiyak na mga indibidwal o koponan. | ||
|
|
||
| In any comment you can start typing a `@` character and it will begin to autocomplete with the names and usernames of people who are collaborators or contributors in the project. | ||
| Sa anumang komento maaari mong simulan sa pagtitipa ng karakter na `@` at ito ay magsisimula sa autocomplete kasabay ng mga pangalan at username ng tao na mga tagatulong o nag-aambag sa proyekto. |
There was a problem hiding this comment.
change autocomplete to awtomatikong matapos
mind-blast
reviewed
Feb 16, 2018
|
|
||
| .Start typing @ to mention someone. | ||
| image::images/maint-05-mentions.png[Mentions] | ||
| .Simulang magtipa ng @ upang banggitin ang isang tao. |
There was a problem hiding this comment.
change Simulang magtipa ng to Simulan ang pag-type
mind-blast
reviewed
Feb 16, 2018
| Once you post a comment with a user mention, that user will be notified. | ||
| This means that this can be a really effective way of pulling people into conversations rather than making them poll. | ||
| Very often in Pull Requests on GitHub people will pull in other people on their teams or in their company to review an Issue or Pull Request. | ||
| Sa sandaling magpaskil ka ng komento sa isang pagbanggit ng user, aabisuhan ang user na iyon. |
mind-blast
reviewed
Feb 16, 2018
| If you no longer wish to receive notifications, there is an ``Unsubscribe'' button on the page you can click to stop receiving updates on it. | ||
| Kung may isang tao ang nakuhang nabanggit sa isang Kahilingan na Pull o Isyu, sila ay magiging ``naka-subscribe'' nito at patuloy na makakakuha ng mga abiso sa anumang oras na nangyayari ang aktibidad nito. | ||
| Ma-subscribe ka rin sa isang bagay kung binuksan mo ito, kung nanonood ka sa repositoryo o kung ikaw ay nagkomento ka sa isang bagay. | ||
| Kung hindi mo na nais na makatanggap ng mga abiso, may isang pindutan na ``Unsubscribe'' sa pahina na maaari mong i-click upang ihinto ang pagtanggap ng mga update nito. |
mind-blast
reviewed
Feb 16, 2018
| Ang mga email ay ma-thread din nang mabuti, na maganda kung ika'y gumagamit ng isang kliyente ng pag-thread ng email. | ||
|
|
||
| There is also a fair amount of metadata embedded in the headers of the emails that GitHub sends you, which can be really helpful for setting up custom filters and rules. | ||
| Mayroon ding isang makatarungang dami ng metadata na naka-embed sa mga header ng mga email na ipinadala sa iyo ng GitHub, na maaaring maging kapaki-pakinabang para sa pag-set up ng mga pasadyang filter at patakaran. |
mind-blast
reviewed
Feb 16, 2018
| The first is the `README` file, which can be of nearly any format that GitHub recognizes as prose. | ||
| For example, it could be `README`, `README.md`, `README.asciidoc`, etc. | ||
| If GitHub sees a README file in your source, it will render it on the landing page of the project. | ||
| Ang una ay ang file na `README`, na maaaring maging halos sa anumang format na nakikilala ng GitHub bilang prosa. |
There was a problem hiding this comment.
hi sir @Robin-Ho, prose can also be translated to prosa.
references:
|
Please change suggested words . Thank you. |
|
Hi Sir @Robin-Ho, changes have been applied. Few suggestions were not applied though.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.