-
Notifications
You must be signed in to change notification settings - Fork 19
TL Localization - Chapter 6, section 3 - part 1 (1,992 words) #45
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
Conversation
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.
Great quality translations @heywens . I have only suggested minor changes on your work. Good job.
=== Pagpapanatili ng isang Proyekto | ||
|
||
Now that we're comfortable contributing to a project, let's look at the other side: creating, maintaining and administering your own project. | ||
Ngayon na kumportable tayo na nag-aambag sa isang proyekto, tingnan natin ang kabilang panig: paglikha, pagpapanatili at pangangasiwa ng iyong sariling proyekto. |
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.
tayo na
could be shortened to tayong
.The ``new repository'' form. | ||
image::images/newrepoform.png[The ``new repository'' form.] | ||
.Ang form ng ``bagong repositoryo''. | ||
image::images/newrepoform.png[The ``new repositoryo'' form.] |
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.
new
to bagong
If you're working with other people who you want to give commit access to, you need to add them as ``collaborators''. | ||
If Ben, Jeff, and Louise all sign up for accounts on GitHub, and you want to give them push access to your repository, you can add them to your project. | ||
Doing so will give them ``push'' access, which means they have both read and write access to the project and Git repository. | ||
Kung ikaw ay nagtatrabaho kasama ang ibang tao nga nais mong bigyan ng access sa pag-commit, kailangan mong idagdag sila bilang ``tagapangasiwa''. |
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.
nga
to na
Doing so will give them ``push'' access, which means they have both read and write access to the project and Git repository. | ||
Kung ikaw ay nagtatrabaho kasama ang ibang tao nga nais mong bigyan ng access sa pag-commit, kailangan mong idagdag sila bilang ``tagapangasiwa''. | ||
Kung si Ben, Jeff, and Louise ay nag-sign up ng mga account sa GitHub, at gusto mo silang bigyan ng access sa pag-push sa iyong repositoryo, maaari mo silang idagdag sa iyong proyekto. | ||
Paggawa nito ay nagbibigay sa kanila ng access sa ``push'', na nangangahulugan na mayroon silang access sa pagbasa at pagsulat sa proyekto at repositoryo ng Git. |
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.
- you could change
Paggawa
toAng paggawa
- spacing between
at
andrepositoryo
.The repository settings link. | ||
image::images/reposettingslink.png[The repository settings link.] | ||
.Ang link ng settings ng repositoryo. | ||
image::images/reposettingslink.png[The repositoryo settings link.] |
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.
[Ang link ng settings ng repositoryo.]
.Repository collaborators. | ||
image::images/collaborators.png[The repository collaborators box.] | ||
.Repository tagapangasiwa. | ||
image::images/tagapangasiwa.png[The repositoryo tagapangasiwa box.] |
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.
I think this needs to be translated The repositoryo tagapangasiwa box.
|
||
As we covered in <<_github#_github_flow>>, you can now have a conversation with the person who opened the Pull Request. | ||
You can comment on specific lines of code, comment on whole commits or comment on the entire Pull Request itself, using GitHub Flavored Markdown everywhere. | ||
Sa natalakay sa <<_github#_github_flow>>, maaari ka na ngayong magkaroon ng pag-uusap sa taong nagbukas Kahilingan na Pull. |
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.
taong nagbukas ng Kahilingan na Pull
|
||
GitHub actually advertises the Pull Request branches for a repository as sort of pseudo-branches on the server. | ||
By default you don't get them when you clone, but they are there in an obscured way and you can access them pretty easily. | ||
Ang GitHub ay tunay na nag-aanunsiyo ng mga branch ng Kahilingan na Pull para sa isang repositoryo bilang uri ng mga pseudo-branch sa server.Bilang default hindi mo makuha ang mga ito kapag ikaw ay nag-clone, ngunit doon sila sa isang nakakubling paraan at maaari mong madling ma-access ang mga ito. |
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.
- space between
server.
andBilang
madaling
Ito ay nagsasabi sa Git, ``Kumonekta sa remote na `origin`, at i-download ang ref na pinangalanang `refs/pull/958/head`.'' | ||
Masayang sinusunod ng Git, at nagda-download ng lahat na kinakailangan mo sa pagbuo ng ref na iyon, at naglalagay ng isang pointer sa commit na gusto mo sa ilalim ng `.git/FETCH_HEAD`. | ||
Maaari mong sundan iyon ng `git merge FETCH_HEAD` sa branch na gusto mong suriin, ngunit ang mensahe ng merge commit ay | ||
you want to test it in, but that merge commit ay magiging mukhang kakaiba. |
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.
remove untranslated line you want to test it in, but that merge commit
Ang linyang iyon na nagsisimula sa `fetch =` ay isang ``refspec.'' | ||
Ito'y isang paraan ng pagmamapa ng mga pangalan sa remote sa mga pangalan sa iyong lokal na direktoryo na `.git`. | ||
Ang partikular na ito ay nagsasabi sa Git, "ang mga bagay sa remote na nasa ilalim ng `refs/heads` ay dapat mapunta sa aking lokal na repositoryo sa ilalim ng `refs/remotes/origin`." | ||
Maaari mo mabago ang seksiyon na ito upang magdagdag ng iba pang refspec: |
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.
Maaari mong
.Repository collaborators. | ||
image::images/collaborators.png[The repository collaborators box.] | ||
.Tagapangasiwa ng Repositoryo. | ||
image::images/tagapangasiwa.png[Ang kahon ng tagapangasiwa ng repositoryo.] |
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.
@heywens was the translation of the image file really intended? This .png
does not exist...
In progit2-tl/progit2#45, a reference to an image was changed, without renaming the referenced file accordingly. This leads to a broken link as can be seen in figure 114 at https://git-scm.com/book/tl/v2/GitHub-Pagpapanatili-ng-isang-Proyekto Work around this by forcing the reference back. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
In progit2-tl/progit2#45, a reference to an image was changed, without renaming the referenced file accordingly. This leads to a broken link as can be seen in figure 114 at https://git-scm.com/book/tl/v2/GitHub-Pagpapanatili-ng-isang-Proyekto Work around this by forcing the reference back. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
In progit2-tl/progit2#45, a reference to an image was changed, without renaming the referenced file accordingly. This leads to a broken link as can be seen in figure 114 at https://git-scm.com/book/tl/v2/GitHub-Pagpapanatili-ng-isang-Proyekto Work around this by forcing the reference back. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
In progit2-tl/progit2#45, a reference to an image was changed, without renaming the referenced file accordingly. This leads to a broken link as can be seen in figure 114 at https://git-scm.com/book/tl/v2/GitHub-Pagpapanatili-ng-isang-Proyekto Work around this by forcing the reference back. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
In progit2-tl/progit2#45, a reference to an image was changed, without renaming the referenced file accordingly. This leads to a broken link as can be seen in figure 114 at https://git-scm.com/book/tl/v2/GitHub-Pagpapanatili-ng-isang-Proyekto Work around this by forcing the reference back. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
In progit2-tl/progit2#45, a reference to an image was changed, without renaming the referenced file accordingly. This leads to a broken link as can be seen in figure 114 at https://git-scm.com/book/tl/v2/GitHub-Pagpapanatili-ng-isang-Proyekto Work around this by forcing the reference back. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
In progit2-tl/progit2#45, a reference to an image was changed, without renaming the referenced file accordingly. This leads to a broken link as can be seen in figure 114 at https://git-scm.com/book/tl/v2/GitHub-Pagpapanatili-ng-isang-Proyekto Work around this by forcing the reference back. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
In progit2-tl/progit2#45, a reference to an image was changed, without renaming the referenced file accordingly. This leads to a broken link as can be seen in figure 114 at https://git-scm.com/book/tl/v2/GitHub-Pagpapanatili-ng-isang-Proyekto Work around this by forcing the reference back. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
In progit2-tl/progit2#45, a reference to an image was changed, without renaming the referenced file accordingly. This leads to a broken link as can be seen in figure 114 at https://git-scm.com/book/tl/v2/GitHub-Pagpapanatili-ng-isang-Proyekto Work around this by forcing the reference back. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
In progit2-tl/progit2#45, a reference to an image was changed, without renaming the referenced file accordingly. This leads to a broken link as can be seen in figure 114 at https://git-scm.com/book/tl/v2/GitHub-Pagpapanatili-ng-isang-Proyekto Work around this by forcing the reference back. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
In progit2-tl/progit2#45, a reference to an image was changed, without renaming the referenced file accordingly. This leads to a broken link as can be seen in figure 114 at https://git-scm.com/book/tl/v2/GitHub-Pagpapanatili-ng-isang-Proyekto Work around this by forcing the reference back. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
In progit2-tl/progit2#45, a reference to an image was changed, without renaming the referenced file accordingly. This leads to a broken link as can be seen in figure 114 at https://git-scm.com/book/tl/v2/GitHub-Pagpapanatili-ng-isang-Proyekto Work around this by forcing the reference back. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
In progit2-tl/progit2#45, a reference to an image was changed, without renaming the referenced file accordingly. This leads to a broken link as can be seen in figure 114 at https://git-scm.com/book/tl/v2/GitHub-Pagpapanatili-ng-isang-Proyekto Work around this by forcing the reference back. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
In progit2-tl/progit2#45, a reference to an image was changed, without renaming the referenced file accordingly. This leads to a broken link as can be seen in figure 114 at https://git-scm.com/book/tl/v2/GitHub-Pagpapanatili-ng-isang-Proyekto Work around this by forcing the reference back. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
In progit2-tl/progit2#45, a reference to an image was changed, without renaming the referenced file accordingly. This leads to a broken link as can be seen in figure 114 at https://git-scm.com/book/tl/v2/GitHub-Pagpapanatili-ng-isang-Proyekto Work around this by forcing the reference back. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
In progit2-tl/progit2#45, a reference to an image was changed, without renaming the referenced file accordingly. This leads to a broken link as can be seen in figure 114 at https://git-scm.com/book/tl/v2/GitHub-Pagpapanatili-ng-isang-Proyekto Work around this by forcing the reference back. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
In progit2-tl/progit2#45, a reference to an image was changed, without renaming the referenced file accordingly. This leads to a broken link as can be seen in figure 114 at https://git-scm.com/book/tl/v2/GitHub-Pagpapanatili-ng-isang-Proyekto Work around this by forcing the reference back. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
In progit2-tl/progit2#45, a reference to an image was changed, without renaming the referenced file accordingly. This leads to a broken link as can be seen in figure 114 at https://git-scm.com/book/tl/v2/GitHub-Pagpapanatili-ng-isang-Proyekto Work around this by forcing the reference back. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
In progit2-tl/progit2#45, a reference to an image was changed, without renaming the referenced file accordingly. This leads to a broken link as can be seen in figure 114 at https://git-scm.com/book/tl/v2/GitHub-Pagpapanatili-ng-isang-Proyekto Work around this by forcing the reference back. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
In progit2-tl/progit2#45, a reference to an image was changed, without renaming the referenced file accordingly. This leads to a broken link as can be seen in figure 114 at https://git-scm.com/book/tl/v2/GitHub-Pagpapanatili-ng-isang-Proyekto Work around this by forcing the reference back. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
No description provided.