Translation of 3-maintaining.asc #38
Open
Conversation
This file contains 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
Contributor
azwarrangkuti
commented
Feb 18, 2018
azwarrangkuti
commented
- translation until line 113
- total words of the translation are 1175 words
* translation until line 113 * total words of the translation are 1175 words
baguzzzaji
requested changes
Feb 18, 2018
|
|
||
| Let's create a new repository to share our project code with. | ||
| Start by clicking the ``New repository'' button on the right-hand side of the dashboard, or from the `+` button in the top toolbar next to your username as seen in <<_new_repo_dropdown>>. | ||
| Mari kita membuat repositori baru untuk berbagi kode proyek kita dengan cara. |
There was a problem hiding this comment.
Mari kita membuat repositori baru untuk berbagi kode proyek. (cukup sampai disini bisa).
Jangan menerjemahkan word by word.
|
|
||
| .The ``new repository'' form. | ||
| image::images/newrepoform.png[The ``new repository'' form.] | ||
|
|
||
| All you really have to do here is provide a project name; the rest of the fields are completely optional. | ||
| For now, just click the ``Create Repository'' button, and boom – you have a new repository on GitHub, named `<user>/<project_name>`. | ||
| Yang harus Anda lakukan di sini adalah memberikan nama proyek; sisa field yang lain sepenuhnya pilihan. |
There was a problem hiding this comment.
optional sepertinya lebih baik jika menjadi tambahan
|
|
||
| Click the ``Settings'' link at the bottom of the right-hand sidebar. | ||
| Klik tautan ``Settings''di bagian bawah sidebar kanan. |
|
|
||
| .Repository collaborators. | ||
| image::images/collaborators.png[The repository collaborators box.] | ||
|
|
||
| ==== Managing Pull Requests | ||
| ==== Mnegelola Pull Requests |
|
|
||
| Now that you have a project with some code in it and maybe even a few collaborators who also have push access, let's go over what to do when you get a Pull Request yourself. | ||
| Sekarang setelah Anda memiliki sebuah proyek dengan beberapa kode di dalamnya dan mungkin bahkan beberapa kolaborator yang juga memiliki akses push, mari kita membahas apa yang harus dilakukan saat Anda mendapatkan Pull Request sendiri. |
There was a problem hiding this comment.
Cukup sampai Request. Kata sendirinya bisa dihapus. Sekali lagi, tidak perlu menerjemahkan word by word.
|
|
||
| [[_email_pr]] | ||
| .Email notification of a new Pull Request. | ||
| image::images/maint-01-email.png[Pull Request email notification] | ||
|
|
||
| There are a few things to notice about this email. It will give you a small diffstat -- a list of files that have changed in the Pull Request and by how much. It gives you a link to the Pull Request on GitHub. It also gives you a few URLs that you can use from the command line. | ||
| Ada beberapa hal yang harus diperhatikan mengenai surel ini. Ini akan memberi Anda diffstat kecil -- daftar berkas yang telah berubah dalam Pull Request dan seberapa banyak. Ini memberi Anda tautan ke Pull Request pada GitHub. Ini juga memberikan Anda beberapa URL yang dapat Anda gunakan dari baris perintah. |
There was a problem hiding this comment.
small diffstat bisa diartinya diffstat pendek (karena teks).
" -- sebuah daftar berkas yang telah berubah dan seberapa banyak berubahnya di Pull Request tersebut."
Terjemahkan tidak harus mengikuti word by word dari kata bahasa inggrisnya.
|
|
||
| If you notice the line that says `git pull <url> patch-1`, this is a simple way to merge in a remote branch without having to add a remote. We went over this quickly in <<_checking_out_remotes>>. If you wish, you can create and switch to a topic branch and then run this command to merge in the Pull Request changes. | ||
| Jika Anda melihat baris yang mengatakan `git pull <url> patch-1`, ini adalah cara mudah untuk melakukan merge branch remote tanpa harus menambahkan remote. Kami membahasnya dengan cepat di <<_checking_out_remotes>>. Jika Anda mau, Anda dapat membuat dan beralih ke branch topik dan kemudian menjalankan perintah ini untuk di-merge-kan dalam perubahan Pull Request. |
There was a problem hiding this comment.
We di sini adalah kita. Kita mengajak pembaca melakukan apa yang akan dilakukan.
|
|
||
| If the merge is trivial, you can also just hit the ``Merge'' buton on the GitHub site. This will do a ``non-fast-forward'' merge, creating a merge commit even if a fast-forward merge was possible. This means that no matter what, every time you hit the merge button, a merge commit is created. As you can see in <<_merge_button>>, GitHub gives you all of this information if you click the hint link. | ||
| Jika ingin merge itu lebih mudah, Anda juga bisa menekan tombol ``Merge'' di situs GitHub. Ini akan melakukan merge ``non-fast-forward'', membuat commit merge bahkan jika merge cepat mungkin diteruskan. Ini berarti dalam keadaan apapun, setiap kali Anda menekan tombol merge, sebuah commit merge dibuat. Seperti yang bisa Anda lihat di <<_merge_button>>, GitHub memberi Anda semua informasi ini jika Anda mengklik tautan petunjuknya. |
There was a problem hiding this comment.
Tolong kalimat pertamanya disusun ulang.
|
|
||
| [[_pr_refs]] | ||
| ===== Pull Request Refs | ||
|
|
||
| If you're dealing with a *lot* of Pull Requests and don't want to add a bunch of remotes or do one time pulls every time, there is a neat trick that GitHub allows you to do. This is a bit of an advanced trick and we'll go over the details of this a bit more in <<_refspec>>, but it can be pretty useful. | ||
| Jika Anda berurusan dengan *banyak* Pull Request dan tidak ingin menambahkan sekumpulan remote atau satu kali melakukan pull setiap saat, ada trik bagus yang memungkinkan GitHub Anda lakukan. Ini adalah sedikit trik canggih dan kita akan membahas rincian ini lebih banyak di <<_refspec>>, tapi ini bisa sangat berguna. |
There was a problem hiding this comment.
Kalimatnya disusun lagi.
|
|
||
| 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. | ||
| GitHub benar-benar mengiklankan branch Pull Request untuk repositori sebagai sejenis branch-pseudo di server. Secara default Anda tidak mendapatkannya ketika Anda mengkloning, tapi mereka berada di sana dengan cara yang tidak jelas dan Anda dapat mengaksesnya dengan mudah. |
There was a problem hiding this comment.
pseudo-branch biarkan saja seperti itu
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.