From 56a4bfa3d5125912c6ecec296ffe7d1acc1f96bc Mon Sep 17 00:00:00 2001 From: Roshan Jossy Date: Tue, 22 Nov 2022 01:05:15 +0100 Subject: [PATCH] reset repo --- .github/CONTRIBUTING.md | 86 +++ .github/ISSUE_TEMPLATE.md | 20 + .github/ISSUE_TEMPLATE/issue-template.md | 30 + .gitignore | 390 ++++++++++++ CODE_OF_CONDUCT.md | 133 ++++ Contributors.md | 572 ++++++++++++++++++ LICENSE | 21 + README.md | 207 +++++++ .../Things a non Programmer can do.md | 117 ++++ .../Useful-links-for-further-learning.md | 45 ++ .../additional-material.md | 50 ++ .../amending-a-commit.md | 48 ++ .../check-commit-log.md | 20 + .../git_workflow_scenarios/configuring-git.md | 76 +++ .../creating-a-gitignore-file.md | 73 +++ .../delete-branch-locally.md | 19 + .../git_workflow_scenarios/gitflow.md | 119 ++++ ...g-your-fork-synced-with-this-repository.md | 45 ++ .../moving-a-commit-to-a-different-branch.md | 25 + .../git_workflow_scenarios/removing-a-file.md | 23 + .../removing-branch-from-your-repository.md | 31 + .../resetting-a-branch.md | 18 + .../resetting-a-commit.md | 20 + .../resolving-merge-conflicts.md | 35 ++ .../reverting-a-commit.md | 41 ++ .../squashing-commits.md | 86 +++ .../git_workflow_scenarios/stashing-a-file.md | 137 +++++ .../undoing-a-commit.md | 55 ++ .../why-using-branches.md | 53 ++ .../Useful-links-for-further-learning.by.md | 36 ++ .../Belarusian/additional-material.by.md | 46 ++ .../Belarusian/amending-a-commit.by.md | 46 ++ .../Belarusian/configuring-git.by.md | 76 +++ ...our-fork-synced-with-this-repository.by.md | 42 ++ ...oving-a-commit-to-a-different-branch.by.md | 25 + .../Belarusian/removing-a-file.by.md | 23 + ...removing-branch-from-your-repository.by.md | 31 + .../resolving-merge-conflicts.by.md | 33 + .../Belarusian/reverting-a-commit.by.md | 40 ++ .../Belarusian/squashing-commits.by.md | 86 +++ .../Belarusian/stashing-a-file.by.md | 137 +++++ .../Belarusian/undoing-a-commit.by.md | 59 ++ .../Chinese/addtional-material.cht.md | 46 ++ .../French/additional-material.fr.md | 49 ++ .../French/amending-a-commit.fr.md | 52 ++ ...oving-a-commit-to-a-different-branch.hi.md | 25 + .../translations/Hindi/nepali.np.md | 25 + .../translations/Hindi/removing-a-file.hi.md | 20 + ...removing-branch-from-your-repository.hi.md | 31 + .../Indonesian/additional-material.id.md | 46 ++ .../Indonesian/removing-a-file.id.md | 23 + .../Italian/removing-a-file.it.md | 23 + .../Korean/additional-material.ko.md | 42 ++ .../Korean/amending-a-commit.ko.md | 46 ++ ...our-fork-synced-with-this-repository.ko.md | 41 ++ ...oving-a-commit-to-a-different-branch.ko.md | 28 + ...removing-branch-from-your-repository.ko.md | 30 + .../Korean/resolving-merge-conflicts.ko.md | 43 ++ .../Korean/reverting-a-commit.ko.md | 35 ++ .../Korean/undoing-a-commit.ko.md | 59 ++ .../Portuguese/additional-material.pt_br.md | 46 ++ .../Portuguese/amending-a-commit.pt_br.md | 52 ++ .../Portuguese/confinguring-git.pt-br.md | 73 +++ ...-fork-synced-with-this-repository.pt_br.md | 40 ++ ...ng-a-commit-to-a-different-branch.pt_br.md | 25 + .../Portuguese/removing-a-file.pt_br.md | 24 + ...oving-branch-from-your-repository.pt_br.md | 31 + .../Russian/additional-material.ru.md | 46 ++ .../Russian/amending-a-commit.ru.md | 45 ++ .../Russian/configuring-git.ru.md | 76 +++ ...oving-a-commit-to-a-different-branch.ru.md | 25 + .../Russian/removing-a-file.ru.md | 23 + .../Slovenian/additional-material.sl.md | 46 ++ .../Slovenian/amending-a-commit.sl.md | 48 ++ .../Slovenian/configuring-git.sl.md | 77 +++ ...our-fork-synced-with-this-repository.sl.md | 40 ++ ...oving-a-commit-to-a-different-branch.sl.md | 24 + .../Slovenian/removing-a-file.sl.md | 23 + ...removing-branch-from-your-repository.sl.md | 30 + .../Slovenian/resolving-merge-conflicts.sl.md | 34 ++ .../Slovenian/reverting-a-commit.sl.md | 38 ++ .../Slovenian/squashing-commits.sl.md | 94 +++ .../Slovenian/stashing-a-file.sl.md | 136 +++++ .../Slovenian/undoing-a-commit.sl.md | 55 ++ .../Ukrainian/removing-a-file.ua.md | 23 + .../Urdu/additional-material.ur.md | 46 ++ .../translations/Urdu/amending-a-commit.ur.md | 51 ++ .../Useful-links-for-further-learning.id.md | 45 ++ .../resolving-merge-conflicts.vi.md | 33 + .../translations/additional-material.np.md | 48 ++ .../translations/amending-a-commit.np.md | 50 ++ .../translations/configuring-git.np.md | 77 +++ .../translations/delete-branch-locally.fa.md | 19 + .../git-bash-windows-tutorial.md | 129 ++++ cli-tool-tutorials/github-cli-tutorial.md | 101 ++++ .../github-desktop-old-version-tutorial.md | 108 ++++ gui-tool-tutorials/github-desktop-tutorial.md | 119 ++++ .../github-windows-intellij-tutorial.md | 112 ++++ .../github-windows-vs-code-tutorial.md | 118 ++++ .../github-windows-vs2017-tutorial.md | 140 +++++ gui-tool-tutorials/gitkraken-tutorial.md | 123 ++++ .../sourcetree-macos-tutorial.md | 139 +++++ gui-tool-tutorials/sublime-merge-tutorial.md | 121 ++++ .../github-desktop-tutorial.ng_yr.md | 106 ++++ .../github-desktop-tutorial.pt_br.md | 119 ++++ .../github-windows-intellij-tutorial.pt_br.md | 126 ++++ .../github-windows-vs-code-tutorial-hi.md | 116 ++++ .../github-windows-vs-code-tutorial.pt_br.md | 117 ++++ .../github-windows-vs-code-tutorial_id.md | 121 ++++ .../github-windows-vs-code-tutorial_pt_br.md | 124 ++++ .../github-windows-vs2017-tutorial.pt_br.md | 149 +++++ .../translations/gitkraken-tutorial.pt-br.md | 126 ++++ translations/README.afk.md | 129 ++++ translations/README.al.md | 127 ++++ translations/README.am.md | 124 ++++ translations/README.ar.md | 179 ++++++ translations/README.aze.md | 116 ++++ translations/README.bg.md | 124 ++++ translations/README.bih.md | 124 ++++ translations/README.bn.md | 122 ++++ translations/README.by.md | 151 +++++ translations/README.ca.md | 122 ++++ translations/README.cs.md | 127 ++++ translations/README.da.md | 123 ++++ translations/README.de.md | 114 ++++ translations/README.eg.md | 154 +++++ translations/README.en-pirate.md | 130 ++++ translations/README.es.md | 121 ++++ translations/README.fa.md | 107 ++++ translations/README.fi.md | 129 ++++ translations/README.fr.md | 142 +++++ translations/README.ge.md | 123 ++++ translations/README.gl.md | 107 ++++ translations/README.gr.md | 128 ++++ translations/README.guj.md | 143 +++++ translations/README.hau.md | 134 ++++ translations/README.hb.md | 216 +++++++ translations/README.hi.md | 125 ++++ translations/README.hne.md | 124 ++++ translations/README.hr.md | 124 ++++ translations/README.hu.md | 124 ++++ translations/README.hy.md | 136 +++++ translations/README.id.md | 139 +++++ translations/README.igb.md | 128 ++++ translations/README.it.md | 117 ++++ translations/README.ja.md | 116 ++++ translations/README.ka.md | 89 +++ translations/README.ko.md | 134 ++++ translations/README.kws.md | 134 ++++ translations/README.kz.md | 109 ++++ translations/README.la.md | 119 ++++ translations/README.lt.md | 110 ++++ translations/README.lv.md | 123 ++++ translations/README.me.md | 129 ++++ translations/README.mk.md | 124 ++++ translations/README.ml.md | 131 ++++ translations/README.mm_unicode.md | 195 ++++++ translations/README.mr.md | 131 ++++ translations/README.mx.md | 124 ++++ translations/README.my.md | 121 ++++ translations/README.nl.md | 162 +++++ translations/README.no.md | 129 ++++ translations/README.np.md | 117 ++++ translations/README.pb.md | 117 ++++ translations/README.pl.md | 124 ++++ translations/README.ps.md | 142 +++++ translations/README.pt-pt.md | 105 ++++ translations/README.pt_br.md | 124 ++++ translations/README.pus.md | 109 ++++ translations/README.ro.md | 112 ++++ translations/README.ru.md | 174 ++++++ translations/README.se.md | 123 ++++ translations/README.si.md | 130 ++++ translations/README.sindhi.md | 132 ++++ translations/README.sk.md | 125 ++++ translations/README.sl.md | 121 ++++ translations/README.slk.md | 121 ++++ translations/README.sr.md | 118 ++++ translations/README.ta.md | 143 +++++ translations/README.te.md | 119 ++++ translations/README.th.md | 119 ++++ translations/README.tl.md | 124 ++++ translations/README.tr.md | 134 ++++ translations/README.ua.md | 138 +++++ translations/README.un-aln.md | 129 ++++ translations/README.ur.md | 151 +++++ translations/README.uz.md | 139 +++++ translations/README.vn.md | 123 ++++ translations/README.yor.md | 129 ++++ translations/README.zh-cn.md | 113 ++++ translations/README.zh-tw.md | 115 ++++ translations/README.zul.md | 133 ++++ translations/Translations.md | 74 +++ 193 files changed, 18186 insertions(+) create mode 100644 .github/CONTRIBUTING.md create mode 100644 .github/ISSUE_TEMPLATE.md create mode 100644 .github/ISSUE_TEMPLATE/issue-template.md create mode 100644 .gitignore create mode 100644 CODE_OF_CONDUCT.md create mode 100644 Contributors.md create mode 100644 LICENSE create mode 100644 README.md create mode 100644 additional-material/Things a non Programmer can do.md create mode 100644 additional-material/git_workflow_scenarios/Useful-links-for-further-learning.md create mode 100644 additional-material/git_workflow_scenarios/additional-material.md create mode 100644 additional-material/git_workflow_scenarios/amending-a-commit.md create mode 100644 additional-material/git_workflow_scenarios/check-commit-log.md create mode 100644 additional-material/git_workflow_scenarios/configuring-git.md create mode 100644 additional-material/git_workflow_scenarios/creating-a-gitignore-file.md create mode 100644 additional-material/git_workflow_scenarios/delete-branch-locally.md create mode 100644 additional-material/git_workflow_scenarios/gitflow.md create mode 100644 additional-material/git_workflow_scenarios/keeping-your-fork-synced-with-this-repository.md create mode 100644 additional-material/git_workflow_scenarios/moving-a-commit-to-a-different-branch.md create mode 100644 additional-material/git_workflow_scenarios/removing-a-file.md create mode 100644 additional-material/git_workflow_scenarios/removing-branch-from-your-repository.md create mode 100644 additional-material/git_workflow_scenarios/resetting-a-branch.md create mode 100644 additional-material/git_workflow_scenarios/resetting-a-commit.md create mode 100644 additional-material/git_workflow_scenarios/resolving-merge-conflicts.md create mode 100644 additional-material/git_workflow_scenarios/reverting-a-commit.md create mode 100644 additional-material/git_workflow_scenarios/squashing-commits.md create mode 100644 additional-material/git_workflow_scenarios/stashing-a-file.md create mode 100644 additional-material/git_workflow_scenarios/undoing-a-commit.md create mode 100644 additional-material/git_workflow_scenarios/why-using-branches.md create mode 100644 additional-material/translations/Belarusian/Useful-links-for-further-learning.by.md create mode 100644 additional-material/translations/Belarusian/additional-material.by.md create mode 100644 additional-material/translations/Belarusian/amending-a-commit.by.md create mode 100644 additional-material/translations/Belarusian/configuring-git.by.md create mode 100644 additional-material/translations/Belarusian/keeping-your-fork-synced-with-this-repository.by.md create mode 100644 additional-material/translations/Belarusian/moving-a-commit-to-a-different-branch.by.md create mode 100644 additional-material/translations/Belarusian/removing-a-file.by.md create mode 100644 additional-material/translations/Belarusian/removing-branch-from-your-repository.by.md create mode 100644 additional-material/translations/Belarusian/resolving-merge-conflicts.by.md create mode 100644 additional-material/translations/Belarusian/reverting-a-commit.by.md create mode 100644 additional-material/translations/Belarusian/squashing-commits.by.md create mode 100644 additional-material/translations/Belarusian/stashing-a-file.by.md create mode 100644 additional-material/translations/Belarusian/undoing-a-commit.by.md create mode 100644 additional-material/translations/Chinese/addtional-material.cht.md create mode 100644 additional-material/translations/French/additional-material.fr.md create mode 100644 additional-material/translations/French/amending-a-commit.fr.md create mode 100644 additional-material/translations/Hindi/moving-a-commit-to-a-different-branch.hi.md create mode 100644 additional-material/translations/Hindi/nepali.np.md create mode 100644 additional-material/translations/Hindi/removing-a-file.hi.md create mode 100644 additional-material/translations/Hindi/removing-branch-from-your-repository.hi.md create mode 100644 additional-material/translations/Indonesian/additional-material.id.md create mode 100644 additional-material/translations/Indonesian/removing-a-file.id.md create mode 100644 additional-material/translations/Italian/removing-a-file.it.md create mode 100644 additional-material/translations/Korean/additional-material.ko.md create mode 100644 additional-material/translations/Korean/amending-a-commit.ko.md create mode 100644 additional-material/translations/Korean/keeping-your-fork-synced-with-this-repository.ko.md create mode 100644 additional-material/translations/Korean/moving-a-commit-to-a-different-branch.ko.md create mode 100644 additional-material/translations/Korean/removing-branch-from-your-repository.ko.md create mode 100644 additional-material/translations/Korean/resolving-merge-conflicts.ko.md create mode 100644 additional-material/translations/Korean/reverting-a-commit.ko.md create mode 100644 additional-material/translations/Korean/undoing-a-commit.ko.md create mode 100644 additional-material/translations/Portuguese/additional-material.pt_br.md create mode 100644 additional-material/translations/Portuguese/amending-a-commit.pt_br.md create mode 100644 additional-material/translations/Portuguese/confinguring-git.pt-br.md create mode 100644 additional-material/translations/Portuguese/keeping-your-fork-synced-with-this-repository.pt_br.md create mode 100644 additional-material/translations/Portuguese/moving-a-commit-to-a-different-branch.pt_br.md create mode 100644 additional-material/translations/Portuguese/removing-a-file.pt_br.md create mode 100644 additional-material/translations/Portuguese/removing-branch-from-your-repository.pt_br.md create mode 100644 additional-material/translations/Russian/additional-material.ru.md create mode 100644 additional-material/translations/Russian/amending-a-commit.ru.md create mode 100644 additional-material/translations/Russian/configuring-git.ru.md create mode 100644 additional-material/translations/Russian/moving-a-commit-to-a-different-branch.ru.md create mode 100644 additional-material/translations/Russian/removing-a-file.ru.md create mode 100644 additional-material/translations/Slovenian/additional-material.sl.md create mode 100644 additional-material/translations/Slovenian/amending-a-commit.sl.md create mode 100644 additional-material/translations/Slovenian/configuring-git.sl.md create mode 100644 additional-material/translations/Slovenian/keeping-your-fork-synced-with-this-repository.sl.md create mode 100644 additional-material/translations/Slovenian/moving-a-commit-to-a-different-branch.sl.md create mode 100644 additional-material/translations/Slovenian/removing-a-file.sl.md create mode 100644 additional-material/translations/Slovenian/removing-branch-from-your-repository.sl.md create mode 100644 additional-material/translations/Slovenian/resolving-merge-conflicts.sl.md create mode 100644 additional-material/translations/Slovenian/reverting-a-commit.sl.md create mode 100644 additional-material/translations/Slovenian/squashing-commits.sl.md create mode 100644 additional-material/translations/Slovenian/stashing-a-file.sl.md create mode 100644 additional-material/translations/Slovenian/undoing-a-commit.sl.md create mode 100644 additional-material/translations/Ukrainian/removing-a-file.ua.md create mode 100644 additional-material/translations/Urdu/additional-material.ur.md create mode 100644 additional-material/translations/Urdu/amending-a-commit.ur.md create mode 100644 additional-material/translations/Useful-links-for-further-learning.id.md create mode 100644 additional-material/translations/Vietnamese/resolving-merge-conflicts.vi.md create mode 100644 additional-material/translations/additional-material.np.md create mode 100644 additional-material/translations/amending-a-commit.np.md create mode 100644 additional-material/translations/configuring-git.np.md create mode 100644 additional-material/translations/delete-branch-locally.fa.md create mode 100644 cli-tool-tutorials/git-bash-windows-tutorial.md create mode 100644 cli-tool-tutorials/github-cli-tutorial.md create mode 100644 gui-tool-tutorials/github-desktop-old-version-tutorial.md create mode 100644 gui-tool-tutorials/github-desktop-tutorial.md create mode 100644 gui-tool-tutorials/github-windows-intellij-tutorial.md create mode 100644 gui-tool-tutorials/github-windows-vs-code-tutorial.md create mode 100644 gui-tool-tutorials/github-windows-vs2017-tutorial.md create mode 100644 gui-tool-tutorials/gitkraken-tutorial.md create mode 100644 gui-tool-tutorials/sourcetree-macos-tutorial.md create mode 100644 gui-tool-tutorials/sublime-merge-tutorial.md create mode 100644 gui-tool-tutorials/translations/github-desktop-tutorial.ng_yr.md create mode 100644 gui-tool-tutorials/translations/github-desktop-tutorial.pt_br.md create mode 100644 gui-tool-tutorials/translations/github-windows-intellij-tutorial.pt_br.md create mode 100644 gui-tool-tutorials/translations/github-windows-vs-code-tutorial-hi.md create mode 100644 gui-tool-tutorials/translations/github-windows-vs-code-tutorial.pt_br.md create mode 100644 gui-tool-tutorials/translations/github-windows-vs-code-tutorial_id.md create mode 100644 gui-tool-tutorials/translations/github-windows-vs-code-tutorial_pt_br.md create mode 100644 gui-tool-tutorials/translations/github-windows-vs2017-tutorial.pt_br.md create mode 100644 gui-tool-tutorials/translations/gitkraken-tutorial.pt-br.md create mode 100644 translations/README.afk.md create mode 100644 translations/README.al.md create mode 100644 translations/README.am.md create mode 100644 translations/README.ar.md create mode 100644 translations/README.aze.md create mode 100644 translations/README.bg.md create mode 100644 translations/README.bih.md create mode 100644 translations/README.bn.md create mode 100644 translations/README.by.md create mode 100644 translations/README.ca.md create mode 100644 translations/README.cs.md create mode 100644 translations/README.da.md create mode 100644 translations/README.de.md create mode 100644 translations/README.eg.md create mode 100644 translations/README.en-pirate.md create mode 100644 translations/README.es.md create mode 100644 translations/README.fa.md create mode 100644 translations/README.fi.md create mode 100644 translations/README.fr.md create mode 100644 translations/README.ge.md create mode 100644 translations/README.gl.md create mode 100644 translations/README.gr.md create mode 100644 translations/README.guj.md create mode 100644 translations/README.hau.md create mode 100644 translations/README.hb.md create mode 100644 translations/README.hi.md create mode 100644 translations/README.hne.md create mode 100644 translations/README.hr.md create mode 100644 translations/README.hu.md create mode 100644 translations/README.hy.md create mode 100644 translations/README.id.md create mode 100644 translations/README.igb.md create mode 100644 translations/README.it.md create mode 100644 translations/README.ja.md create mode 100644 translations/README.ka.md create mode 100644 translations/README.ko.md create mode 100644 translations/README.kws.md create mode 100644 translations/README.kz.md create mode 100644 translations/README.la.md create mode 100644 translations/README.lt.md create mode 100644 translations/README.lv.md create mode 100644 translations/README.me.md create mode 100644 translations/README.mk.md create mode 100644 translations/README.ml.md create mode 100644 translations/README.mm_unicode.md create mode 100644 translations/README.mr.md create mode 100644 translations/README.mx.md create mode 100644 translations/README.my.md create mode 100644 translations/README.nl.md create mode 100644 translations/README.no.md create mode 100644 translations/README.np.md create mode 100644 translations/README.pb.md create mode 100644 translations/README.pl.md create mode 100644 translations/README.ps.md create mode 100644 translations/README.pt-pt.md create mode 100644 translations/README.pt_br.md create mode 100644 translations/README.pus.md create mode 100644 translations/README.ro.md create mode 100644 translations/README.ru.md create mode 100644 translations/README.se.md create mode 100644 translations/README.si.md create mode 100644 translations/README.sindhi.md create mode 100644 translations/README.sk.md create mode 100644 translations/README.sl.md create mode 100644 translations/README.slk.md create mode 100644 translations/README.sr.md create mode 100644 translations/README.ta.md create mode 100644 translations/README.te.md create mode 100644 translations/README.th.md create mode 100644 translations/README.tl.md create mode 100644 translations/README.tr.md create mode 100644 translations/README.ua.md create mode 100644 translations/README.un-aln.md create mode 100644 translations/README.ur.md create mode 100644 translations/README.uz.md create mode 100644 translations/README.vn.md create mode 100644 translations/README.yor.md create mode 100644 translations/README.zh-cn.md create mode 100644 translations/README.zh-tw.md create mode 100644 translations/README.zul.md create mode 100644 translations/Translations.md diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md new file mode 100644 index 00000000000..97ef1dd8a52 --- /dev/null +++ b/.github/CONTRIBUTING.md @@ -0,0 +1,86 @@ +# Contribution guide + +We appreciate your thought to contribute to open source. :heart: + +If you'd like to suggest a change in the tutorials or the workflow, please [raise an issue](https://github.com/firstcontributions/first-contributions/issues/new). We can have a discussion to better understand the problem, get more people involved and make a collective decision. + +If you're making changes to a translation, please request a review from our previous contributors who has translated to the respective translation. Our goal is for all translations to have the same content as the English one (`Readme.md`) (Except for links to other translations. We realised that it doesn't add much value) + +### Our reviewers :sparkles: + +| Language Name | Name in English | Reviewers| +|---|---|---| +| Afrikaans | [Afrikaans](../translations/README.afk.md) | [@zecollokaris](https://github.com/zecollokaris) | +| Albanian | [Albanian](../translations/README.al.md) | [RronKurtishi](https://github.com/RronKurtishi) | +| العربية | [Arabic](../translations/README.ar.md) | [OsaidAlhomedy](https://github.com/OsaidAlhomedy) [AlaaYlula](https://github.com/AlaaYlula) [Laith-Alayassa](https://github.com/Laith-Alayassa) | +| Azerbaijani | [Azerbaijani](../translations/README.aze.md) | [@isakurbanov744](https://github.com/isakurbanov744) [@Ahm3tJ4f](https://github.com/Ahm3tJ4f) | +| Bulgarian | [Bulgarian](../translations/README.bg.md) | []() | +| Bosnian | [Bosnian](../translations/README.bih.md) | []() | +| বাংলা | [Bengali](../translations/README.bn.md) | [@cse031sust02](https://github.com/cse031sust02) | +| Belarusian | [Belarusian](../translations/README.by.md) | []() | +| Català | [Catalan](../translations/README.ca.md) | [@Sergih28](https://github.com/Sergih28) | +| čeština | [Czech](../translations/README.cs.md) | []() | +| Danish | [Danish](../translations/README.da.md) | [@7013145](https://github.com/7013145) | +| Deutsch | [German](../translations/README.de.md) | [@lkreimann](https://github.com/lkreimann) | +| المصرية | [Egyptian](../translations/README.eg.md) | [@MichaelKMalak](https://github.com/MichaelKMalak) | +| English (Pirate) | [English (Pirate)](../translations/README.en-pirate.md) | [@lukeoliff](https://github.com/lukeoliff) | +| Español | [Spanish](../translations/README.es.md) | [@yirini](https://github.com/yirini) [@aaossa](https://github.com/aaossa) | +| فارسی | [Persian](../translations/README.fa.md) | [@ThirdScript](https://github.com/ThirdScript) | +| Finnish | [Finnish](../translations/README.fi.md) | []() | +| Français | [French](../translations/README.fr.md) | [@LePetitRenard](https://github.com/LePetitRenard) | +| ქართული | [Georgian](../translations/README.ka.md) | [@iko1133](https://github.com/iko1133) | +| Galego | [Galician](../translations/README.gl.md) | [@siderio2](https://github.com/siderio2) | +| Greek | [Greek](../translations/README.gr.md) | []() | +| Gujarati | [Gujarati](../translations/README.guj.md) | [@smitgajjar](https://github.com/smitgajjar) | +| Hausa | [Hausa](../translations/README.ha.md) | []() | +| עברית | [Hebrew](../translations/README.hb.md) | [@TomerPacific](https://github.com/TomerPacific) | +| हिन्दी | [Hindi](../translations/README.hi.md) | [@arshadkazmi42](https://github.com/arshadkazmi42) [@sara-02](https://github.com/sara-02) [shrut1996](https://github.com/shrut1996) | +| Chhattisgarhi | [Chhattisgarhi](../translations/README.hne.md) | [@pradyyadav](https://github.com/pradyyadav) | +| Magyar | [Hungarian](../translations/README.hu.md) | []() | +| Armenian | [Armenian](../translations/README.hy.md) | []() | +| Indonesian | [Indonesian](../translations/README.id.md) | [@hahn](https://github.com/hahn) | +| Igbo | [Igbo](../translations/README.igb.md) | [@zecollokaris](https://github.com/zecollokaris) []() | +| Italiano | [Italian](../translations/README.it.md) | [@platipo](https://github.com/platipo) | +| 日本語 | [Japanese](../translations/README.ja.md) | [@cbondurant](https://github.com/cbondurant) | +| ಕನ್ನಡ | [Kannada](../translations/README.ka.md) | []() | +| 한국어 | [Korean](../translations/README.ko.md) | [@espozbob](https://github.com/espozbob) | +| Kiswahili | [Kiswahili](../translations/README.ksw.md) |[@zecollokaris](https://github.com/zecollokaris) []() | +| Kazakh | [Kazakh](../translations/README.kz.md) | [@kurshakuz](https://github.com/kurshakuz) | +| Lietuvių kalba | [Lithuanian](../translations/README.lt.md) | [@neone35](https://github.com/neone35) | +| Latviešu valoda | [Latvian](../translations/README.lv.md) | []() | +| | [me](../translations/README.me.md) | [@neone35]() | +| Македонски | [Macedonian](../translations/README.mk.md) | []() | +| മലയാളം | [Malayalam](../translations/README.ml.md) | [@yedhukrishnan](https://github.com/yedhukrishnan) | +| Burmese | [Burmese](../translations/README.mm_unicode.md) | [@lwinkyawmyat](https://github.com/lwinkyawmyat) | +| मराठी | [Marathi](../translations/README.mr.md) | [@bantya](https://github.com/bantya) | +| Español de México | [Spanish of Mexico](../translations/README.mx.md) | []() | +| Bahasa Melayu | [Malay](../translations/README.my.md) | []() | +| Nederlandse | [Dutch](../translations/README.nl.md) | [@MJMajoor](https://github.com/MJMajoor) | +| Norsk | [Norwegian](../translations/README.no.md) | []() | +| नेपाली | [Nepali](../translations/README.np.md) | [@milap-neupane](https://github.com/milap-neupane) | +| ਪਨਜਾਬੀ | [Punjabi](../translations/README.pa.md) | []() | +| Polski | [Polish](../translations/README.pl.md) | [@P1X3L0V4](https://github.com/P1X3L0V4) [@mikowhy](https://github.com/mikowhy) | +| Português | [Portuguese (Portugal)](../translations/README.pt-pt.md) | [@RamosCSV](https://github.com/RamosCSV) | +| Português do Brasil | [Portuguese (Brazil)](../translations/README.pt-br.md) | [@OtacilioN](https://github.com/OtacilioN) [@gabrielsanttana](https://github.com/gabrielsanttana)| +| Română | [Romanian](../translations/README.ro.md) | [ @dp97](https://github.com/dp97) | +| Русский | [Russian](../translations/README.ru.md) | [@ayanovsk](https://github.com/ayanovsk) | +| Svenska | [Swedish](../translations/README.sv.md) | [@jcer](https://github.com/jcer) | +| Sinhala | [Sinhala](../translations/README.si.md) | []() | +| Sindhi | [Sindhi](../translations/README.sindhi.md) | []() | +| Slovenčina | [Slovak](../translations/README.sk.md) | [@CoderKlemen](https://github.com/CoderKlemen) | +| Slovenščina | [Slovenian](../translations/README.slk.md) | [@hercegtomas](https://github.com/hercegtomas) | +| Serbian | [Serbian](../translations/README.sr.md) | [@Mateja3m](https://github.com/Mateja3m) | +| தமிழ் | [Tamil](../translations/README.ta.md) | [@sathishkumar-manogaran](https://github.com/sathishkumar-manogaran) | +| తెలుగు | [Telugu](../translations/README.te.md) | []() | +| ไทย | [Thai](../translations/README.th.md) | [@AimeTPGM](https://github.com/AimeTPGM) | +| Tagalog | [Tagalog](../translations/README.tl.md) | []() | +| Türkçe | [Turkish](../translations/README.tr.md) | [@yamac-kurtulus](https://github.com/yamac-kurtulus) | +| Українська | [Ukrainian](../translations/README.ua.md) | []() | +| Universal Alien | [Universal Alien](../translations/README.un-aln.md) | [@debjit-bw]() | +| اردو | [Urdu](../translations/README.ur.md) | [@Shhzdmrz](https://github.com/Shhzdmrz) | +| Tiếng Việt | [Vietnamese](../translations/README.vn.md) | [@tranlyvu](https://github.com/tranlyvu) | +| Yorùbá | [Yorùbá](../translations/README.yor.md) | []() | +| 中文 | [Chinese (Simplified)](../translations/README.zh-cn.md) | [@yuzhoujr](https://github.com/yuzhoujr) | +| 中文 | [Chinese (Traditional)](../translations/README.zh-tw.md) | [@WeiChienHsu](https://github.com/WeiChienHsu) | +| Zulu | [Zulu](../translations/README.zu.md) | [@zecollokaris](https://github.com/zecollokaris) []() | + diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md new file mode 100644 index 00000000000..7eeb142fe35 --- /dev/null +++ b/.github/ISSUE_TEMPLATE.md @@ -0,0 +1,20 @@ + + +🐞 **Problem** + + + +🎯 **Goal** + + + +💡 **Possible solutions** + + +📋 **Steps to solve the problem** + +* Comment below about what you've started working on. +* Add, commit, push your changes. +* Submit a pull request and add this in comments - `Addresses #` +* Ask for reviews in comments section of pull request. +* Celebrate your contribution to this project. 🎉 diff --git a/.github/ISSUE_TEMPLATE/issue-template.md b/.github/ISSUE_TEMPLATE/issue-template.md new file mode 100644 index 00000000000..edaaf5b6e5f --- /dev/null +++ b/.github/ISSUE_TEMPLATE/issue-template.md @@ -0,0 +1,30 @@ +--- +name: Suggest changes +about: If you want to report a bug or suggest improvements, please open an issue. +title: '' +labels: discussion, question +assignees: Roshanjossey + +--- + + + + +🐞 **Problem** + + + +🎯 **Goal** + + + +💡 **Possible solutions** + + +📋 **Steps to solve the problem** + +* Comment below about what you've started working on. +* Add, commit, push your changes. +* Submit a pull request and add this in comments - `Addresses #` +* Ask for reviews in comments section of pull request. +* Celebrate your contribution to this project. 🎉 diff --git a/.gitignore b/.gitignore new file mode 100644 index 00000000000..894831f3cb6 --- /dev/null +++ b/.gitignore @@ -0,0 +1,390 @@ +.DS_Store; +.idea/ +.vs +.env +# User-specific files +*.rsuser +*.suo +*.user +*.userosscache +*.sln.docstates +*.swp + +# User-specific files (MonoDevelop/Xamarin Studio) +*.userprefs + +# Mono auto generated files +mono_crash.* + +# Build results +[Dd]ebug/ +[Dd]ebugPublic/ +[Rr]elease/ +[Rr]eleases/ +x64/ +x86/ +[Ww][Ii][Nn]32/ +[Aa][Rr][Mm]/ +[Aa][Rr][Mm]64/ +bld/ +[Bb]in/ +[Oo]bj/ +[Ll]og/ +[Ll]ogs/ + +# Visual Studio 2015/2017 cache/options directory +.vs/ +# Uncomment if you have tasks that create the project's static files in wwwroot +#wwwroot/ + +# Visual Studio 2017 auto generated files +Generated\ Files/ + +# MSTest test Results +[Tt]est[Rr]esult*/ +[Bb]uild[Ll]og.* + +# NUnit +*.VisualState.xml +TestResult.xml +nunit-*.xml + +# Build Results of an ATL Project +[Dd]ebugPS/ +[Rr]eleasePS/ +dlldata.c + +# Benchmark Results +BenchmarkDotNet.Artifacts/ + +# .NET Core +project.lock.json +project.fragment.lock.json +artifacts/ + +# ASP.NET Scaffolding +ScaffoldingReadMe.txt + +# StyleCop +StyleCopReport.xml + +# Files built by Visual Studio +*_i.c +*_p.c +*_h.h +*.ilk +*.meta +*.obj +*.iobj +*.pch +*.pdb +*.ipdb +*.pgc +*.pgd +*.rsp +*.sbr +*.tlb +*.tli +*.tlh +*.tmp +*.tmp_proj +*_wpftmp.csproj +*.log +*.tlog +*.vspscc +*.vssscc +.builds +*.pidb +*.svclog +*.scc + +# Chutzpah Test files +_Chutzpah* + +# Visual C++ cache files +ipch/ +*.aps +*.ncb +*.opendb +*.opensdf +*.sdf +*.cachefile +*.VC.db +*.VC.VC.opendb + +# Visual Studio profiler +*.psess +*.vsp +*.vspx +*.sap + +# Visual Studio Trace Files +*.e2e + +# TFS 2012 Local Workspace +$tf/ + +# Guidance Automation Toolkit +*.gpState + +# ReSharper is a .NET coding add-in +_ReSharper*/ +*.[Rr]e[Ss]harper +*.DotSettings.user + +# TeamCity is a build add-in +_TeamCity* + +# DotCover is a Code Coverage Tool +*.dotCover + +# AxoCover is a Code Coverage Tool +.axoCover/* +!.axoCover/settings.json + +# Coverlet is a free, cross platform Code Coverage Tool +coverage*.json +coverage*.xml +coverage*.info + +# Visual Studio code coverage results +*.coverage +*.coveragexml + +# NCrunch +_NCrunch_* +.*crunch*.local.xml +nCrunchTemp_* + +# MightyMoose +*.mm.* +AutoTest.Net/ + +# Web workbench (sass) +.sass-cache/ + +# Installshield output folder +[Ee]xpress/ + +# DocProject is a documentation generator add-in +DocProject/buildhelp/ +DocProject/Help/*.HxT +DocProject/Help/*.HxC +DocProject/Help/*.hhc +DocProject/Help/*.hhk +DocProject/Help/*.hhp +DocProject/Help/Html2 +DocProject/Help/html + +# Click-Once directory +publish/ + +# Publish Web Output +*.[Pp]ublish.xml +*.azurePubxml +# Note: Comment the next line if you want to checkin your web deploy settings, +# but database connection strings (with potential passwords) will be unencrypted +*.pubxml +*.publishproj + +# Microsoft Azure Web App publish settings. Comment the next line if you want to +# checkin your Azure Web App publish settings, but sensitive information contained +# in these scripts will be unencrypted +PublishScripts/ + +# NuGet Packages +*.nupkg +# NuGet Symbol Packages +*.snupkg +# The packages folder can be ignored because of Package Restore +**/[Pp]ackages/* +# except build/, which is used as an MSBuild target. +!**/[Pp]ackages/build/ +# Uncomment if necessary however generally it will be regenerated when needed +#!**/[Pp]ackages/repositories.config +# NuGet v3's project.json files produces more ignorable files +*.nuget.props +*.nuget.targets + +# Nuget personal access tokens and Credentials +nuget.config + +# Microsoft Azure Build Output +csx/ +*.build.csdef + +# Microsoft Azure Emulator +ecf/ +rcf/ + +# Windows Store app package directories and files +AppPackages/ +BundleArtifacts/ +Package.StoreAssociation.xml +_pkginfo.txt +*.appx +*.appxbundle +*.appxupload + +# Visual Studio cache files +# files ending in .cache can be ignored +*.[Cc]ache +# but keep track of directories ending in .cache +!?*.[Cc]ache/ + +# Others +ClientBin/ +~$* +*~ +*.dbmdl +*.dbproj.schemaview +*.jfm +*.pfx +*.publishsettings +orleans.codegen.cs + +# Including strong name files can present a security risk +# (https://github.com/github/gitignore/pull/2483#issue-259490424) +#*.snk + +# Since there are multiple workflows, uncomment next line to ignore bower_components +# (https://github.com/github/gitignore/pull/1529#issuecomment-104372622) +#bower_components/ + +# RIA/Silverlight projects +Generated_Code/ + +# Backup & report files from converting an old project file +# to a newer Visual Studio version. Backup files are not needed, +# because we have git ;-) +_UpgradeReport_Files/ +Backup*/ +UpgradeLog*.XML +UpgradeLog*.htm +ServiceFabricBackup/ +*.rptproj.bak + +# SQL Server files +*.mdf +*.ldf +*.ndf + +# Business Intelligence projects +*.rdl.data +*.bim.layout +*.bim_*.settings +*.rptproj.rsuser +*- [Bb]ackup.rdl +*- [Bb]ackup ([0-9]).rdl +*- [Bb]ackup ([0-9][0-9]).rdl + +# Microsoft Fakes +FakesAssemblies/ + +# GhostDoc plugin setting file +*.GhostDoc.xml + +# Node.js Tools for Visual Studio +.ntvs_analysis.dat +node_modules/ + +# Visual Studio 6 build log +*.plg + +# Visual Studio 6 workspace options file +*.opt + +# Visual Studio 6 auto-generated workspace file (contains which files were open etc.) +*.vbw + +# Visual Studio LightSwitch build output +**/*.HTMLClient/GeneratedArtifacts +**/*.DesktopClient/GeneratedArtifacts +**/*.DesktopClient/ModelManifest.xml +**/*.Server/GeneratedArtifacts +**/*.Server/ModelManifest.xml +_Pvt_Extensions + +# Paket dependency manager +.paket/paket.exe +paket-files/ + +# FAKE - F# Make +.fake/ + +# CodeRush personal settings +.cr/personal + +# Python Tools for Visual Studio (PTVS) +__pycache__/ +*.pyc + +# Cake - Uncomment if you are using it +# tools/** +# !tools/packages.config + +# Tabs Studio +*.tss + +# Telerik's JustMock configuration file +*.jmconfig + +# BizTalk build output +*.btp.cs +*.btm.cs +*.odx.cs +*.xsd.cs + +# OpenCover UI analysis results +OpenCover/ + +# Azure Stream Analytics local run output +ASALocalRun/ + +# MSBuild Binary and Structured Log +*.binlog + +# NVidia Nsight GPU debugger configuration file +*.nvuser + +# MFractors (Xamarin productivity tool) working folder +.mfractor/ + +# Local History for Visual Studio +.localhistory/ + +# BeatPulse healthcheck temp database +healthchecksdb + +# Backup folder for Package Reference Convert tool in Visual Studio 2017 +MigrationBackup/ + +# Ionide (cross platform F# VS Code tools) working folder +.ionide/ + +# Fody - auto-generated XML schema +FodyWeavers.xsd + +# VS Code files for those working on multiple tools +.vscode/* +!.vscode/settings.json +!.vscode/tasks.json +!.vscode/launch.json +!.vscode/extensions.json +*.code-workspace + +# Local History for Visual Studio Code +.history/ + +# Windows Installer files from build outputs +*.cab +*.msi +*.msix +*.msm +*.msp + +# JetBrains Rider +.idea/ +*.sln.iml +.vscode/settings.json +.DS_Store diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 00000000000..6cf8f1914e7 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,133 @@ + +# Contributor Covenant Code of Conduct + +## Our Pledge + +We as members, contributors, and leaders pledge to make participation in our +community a harassment-free experience for everyone, regardless of age, body +size, visible or invisible disability, ethnicity, sex characteristics, gender +identity and expression, level of experience, education, socio-economic status, +nationality, personal appearance, race, caste, color, religion, or sexual +identity and orientation. + +We pledge to act and interact in ways that contribute to an open, welcoming, +diverse, inclusive, and healthy community. + +## Our Standards + +Examples of behavior that contributes to a positive environment for our +community include: + +* Demonstrating empathy and kindness toward other people +* Being respectful of differing opinions, viewpoints, and experiences +* Giving and gracefully accepting constructive feedback +* Accepting responsibility and apologizing to those affected by our mistakes, + and learning from the experience +* Focusing on what is best not just for us as individuals, but for the overall + community + +Examples of unacceptable behavior include: + +* The use of sexualized language or imagery, and sexual attention or advances of + any kind +* Trolling, insulting or derogatory comments, and personal or political attacks +* Public or private harassment +* Publishing others' private information, such as a physical or email address, + without their explicit permission +* Other conduct which could reasonably be considered inappropriate in a + professional setting + +## Enforcement Responsibilities + +Community leaders are responsible for clarifying and enforcing our standards of +acceptable behavior and will take appropriate and fair corrective action in +response to any behavior that they deem inappropriate, threatening, offensive, +or harmful. + +Community leaders have the right and responsibility to remove, edit, or reject +comments, commits, code, wiki edits, issues, and other contributions that are +not aligned to this Code of Conduct, and will communicate reasons for moderation +decisions when appropriate. + +## Scope + +This Code of Conduct applies within all community spaces, and also applies when +an individual is officially representing the community in public spaces. +Examples of representing our community include using an official e-mail address, +posting via an official social media account, or acting as an appointed +representative at an online or offline event. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported to the community leaders responsible for enforcement at +firstcontributions@gmail.com. +All complaints will be reviewed and investigated promptly and fairly. + +All community leaders are obligated to respect the privacy and security of the +reporter of any incident. + +## Enforcement Guidelines + +Community leaders will follow these Community Impact Guidelines in determining +the consequences for any action they deem in violation of this Code of Conduct: + +### 1. Correction + +**Community Impact**: Use of inappropriate language or other behavior deemed +unprofessional or unwelcome in the community. + +**Consequence**: A private, written warning from community leaders, providing +clarity around the nature of the violation and an explanation of why the +behavior was inappropriate. A public apology may be requested. + +### 2. Warning + +**Community Impact**: A violation through a single incident or series of +actions. + +**Consequence**: A warning with consequences for continued behavior. No +interaction with the people involved, including unsolicited interaction with +those enforcing the Code of Conduct, for a specified period of time. This +includes avoiding interactions in community spaces as well as external channels +like social media. Violating these terms may lead to a temporary or permanent +ban. + +### 3. Temporary Ban + +**Community Impact**: A serious violation of community standards, including +sustained inappropriate behavior. + +**Consequence**: A temporary ban from any sort of interaction or public +communication with the community for a specified period of time. No public or +private interaction with the people involved, including unsolicited interaction +with those enforcing the Code of Conduct, is allowed during this period. +Violating these terms may lead to a permanent ban. + +### 4. Permanent Ban + +**Community Impact**: Demonstrating a pattern of violation of community +standards, including sustained inappropriate behavior, harassment of an +individual, or aggression toward or disparagement of classes of individuals. + +**Consequence**: A permanent ban from any sort of public interaction within the +community. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], +version 2.1, available at +[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. + +Community Impact Guidelines were inspired by +[Mozilla's code of conduct enforcement ladder][Mozilla CoC]. + +For answers to common questions about this code of conduct, see the FAQ at +[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at +[https://www.contributor-covenant.org/translations][translations]. + +[homepage]: https://www.contributor-covenant.org +[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html +[Mozilla CoC]: https://github.com/mozilla/diversity +[FAQ]: https://www.contributor-covenant.org/faq +[translations]: https://www.contributor-covenant.org/translations diff --git a/Contributors.md b/Contributors.md new file mode 100644 index 00000000000..ce423753a04 --- /dev/null +++ b/Contributors.md @@ -0,0 +1,572 @@ +# Contributors + +- [Carlos Luque] (https://github.com/carlosluque) +- [Benjamin Morgiewicz](https://github.com/BaseBenjamin13) +- [Keenan Speaks] (https://github.com/Styleshift) +- [Sabir Khan](https://github.com/simplysabir) +- [Aman Bharti](https://github.com/aman0ab) +- [Archishman Dash](https://www.github.com/aholic-archie) +- [Esta es mi primer contribucion](https://github.com/PabloCH23) +- [Juanma Romero](https://github.com/juanmaroni/) +- [Craig Leppan] (https://github.com/yoyozi) +- [Josh Mayeda] (https://github.com/joshmayeda) +- [Chhabi Acharya](https://github.com/Chhabii) +- [Jeevan Naik](https://github.com/JeevanNaikOP) +- [Anuhya sabbani](https://github.com/anuhyasabbani) +- [Bojidar Vladimirov](https://github.com/BojidarV) +- [Poyraz Bahcivan](https://github.com/poyrazbahcivan) +- [Ryan Ignasiak](https://github.com/theravenousR) +- [Arman Hadzigrahic](https://github.com/armeono) +- [Theo Dep](https://github.com/theoDep) +- [Andreas](https://github.com/Andreas1593) +- [Chase Hunter](https://github.com/TaylorChaseHunter) +- [Yash Wake](https://github.com/yashwxd) +- [Ankith Motha](https://github.com/Alpha-github/) +- [Masih Karimi](https://github.com/MasihKarimi) +- [Gabriel Waegner](https://github.com/Gwaegs) +- [Anand S](https://github.com/anand2000s) +- [Aryan Wadhwa](https://github.com/TastyBiscuit0808/first-contributions) +- [Ishmael Peavy] (https://github.com/ipeavy) +- [Joker-CDSS-Abasiediedu] (https://github.com/Joker-CDSS) +- [R.Noto](https://github.com/RikitoNoto) +- [James Hansen](https://github.com/jameszenartist) +- [Brandon Andrews](https://github.com/brandrewsss) +- [Gabriel Fernandes](https://github.com/GabrielFernandes251) +- [Lorenzo Francisco](https://github.com/lozo6) +- [Pratyush Tyagi](https://github.com/Pratyush0612) +- [Surajit Dey Sarkar](https://github.com/Surajitds) +- [Mohit Marathe](https://github.com/Mohit2758) +- [Satarupa Deb]( https://github.com/Satarupa22-SD) +- [Edwin Kim](https://github.com/edwinkim97) +- [Rezgui Med Aziz](https://github.com/medAzizRezgui) +- [Henrikas Budrys](https://github.com/hbportfolio) +- [Vijendra Pandey](https://github.com/VijendraPandey) +- [Erik Opinaldo](https://github.com/erikopinaldo) +- [Utpal Savaliya](https://github.com/utpalsavliya) +- [stardustgd](https://github.com/stardustgd) +- [mahalakshmikutcharlapati](https://github.com/mahalakshmikutcharlapati) +- [randose](https://github.com/randose) +- [sagehourihan](https://github.com/SageHourihan) +- [Chandan Arya](https://github.com/alpha2lucifer) +- [suman](https://github.com/sumanghosh13) +- [Thet Paing Soe](https://github.com/ThetPaingSoe) +- [regularmute](https://github.com/regularmute) +- [Tewodros Amare](https://github.com/teddygizachew) +- [Stephen Silveira](https://github.com/stephen-silveira) +- [Anmol Bansal](https://github.com/AnmolBansalDEV) +- [Adeolu Oyinlola](https://github.com/deoluoyinlola) +- [Alisher Muzaffarov](https://github.com/aliml92) +- [bohemian-x] (https://github.com/bohemiancode-x) +- [Apeksha Arora](http://github.com/apekshasan) +- [RAHUL g](https://github.com/Rahulg8270) +- [Chirayu Pancholi](https://github.com/Chirayu31) +- [AnushaPalle](https://github.com/AnushaPalle) +- [Hemant Lohar] (https://github.com/Hemant-Lohar) +- [Soubhik Maji](https://github.com/majisoubhik01) +- [Jisan-mia](https://github.com/Jisan-mia) +- [Gideon Opoku](https://github.com/nana562) +- [wfrsk](hhpts://github.com/wfrsk) +- [Khalid-Hasan](https://github.com/khalidx3) +- [David Lopez](https://github.com/davidnoelopez) +- [Moustafa Hassan](https://github.com/MoustafaHassan1) +- [Brendan Tuckerman](https://github.com/MrMaverick79/) +- [Renz Sira](https://github.com/rcsira) +- [CarmenResquin] (https://github.com/CarmenResquin) +- [Rounak Shrestha](https://github.com/Rounak-stha) +- [Obafemi Oludahunsi] (https://github.com/Obafemi-NG) +- [James Hunter] (https://github.com/Jameshunter1) +- [SAHIL SINHA](https://github.com/SahilSinha007) +- [Maximiliano Carrasco](https://github.com/macsito-prog) +- [Sarthak Mittal](https://github.com/SarthakMittal777) +- [Luisa Haase](https://github.com/luisaha) +- [Nayna Sahu ](https://github.com/NaynaSahu/) +- [Bruno De Paula 🚀](https://github.com/Gr33nLight) +- [Sudarsan Balaji](https://github.com/artfuldev) +- [Ricardo Beaujon] (http://rbeaujon.com) +- [jatin kumar](https://github.com/jatin75757) +- [ahmad nawaz khan](https://github.com/4hmaad) +- [Ishita Batra](https://github.com/ishita6) +- [Devanshu Mahapatra](https://github.com/Devanshu-17) +- [Pablo Alejandro](https://github.com/Pabloalesca) +- [Khan Winter](https://github.com/thecoolwinter) +- [Mickhat](https://github.com/Mickhat) +- [Mohit Bishwokarma](https://github.com/Mohitbishukarma) +- [Matt Arias](https://github.com/FreedSoul) +- [Alex Song](https://github.com/TheRealAlexSong) +- [mahalakshmikutcharlapati](https://github.com/mahalakshmikutcharlapati) +- [Andrea Mammoliti](https://github.com/AndreusSH) +- [Praddyum Verma](https://praddy2009.github.io/) +- [Divyanshu Singhal](https://github.com/divyanshu9821) +- [bhavana] (https://github.com/bhavana-263) +- [Don Chisolm](https://github.com/Donchiz77) +- [Usman Khan](https://github.com/UsmanK7) +- [Shannon Torcato](https://github.com/shannontorcato) +- [DaneeSkripter](htttps://github.com/daneeskripter) +- [IsaacWritesCode](https://github.com/IsaacWritesCodeGithub) +- [Reed Conway](https://github.com/ReedConway) +- [Pratheek Shetty](https://github.com/pratheek-shett) +- [Dionne Mascarenhas](https://github.com/dmasc2) +- [Usman Khan](https://github.com/UsmanK7) +- [SAURABH200300](https://github.com/SAURABH200301) +- [Mustafa Bhm](https://github.com/mustafa-bhm) +- [Joswagc](https://github.com/joswagc) +- [Khushi Shukla](https://github.com/Khushi-Shukla) +- [Srijan D](https://github.com/Srijan-D) +- [srinivasthedeveloper](https://github.com/srinivasthedeveloper) +- [divijaa](https://github.com/divijaa) +- [ngweishen99](https://github.com/ngweishen99) +- [Avedis_Yapoudjian](https://github.com/AvedisY) +- [xa49](https://github.com/xa49) +- [bytesofbec](https://github.com/bytesofbec) +- [SamAtkinsonModeste](https://www.github.com/SamAtkinsonModeste) +- [william-chalk](https://github.com/william-chalk) +- [terminalPoltergeist](https://github.com/terminalPoltergeist) +- [katumba jonathan paul](https://github.com/kpaool) +- [Sushil Suthar](https://github.com/isushilsuthar) +- [Anupama Jedi](https://github.com/anupama003) +- [Jalebium69](https://github.com/jesherjoshua) +- [marioluiss](https://github.com/MarioLuiss) +- [Bojidar Vladimirov](https://github.com/BojidarV) +- [Cocozin13](https://github.com/Cocozin13) +- [Yuvraj Seegolam](https://github.com/yuvraj108c) +- [Gabriel Coelho](https://github.com/bielcoelho) +- [Urvesh Radadiya](https://github.com/URVESH1121) +- [Jibrin Ahmed](https://github.com/TacetSteeze) +- [Kely Sarmi](https://github.com/kelysi) +- [Adit Bhargava](https://github.com/zcsop1206) +- [Tanu Singh](https://github.com/TanuSingh17) + [Adarsh Sharma](https://github.com/Adarsh1885) +- [Shreyas Bhagwat](https://github.com/ShreyasBhagwat) +- [Sahil Barsaiyan](https://github.com/Sahilb12) +- [Dario Gumucio](https://github.com/dariogumucio) +- [Aman Bhagat](https://GitHub.com/sanayaa) +- [Zoltan Nahoczki](https://github.com/nahoczki) +- [Siddharth Singh](https://github.com/siddharthqs/rust_quant) +- [Akshay Jain](https://github.com/rudeakshay) +- [Sujith P](https://github.com/Alfa-ZORO) +- [NIKITA PANDEY 🦋](https://github.com/NIKITApandey01) +- [Cesar Rodas](https://github.com/Care99) +- [Sahil Singh](www.linkedin.com/in/sahil-singh-ss9824) +- [imappuru](https://github.com/imappuru) +- [plaguss](https://github.com/plaguss) +- [Rafiqul Shopon](https://github.com/rafiqulshopon) +- [verissimon](https://github.com/verissimon) +- [DragonFireShield](https://github.com/dragonfireshield) +- [Al Aasad Nur Riyad](https://github.com/nurRiyad) +- [Muhammed Emin Boydak](https://github.com/eminboydak) +- [Teguh Widodo](https://github.com/teguhwin8) +- [Harshit Arora](https://github.com/harshit0755) +- [Mayank Jha](https://github.com/mkjha482) +- [Frank Akrasi Antwi](https://github.com/fantwi) +- [Shreya Dubey](https://github.com/ShreyaDubey1001) +- [LaplancheMaxime](https://github.com/LaplancheMaxime) +- [Vicky Grover](https://github.com/LaplancheMaxime) +- [Siddhant Majumder](https://github.com/Codeworm08) +- [Soumyadip Bhowmik](https://github.com/SoumyadipBhowmik) +- [Alex Reveles](https://github.com/aajj333) +- [Samuel Oluyede](https://github.com/Masei25) +- [Ankush](https://github.com/ankushrai999) +- [Phillip Chu](https://github.com/phillippchu) +- [Aazim Parwaz](https://github.com/Aazim-parwaz) +- [Monish Prabhu](https://github.com/monish-pr/) +- [Khaled](https://github.com/KALs3) +- [Deepali](https://github.com/deepseas07) +- [Ailen Paez](https://github.com/paezailen) +- [Bella Emz] (https://github.com/EmzB) +- [Vatsal K](https://github.com/vatsalkudecha) +- [Mika] (https://github.com/SK-2022) +- [Prakhar Bhatia](https://github.com/prakharbhatia4) +- [vinthara](https://github.com.vinthara) +- [Vaibhavi Gaur](https://github.com/vai14-gaur) +- [Julio Lezcano](https://github.com/lezcano17) +- [Dhriti](https://github.com/Dhriti-singh) +- [Haseeb Ahmad Siddiqui](https://github.com/hasebsiddiqui) +- [Dominic R.](https://github.com/jD2R) +- [Bestin K Benny](https://github.com/bestin015) +- [Chani](https://github.com/ChaniDev) +- [Vaishnavi](https://github.com/vaisrinivasan) +- [Dhruv](https://github.com/Elektrikk) +- [Meet Vansjaliya](https://github.com/meetvansjaliya) +- [Anmoldeep Kaur](https://github.com/anmoldeep1512) +- [JOSE VEDIA](https://github.com/Jose-b-v) +- [Freya Shah](https://github.com/Freya-29) +- [Pasan Pahasara](https://github.com/Pasan-Pahasara) +- [Chethas Pv](https://github.com/chethas7) +- [Cyan Cipher](https://github.com/CyanCipher) +- [kelys] (https://github.com/kelysi) +- [Muskan_Kansal] (https://github.com/crazylot) +- [Aayush Arora](https://github.com/AroraAayush) +- [Michelle Wong](https://github.com/strawberrie68/) +- [Suraj Patra](https://github.com/Suraj-Patra) +- [Mallela D. Vinay](https://github.com/MD571) +- [Mariam Lawal](https://github.com/Maerryham) +- [ADITI-2003](https://github.com/ADITI-2003) +- [Glitchr](https://github.com/Glitchr) +- [Shabeeb PV](https://github.com/shabeebleo) +- [Sakshi](https://github.com/sagupta8399) +- [Krombopulos](https://github.com/krombopulos-eddie) +- [Muskan](https://github.com/Muskan-Git-Code) +- [Urmil Bhavsar](https://github.com/urmil22) +- [Abhay Kshirsagar](https://github.com/AK6263/) +- [Vedant Garhwal](https://github.com/vedant21-2005) +- [Ziabeher Phillips](https://github.com/Zabzx) +- [Pankaj Adhikari](https://github.com/Pankaj809) +- [shashank-gupta](https://github.com/shashank-2310/) +- [bungbloopity](https://github.com/bungbloopity/) +- [Mohammed Arshad](https://github.com/mohammedarshad18) +- [Aleksandr Bochkarev](https://github.com/sash00k/) +- [Dylan Messerly](https://github.com/CodeDTX11) +- [Zhenya Mateyuk](https://github.com/jEUGENEdev/) +- [Soy el Yisus](https://github.com/Jebushdd) +- [Mila](https://github.com/jaetenty) +- [Ayush Shete](https://github.com/ayushete02) +- [Rishabh Gist](https://github.com/rishabhgist) +- [Satyasuranjeet](https://github.com/Satyasuranjeet) +- [Ritwika Das](www.linkedin.com/in/ritwika-das-1510a4207) +- [Anya McDonald](https://github.com/anyahush) +- [Kartik Kumar](https://github.com/yellowterrum) +- [devzohaib](https://github.com/devzohaib) +- [Adanvasconcelos](https://github.com/AdanVasconcelos) +- [Tanmay Bhujade](https://github.com/Tanmaybhujade) +- [Ehmad Saeed](https://github.com/ehmadsaeed) +- [Alex Buser](https://github.com/Albuser) +- [Alex Peain](https://github.com/Alexpeain) +- [Artyom Malyarenko](https://github.com/malaartyom) +- [Snigdha Sinha](https://github.com/snigdhaop) +- [Dibyendu Das](https://github.com/dibyendu02) +- [Megha](https://github.com/SBMegha) +- [Rahul Saha](https://github.com/Rahul10Saha) +- [Dixon Loo](https://github.com/dxnlu) +- [Jose Armando](https://github.com/Armando-Grados) +- [Sathish Kumar Saminathan](https://github.com/satissssss) +- [MAHASAPU](https://github.com/MahasApu) +- [Sarah Mukuti](https://github.com/cesarWrites) +- [Bharat Mishra](https://github.com/BMlookingforaW) +- [Pradyumn](https://github.com/Hannibal404) +- [Utku Çamlıdağ](https://github.com/UtkuCmldg) +- [Suchit Deshmukh](https://github.com/suchitd11) +- [YogatBear](https://github.com/YogatBear) +- [Smart-Peach](https://github.com/Smart-Peach) +- [Siddhant](https://github.com/SiddJ01) +- [Erika Delfino](https://github.com/edelfino11) +- [JSalinas](https://github.com/javier-salinas) +- [Davies Jeffrey](https://github.com/djokhar05) +- [Hailey Steineke](https://github.com/hdsteineke) +- [Abishek Reddy](https://github.com/Abishek-Reddy) +- [Sahil Wankhade](https://github.com/ArcheR1901) +- [Roberto](https://github.com/VespuccioTech) +- [Abdullatif Khayat](https://github.com/Abdullatif-K123) +- [Ayasha](https://github.com/AyashaSikilkar) +- [Varun Kumar](https://github.com/kukutapuvarun) +- [Suchit](https://github.com/Suchitsj12) +- [Safadtm](https://github.com/safadtm) +- [Anandaram](https://github.com/raawwm/first-contributions) +- [Gaby Victoria](https://github.com/GabyVictoria0122) +- [Corentin Gouanvic](https://github.com/Stoaties) +- [Sherly Febrianti](https://github.com/sherlyfebrianti96) +- [Shrimad Bhagwat](https://github.com/Shrimad-Bhagwat) +- [Giuliano Marcus Bianco](https://github.com/giuliano-marcus-bianco) +- [Niket Tiwari](https://github.com/Tiwari-Niket ) +- [Jason Kasari](https://github.com/jkasari) +- [Abhi Patel](https://github.com/AbhiPatel10 ) +- [Marko Vitkovic](https://github.com/MarkoVitkovic) +- [Yatndeep Dubey](https://github.com/Yatndeep ) +- [Autumn Ouellette](https://github.com/Autumn-Ou) +- [Fatin Almalik](https://github.com/Fatin-Almalik) +- [Mohammad Mubaslat](https://github.com/mohammadmubaslat) +- [Arnaduga](https://github.com/arnaduga) +- [PatentLobster](https://github.com/PatentLobster) +- [Varun Prashant Kadkade](https://github.com/varun2430) +- [Aditya Vijay](https://github.com/kiriotheo) +- [Strelets Alexander](https://github.com/Tenkoru) +- [Indranil Saha](https://github.com/saha-indranil) +- [Aman Khatri](https://github.com/Amank927) +- [divya](https://github.com/Divya2k05) +- [Arunima Chaudhuri](https://github.com/tinniaru3005) +- [Domenico Ivan Fortuna](https://github.com/dromex22) +- [Celeste Dubini](https://github.com/celestedubini) +- [Aksheet10](https://github.com/Aksheet10) +- [David Letaw](https://github.com/davidletaw) +- [Sam Erde](https://github.com/SamErde) +- [Danny Bae](https://github.com/danveb) +- [Abhishek Nayak](https://github.com/Abhishek2nayak) +- [Sarthak Patel](https://github.com/sarthakworkspace) +- [Ping](https://github.com/yaein-c) +- [Shubharthi Nath](https://github.com/shubharthinath) +- [Michael Danilov](https://github.com/michaeld03) +- [Hywenklis Rherbert](https://github.com/hywenklis) +- [Biswa Baibhab Subudhi](https://github.com/biswabaibhab007) +- [KacperC](https://github.com/CKacper) +- [Shivam Dangi](https://github.com/shivamdangi7) +- [Nikhil S Kalburgi](https://github.com/nikhilkalburgi) +- [Farhan khan](https://github.com/farhanalws4u) +- [Chandra Sekhar Vinnakota](https://github.com/Iamchandra-3) +- [Jackie Zou](https://github.com/jz0u) +- [Niklas Betke](https://github.com/nikbetke) +- [Vishal Kumar Sinha](https://github.com/VishSinh) +- [Oluwatimilehin Esan](https://github.com/therealtmmy) +- [Satendra Mishra](https://github.com/Satendram) +- [Himanshu Singh](https://github.com/singh-himanshu-16) +- [Deepa Kumari](https://github.com/deepa181) + [Sudip Neupane](https://github.com/sulphuric-sudip) +- [NandiniPokharna](https://github.com/NandiniPokharna) +- [Ruphaa Ganesan](https://github.com/ruphaa) +- [unpluggedsam](https://github.com/unpluggedsam) +- [JasminTajShaik](https://github.com/JasminTajShaik2601) +- [Isaac Mellad Pemberton](https://github.com/Iketyke) +- [Nishant Kumar](https://github.com/thinkwithcode) + [Javier-Bernabe](https://github.com/javbg97) +- [Pragathees](https://github.com/pragasekar) +- [Thomas Jacka](https://github.com/TJacka) +- [rabisha](https://github.com/rabi-1) +- [William-David](https://github.com/William-David) +- [Yash Bellary](https://github.com/bellaryyash23) +- [jeongwoo903](https://github.com/jeongwoo903) +- [Desmond-Fon](https://github.com/Desmond-Fon) +- [Srijanya Durganala](https://github.com/Srijanya.D) +- [TusharPramanick](https://github.com/TusharPramanick) +- [Krishan-Walia](https://github.com/krishanwalia30) +- [Krishna-Kadu](https://github.com/KaiserKadu) +- [Timothy Chua](https://github.com/tdchua) +- [TesseractionCode](https://github.com/TesseractionCode) +- [Jyotishmoy konwar](https://github.com/Jyotishmoy365) +- [Krishan-Kant-11](https://github.com/Krishan-Kant-11) +- [KiriNeTo](https://github.com/KiriNeTo) +- [Enrique Ambrocio](https://github.com/Enrique-Ambrocio) +- [Martin Poncio](https://github.com/lmponcio) +- [Kiran Kuumar Mohanty](https://github.com/theluckiestsoul) +- [Adam Chen](https://github.com/adamchen151) +- [Jonathan G Araya](https://github.com/Jonathana1106) +- [jungchoib](https://github.com/jungchoib) +- [rajdugad](https://github.com/rajdugad) +- [Tarek-Azzazi](https://github.com/tarekazzazi) +- [EricWink](https://github.com/ericwink) +- [Jongkwang131](https://github.com/Jongkwang131) +- [sneha-2510](https://github.com/sneha-2510) +- [javesshhh](https://github.com/javesshhh) +- [KratikJain10](https://github.com/KratikJain10) +- [RogueTM](https://github.com/RogueTMs) +- [jiwonqaz](https://github.com/jiwonqaz) +- [Joshua Varghese](https://github.com/joshvarg) +- [chowonbhin](https://github.com/chowonbhin) +- [mimeosd](https://github.com/mimeosd) +- [Tanmay Pradhan](https://github.com/tanmaypradhan4112) +- [Chirag Goyal](https://github.com/ChiragGoyal98) +- [Animesh Singh](https://github.com/Animesh0764) +- [Jeet Oza](https://github.com/Oza-Jeetkumar-Vishnubhai) +- [Ayush Dodiya](https://github.com/AHD153) +- [KDE030617](https://github.com/KDE030617) +- [starR-ight](https://github.com/StarR-ight) +- [Leigh-Ola](https://github.com/Leigh-Ola) +- [SAket MIshra](https://github.com/saket3199) +- [Yathin](https://github.com/yathinkv) +- [jiunjiun69](https://github.com/jiunjiun69) +- [Etinosa Ekhator](https://github.com/Etinosa22) +- [seongjunyeong](https://github.com/seongjunyeong) +- [Jungmw03](https://github.com/Jungmw03) +- [yutakdv](https://github.com/yutakdv) +- [TurtleJay](https://github.com/TurtleJay) +- [Gaurav Giri](https://github.com/gaurovgiri) + [yaho1231](https://github.com/yaho1231/) + [SuperAngel11](https://github.com/SuperAngel11/) +- [T4EK](https://github.com/T4EK) + [spartan289](https://github.com/spartan289) +- [Ashwin Bhagavatula](https://github.com/ashwinbhagavatula) +- [smdch](https://github.com/smdch) +- [kevins0101](https://github.com/kevins0101) +- [Samarth](https://github.com/samarth777) +- [Abidi-S](https://github.com/Abidi-S) +- [Sandeep Nayak](https://github.com/SANDEEP-NAYAK) +- [Tarif Higolja](https://github.com/mr-hingolja) +- [Sahil Ahmed](https://github.com/PirateOfAndaman) +- [youngjun1227](https://github.com/youngjun1227) +- [Preston Harms](https://github.com/R3dPnd) +- [kaushalgosaliya5](https://github.com/kaushalgosaliya5) +- [Taaki](https://github.com/taaki2311) +- [kaushalgosaliya5](https://github.com/kaushalgosaliya5) +- [Jo-SungJun](https://github.com/Jo-SungJun) +- [Samvardhan](https://github.com/samvardhan777) +- [Iyyappan R](https://github.com/dvrsaran) +- [Rohit Yadav](https://www.linkedin.com/in/rohit-yadav-0852481b2/) +- [Tyler Martin @HeyTylerMartin](https://github.com/HeyTylerMartin) +- [Arshad Khan](https://github.com/The-Arshad-Khan) +- [Ricardo Fontenla](https://github.com/ricfontenla) +- [M3tal M0nk3y](https://github.com/M3talM0nk3y) +- [Akshay Soni](https://github.com/akshaysoni10) +- [Denis Koshelev](https://github.com/kshpdr) +- [youngjun1227](https://github.com/youngjun1227) +- [Ankit Gupta](https://github.com/Ankit-Gupta0) +- [Vinci Liu](https://github.com/vinciliu30) +- [William Larsen](https://github.com/thewildwilli) +- [Higor Chagas](https://github.com/HigorChagas) +- [Matty Charitan](https://github.com/Matty-charitan) +- [Piyush Raviraj](https://github.com/Piyushraviraj2611) +- [Dwayne Gibbs](https://dwaynegibbs.net) +- [AVINASH YADAV](https://github.com/Happylife10) +- [Joshua Knorz](https://github.com/JoshKn) +- [Tri Pham](https://github.com/TriMPham98) +- [Vishvesh Pratap Singh](https://github.com/Vish221) +- [iParadocx](https://github.com/iParadocx) +- [Aditya Pudaruth](https://github.com/Aditya-Pudaruth) +- [Aman Choudhary](https://github.com/aman-choudhary1) +- [Dmitrii Sidenko](https://github.com/DmSide) +- [Santiago Urbano](https://github.com/sanurb) +- [સ્મિત કાછડીયા](https://github.com/smeekas) +- [Rao Khuram Shahzad](https://github.com/KhuramShahzad-5335) +- [Nikita Mahamuni](https://github.com/Nikita0509/) +- [Yash Deharia](https://github.com/yashdeharia) +- [Akshay Kudalkar](https://github.com/Akshaykk12) +- [Shravan Seth](https://github.com/ShravanSeth) +- [Shaavi Gupta](https://github.com/ShaaviGupta) +- [Sai Rohit](https://github.com/sairohit360) +- [James Anyalewechi](https://github.com/jamesgotech) +- [Dibakar Upadhyaya](https://github.com/Dibakar01) +- [Johan Kreivi](https://github.com/0h4y) +- [Gaurav Patil](https://github.com/GauravPatil8778) +- [Suryajith Ms](https://github.com/Suryajith32) +- [Ananya Agarwal](https://github.com/ananyaa01) +- [Ali El-Shamy](https://github.com/elshali) +- [Rami Shawwa](https://edbtz.com) +- [Chhaganlaal](https://github.com/Chhaganlaal) +- [Chandra Kiran](https://github.com/chandra-kiran1) +- [Aryan Thakore](https://github.com/Aryan1982) +- [Hamza Nehme](https://github.com/hnehme99) +- [Chris Boles](https://github.com/cboles80) + [Dev-it-a-dev](https://github.com/dev-it-a-dev) +- [Alexis Gonzalez](https://github.com/Alex-is-Gonzalez) +- [Shreyash Gupta](https://github.com/shreyash2610) +- [Manish Kumar](https://github.com/Manish-kumar-DEV) +- [Nora Aguirre](https://github.com/nora-programadora) +- [Guna Abola](https://github.com/g-abola) +- [Shabana Naik](https://github.com/ShabanaNaik) +- [Alex Sanzhanov](https://github.com/Sanzhanov) +- [Aecio Neto](https://github.com/aecio-neto) +- [Neha Jadhav](https://github.com/jadhavneha) +- [Kjell-Magnus](https://github.com/kmgrime) +- [Giorgio Menini](https://github.com/Menno00) +- [Suhas Katrahalli](https://github.com/Suhas2002) +- [Jivan Dandapat](https://github.com/jivandandapat) +- [Deepali Sayana](https://github.com/deepseas07) +- [André Carvalhal](https://github.com/ANDREC1986) +- [Rahul Saha](https://github.com/Rahul10Saha) +- [Vishal](https://github.com/VishalPraneeth) +- [Sadiq Siraj Ebrahim](https://github.com/sadiqebrahim) +- [Wajid Ali Tabassum](https://github.com/wajidalitabassum143) +- [Manvendra Prasad](https://github.com/Manv3ndra) +- [Abhinav Chaudhary](https://github.com/lan10rn) +- [Saumya Upadhyay](https://github.com/Saumyaup11) +- [Pranava Kumar Mishra](https://github.com/SatayS) +- [yogesh](https://github.com/yogesh-0911) +- [paras](https://github.com/paras9192) +- [LaElijah](https://github.com/LaElijah) +- [Shivansh Guleria](https://github.com/ShivanshGuleria) +- [Swaraj](https://github.com/swarajzz) +- [Franklin Mensah](https://github.com/fiificode) +- [Bright Odey](https://github.com/starburn-hub) +- [Rahul chaurasiya](https://github.com/Rahul-chaurasiya?) +- [Anugrah Rachman](https://github.com/kidomega-byte/) +- [Hector Quemada](https://github.com/hdquemada) +- [Maheen Saleh](https://github.com/maheensaleh) +- [Sebastian Wu](https://github.com/sebswU) +- [Sofie Borchgrevink](https://github.com/sofieborchgrevink) +- [Karanjot Singh](https://karanjot.vercel.app) +- [Sachit Khadka](https://github.com/Sachit56/first-contributions) +- [SHUBHAM PATIDAR ](https://www.linkedin.com/in/shubham-patidar-98ba5b148) +- [Apurv Tiwari](https://github.com/Mahakal0123) +- [Ajith R Thampi](https://github.com/ajithrthampi) +- [Dhanesh Phulphagar](https://github.com/darayn) +- [R3DRUN3](https://github.com/R3DRUN3) +- [Dhanesh Phulphagar](https://github.com/darayn) +- [Rishi Singh](https://github.com/mrsingh-rishi) +- [Arpan Adlakhiya](https://github.com/mrr0b0t-0x1) +- [Nia Ahmed](https://github.com/technialogy) +- [Bikash yadav](https://github.com/bikashydv) +- [Sowmya S](https://github.com/sowmya-s-26) +- [Andres Emedan](https://github.com/andresemedan) +- [Julian Macioce](https://github.com/JMacioce) +- [Prerit Agrawal](https://github.com/preritagrawal06) +- [Chiranjit Debnath](https://github.com/tomtanner) +- [JSTNSNE](https://github.com/JSTNSNE) +- [JSTNSNE](https://github.com/JSTNSNE) + [ J Sripranya](https://github.com/Sripranya) + [Karthinivash S R](https://github.com/karthinivashSR) +- [Aimee T](https://github.com/aimeetacchi) +- [Abhijith H](https://github.com/Abhijith-H13) +- [Abhighyaa](https://github.com/Abhighyaa) +- [Kaif Shakeel] (https://github.com/KaifShakeel76) +- [Alfeu Xerinda](https://githhub.com/Hard-007) +- [Chandan Singh](https://githhub.com/chandan8678) +- [Sangam Singh](https://githhub.com/codersangam) +- [Shubhanshu Gupta](https://github.com/Gptshubh) +- [shaileshb](https://github.com/shaileshhb) +- [Victor F.](https://github.com/victorfyonemoto) +- [Andre Müller](https://github.com/Amueller36) +- [duzzysroad](https://github.com/duzzysroad) +- [Srivathsan V](https://github.com/Srivathsan-V) +- [TJ Albertson](https://github.com/TJ-Albertson) +- [Ruthik Jadhav](https://github.com/Ruthik130201) +- [Vladimir Cvejanov](https://github.com/VladenCode) +- [Suman Raj](https://github.com/the-suman) +- [Megan Moulos](https://github.com/meganmoulos/) +- [Peter Hansteen](https://github.com/pitrh) +- [Thales Carlesso](https://github.com/ThalesIanMendes) +- [Teju_1212](https://github.com/teju_1212) +- [Aaron Geo Binoy](https://github.com/aarongeo1) +- [Rakshit Gupta](https://github.com/rakshitgupta23) +- [Sameera Dissanayaka](https://github.com/ceylonprogrammer) +- [Chirag Chakraborty](https://github.com/noobchirag69) +- [Aditya Singh](https://github.com/second007) +- [Aman Sharma](https://github.com/amansharma703) +-[Muhammed Fahad v k ](https://github.com/fahadvillan6) +- [Siddharth Bhardwaj](https://github.com/TheUnofficialGod) +- [Jesse Gerbrandt](https://github.com/Jgerbrandt) +- [Aditya Singhal](https://github.com/adityaacse) +- [Utsav Akash Naskar](https://github.com/Utsav1999) +- [Anish Doshi](https://github.com/doshianish8) +- [Saurabh Sinha](https://github.com/sinhasaurabh3104) +- [Girish Nair](https://github.com/javagirish) +- [Prathamesh Sable](https://github.com/prathameshks) +- [Martarion](https://github.com/Martarion-Code) +- [Martins Ngene](https://github.com/Martinsngene) +- [vishal dhavale](https://github.com/vishu1893) +- [Subhajit Mahata](https://github.com/subhajitkp007) +- [Yashvardhan Agnihotri](https://github.com/25011908vardhan) +- [Priyadarshini Sharma](https://github.com/PriyadarshiniSharma) +- [luv sharma](https://github.com/luvsharmag) +- [Raj Patra](https://github.com/raj-patra) +- [Alan Flores](https://github.com/AlanF20) +- [Aaryan Singh](https://github.com/Aaryan376) +- [Arjava Tripathi](https://github.com/ArjavaTripathi) +- [Amit Roy](https://github.com/amitroy-thedev) +- [Siddhi Khade](https://github.com/SiddhiKhade) +- [Pavanteja](https://github.com/Pavanteja17) +- [Shaurya Gupta](https://github.com/Shaurya50211) +- [shrthk-7](https://github.com/shrthk-7) +- [Yash Thakur](https://github.com/philomathaf) +- [Rajarshi Bhattacharya](https://github.com/rajarshi023) +- [Adnan Ahmed](https://github.com/fidato818) +- [Mandar Deshmukh](https://github.com/mandarsd18) +- [Azzarox](https://github.com/azzarox) +- [Aman Badone](https://github.com/amanbadone) +- [Rishabh yaduwanshi](https://github.com/rishabhyaduwanshi) +- [Suraj Patel](https://github.com/Surajpatel2003) +- [Raghav Krishan Kedia](https://github.com/Raghav-Kedia) +- [WhiteR4ven](https://github.com/WhiteR4ven) +- [Aviraj Saxena](https://github.com/theavirajsaxena) +- [Allesandria Bugatti](https://github.com/Abargallo19) +- [shrthk-7](https://github.com/shrthk-7) +- [Dharmik Nadiyapara](https://github.com/Dharmik-0) +- [Shivodit Gill](https://github.com/HotDogEnemy) +- [Shantanu29kumar](https://github.com/Shantanu29kumar) +- [IsaacNewTom](https://github.com/IsaacNewTom) +- [Jai-Marothiya](https://github.com/Jai-Marothiya) +- [Ahan Bandyopadhyay](https://github.com/ahanban15) +- [Monodeep-Das](https://github.com/Monodeep-Das) +- [Sai Manoj Etcherla](https://github.com/saimanoj22) +- [Adam Anderson](https://github.com/Adam-E-Anderson) +- [Mayank Agrawal](https://github.com/Mayank30-creator) +- [Aman Kumar Pandey](https://github.com/amanpandey2101) +- [Patil 2104](https://github.com/patil2104) +- [HiTShiroya](https://github.com/HiTShiroya) +- [Supriadi](https://github.com/obocloud) + \ No newline at end of file diff --git a/LICENSE b/LICENSE new file mode 100644 index 00000000000..6f3f30997c9 --- /dev/null +++ b/LICENSE @@ -0,0 +1,21 @@ + MIT License + + Copyright (c) 2016 - present Roshan Jossey + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all +copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. diff --git a/README.md b/README.md new file mode 100644 index 00000000000..383fdbba9be --- /dev/null +++ b/README.md @@ -0,0 +1,207 @@ +[![Open Source Love](https://firstcontributions.github.io/open-source-badges/badges/open-source-v1/open-source.svg)](https://github.com/firstcontributions/open-source-badges) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +#### _Read this in [other languages](translations/Translations.md)._ + +[Shqip](translations/README.al.md) +[Uzbek language](translations/README.uz.md) +[Azərbaycan dili](translations/README.aze.md) +[বাংলা](translations/README.bn.md) +[Bulgarian](translations/README.bg.md) +[Português](translations/README.pt_br.md) +[Català](translations/README.ca.md) +[中文 (Simplified)](translations/README.zh-cn.md) +[Czech](translations/README.cs.md) +[Deutsch](translations/README.de.md) +[Dansk](translations/README.da.md) +[العربية](translations/README.eg.md) +[Española](translations/README.es.md) +[Française](translations/README.fr.md) +[Galego](translations/README.gl.md) +[Ελληνικά](translations/README.gr.md) +[ქართული](translations/README.ge.md) +[Magyar](translations/README.hu.md) +[Bahasa Indonesia](translations/README.id.md) +[עִברִית](translations/README.hb.md) +[हिंदी/ગુજરાતી/मराठी/മലയാളം/ಕನ್ನಡ/తెలుగు/छत्तीसगढ़ी/বাংলা/தமிழ்](translations/Translations.md) +[தமிழ்](translations/README.ta.md) +[فارسی](translations/README.fa.md) +[پښتو](translations/README.pus.md) +[Italiano](translations/README.it.md) +[日本語](translations/README.ja.md) +[සිංහල](translations/README.si.md) +[Kiswahili (Kenya)](translations/README.kws.md) +[한국어 한국어](translations/README.ko.md) +[Lietuvių kalba](translations/README.lt.md) +[Limba Română Limba Română](translations/README.ro.md) +[မြန်မာ](translations/README.mm_unicode.md) +[Македонски](translations/README.mk.md) +[Español de México](translations/README.mx.md) +[Bahasa Melayu / بهاس ملايو‎ / Malay](translations/README.my.md) +[Dutch](translations/README.nl.md) +[Norsk](translations/README.no.md) +[नेपाली](translations/README.np.md) +[Wikang Filipino](translations/README.tl.md) +[English (Pirate)](translations/README.en-pirate.md) +[اردو](translations/README.ur.md) +[Polski](translations/README.pl.md) +[Português (Portugal)](translations/README.pt-pt.md) +[Русский язык](translations/README.ru.md) +[عربى](translations/README.ar.md) +[Svenska](translations/README.se.md) +[Slovenčina](translations/README.slk.md) +[Slovenščina](translations/README.sl.md) +[ภาษาไทย](translations/README.th.md) +[Türkçe](translations/README.tr.md) +[中文(Traditional)](translations/README.zh-tw.md) +[Українська](translations/README.ua.md) +[Tiếng Việt](translations/README.vn.md) +[Zulu (South Africa)](translations/README.zul.md) +[Afrikaans (South Africa)](translations/README.afk.md) +[Igbo (Nigeria)](translations/README.igb.md) +[Yoruba (Nigeria)](translations/README.yor.md) +[Hausa (Nigeria)](translations/README.hau.md) +[Latvia](translations/README.lv.md) +[Suomeksi](translations/README.fi.md) +[Беларуская мова](translations/README.by.md) +[Српски](translations/README.sr.md) +[Қазақша](translations/README.kz.md) +[Bosanski](translations/README.bih.md) +[Bosanski](translations/README.bih.md) +[Hrvatski](translations/README.hr.md) +[پښتو](translations/README.ps.md) + +# First Contributions + +This project aims to simplify and guide the way beginners make their first contribution. If you are looking to make your first contribution, follow the steps below. + +_If you're not comfortable with command line, [here are tutorials using GUI tools.](#tutorials-using-other-tools)_ + + +fork this repository + +#### If you don't have git on your machine, [install it](https://help.github.com/articles/set-up-git/). + +## Fork this repository + +Fork this repository by clicking on the fork button on the top of this page. +This will create a copy of this repository in your account. + +## Clone the repository + +clone this repository + +Now clone the forked repository to your machine. Go to your GitHub account, open the forked repository, click on the code button and then click the _copy to clipboard_ icon. + +Open a terminal and run the following git command: + +``` +git clone "url you just copied" +``` + +where "url you just copied" (without the quotation marks) is the url to this repository (your fork of this project). See the previous steps to obtain the url. + +copy URL to clipboard + +For example: + +``` +git clone https://github.com/this-is-you/first-contributions.git +``` + +where `this-is-you` is your GitHub username. Here you're copying the contents of the first-contributions repository on GitHub to your computer. + +## Create a branch + +Change to the repository directory on your computer (if you are not already there): + +``` +cd first-contributions +``` + +Now create a branch using the `git switch` command: + +``` +git switch -c your-new-branch-name +``` + +For example: + +``` +git switch -c add-alonzo-church +``` + +## Make necessary changes and commit those changes + +Now open `Contributors.md` file in a text editor, add your name to it. Don't add it at the beginning or end of the file. Put it anywhere in between. Now, save the file. + +git status + +If you go to the project directory and execute the command `git status`, you'll see there are changes. + +Add those changes to the branch you just created using the `git add` command: + +``` +git add Contributors.md +``` + +Now commit those changes using the `git commit` command: + +``` +git commit -m "Add your-name to Contributors list" +``` + +replacing `your-name` with your name. + +## Push changes to GitHub + +Push your changes using the command `git push`: + +``` +git push -u origin your-branch-name +``` + +replacing `your-branch-name` with the name of the branch you created earlier. + +
+ If you get any errors while pushing, click here: + +- ### Authentication Error + 
remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead.
+  remote: Please see https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ for more information.
+  fatal: Authentication failed for 'https://github.com//first-contributions.git/'
+ Go to [GitHub's tutorial](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account) on generating and configuring an SSH key to your account. + +
+ +## Submit your changes for review + +If you go to your repository on GitHub, you'll see a `Compare & pull request` button. Click on that button. + +create a pull request + +Now submit the pull request. + +submit pull request + +Soon I'll be merging all your changes into the main branch of this project. You will get a notification email once the changes have been merged. + +## Where to go from here? + +Congrats! You just completed the standard _fork -> clone -> edit -> pull request_ workflow that you'll often encounter as a contributor! + +Celebrate your contribution and share it with your friends and followers by going to [web app](https://firstcontributions.github.io/#social-share). + +You could join our slack team if you need any help or have any questions. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Now let's get you started with contributing to other projects. We've compiled a list of projects with easy issues you can get started on. Check out [the list of projects in the web app](https://firstcontributions.github.io/#project-list). + +### [Additional material](additional-material/git_workflow_scenarios/additional-material.md) + +## Tutorials Using Other Tools + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [GitHub Desktop](gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/additional-material/Things a non Programmer can do.md b/additional-material/Things a non Programmer can do.md new file mode 100644 index 00000000000..46a4326e8ab --- /dev/null +++ b/additional-material/Things a non Programmer can do.md @@ -0,0 +1,117 @@ +# Things a non Programmer can do +## Start listening + +Everything in open source involves other people. +You're looking to join a team, and that means understanding the community and how it works. +Walking in to a project and saying "Hi, here's what I think this project should be doing" is usually not taken as a good thing. +Some projects may welcome that sort of approach, but if the project has been running a while, the chances of that attitude being embraced are small. +**Listening is the best way to know what the project needs.** + +1. **Join a mailing list**: For many projects, the mailing list is the main conduit of communication about the development of the project. +On large projects, there are many mailing lists to choose from. +For example, the PostgreSQL project has no fewer than 12 user-oriented lists and six developer lists on its mailing list page. +I suggest you follow the main user-oriented list and the core developer list in which to start listening. + +2. **Follow a blog**: Blogs maintained by core developers often give information about what's coming up in future releases, +and what it's taken to get there. A planet site aggregates news and blog entries from many sources related to the project. +If there is a planet site, like planet.gnome.org or planet.mysql.com, start there. Just search Google for "planet ." + +3. **Join an IRC channel**: Many open source projects have dedicated Internet relay chat (IRC) channels where developers and users hang out to discuss problems and development. +Check the project's website for the details of what the channel is called and what IRC network it's found on. + +**Work with Tickets** +Code is the heart of any open source project, but don't think that writing code is the only way to contribute. +Maintenance of code and the systems surrounding the code often are neglected in the rush to create new features and to fix bugs. +Look to these areas as an easy way to get your foot into a project. +Most projects have a publicly visible trouble ticket system, linked from the front page of the project's website and included in the documentation. +It's the primary conduit of communication between the users and the developers. Keeping it current is a great way to help the project. +You may need to get special permissions in the ticketing system, which most project leaders will be glad to give you when you say you want to help clean up the tickets. + +4. **Diagnose a bug**: Bugs are often poorly reported. +Diagnosing and triaging a bug can help save the developers save time with the legwork of figuring out the specifics of the problem. +If a user reported, "The software doesn't work when I do X," spend some time to figure out the specifics of what goes into that problem. +Is it repeatable? Can you create a set of steps to cause the problem repeatedly? Can you narrow down the problem, such as only happening on one browser but not another, or one distro but not another? + +Even if you don't know what causes the problem, the effort you put into narrowing down the circumstances makes it easier for someone else to fix it. +Whatever you discover, add it to the ticket in the bug system for all to see. + +5. **Close fixed bugs**: Often bugs are fixed in the codebase but tickets reported about them don’t get updated in the ticketing system. +Cleaning up this cruft can be time-consuming, but it's valuable to the whole project. + +Start by querying the ticket system for tickets older than a year and see if the bug still exists. +Check the project's release change log to see if the bug was fixed and can be closed. +If it's known to be fixed, note the version number in the ticket and close it. + +Try to recreate the bug with the latest version of the software. +If it can't be recreated with the latest version, note that in the ticket and close it. +If it still exists, note that in the ticket as well and leave it open. + +Working with Code +Programmers of all experience levels can help with the code in the project. +Don't think that you have to be a coding genius to make real contributions to your favorite project. + +If your work involves modification to the code, investigate the method that the project uses for getting code from contributors. +Each project has its own workflow, so ask about how to do it before you set out to submit code. + +For example, the PostgreSQL project is very rigorous in its process: Code modifications are sent in patch form to a mailing list where core developers scrutinize every aspect of the change. On the other end is a project like Parrot where it's easy to get commit privileges to the codebase. If the project uses GitHub, there may be a workflow that uses the pull request feature of GitHub. No two projects are the same. + +Whenever you modify code, make sure that you act as a responsible member of the community and keep your code style to match the rest of the codebase. The code you add or modify should look like the rest. You might not like the bracing style or the handling of spaces for indentation, but it's rude to submit a code change that doesn't match the existing standards. It's the same as saying "I don't like your style, and I think mine is better, so you should do it my way." + +6. **Test a beta or release candidate**: Any project that's designed to run on multiple platforms can have all sorts of portability problems. +When a release approaches and a beta or release candidate is published, the project leader hopes that it will be tested by many different people on many different platforms. +You can be one of those people and help ensure that the package works on your platform. + +Typically you only need to download, build, and test the software, but the value to the project can be huge if you're on an uncommon distribution or hardware. +Just reporting back that the build and test works helps the project leaders know that the impending release is solid. + +7. **Fix a bug**: This is usually where contributors wanting to get working on code start. +It’s simple: Find an interesting-sounding bug in the ticket system and try to fix it in the code. +Document the fix in the code if it's appropriate. +It's a good idea to add a test to the test suite to test the spot of code you fixed; some projects require bug fixes to include tests. Keep notes as you poke around this unfamiliar codebase. Even if you aren't able to fix the bug, document in the ticket what you discovered as part of the fix attempt. What you find helps those who come after you. + +8. **Write a test**: Most projects have a test suite that tests the code, but it's hard to imagine a test suite that couldn't have more tests added to it. +Use a test coverage tool like gcov for C, or Devel::Cover for Perl to identify areas in the source code that aren't tested by the test suite. +Then, add a test to the suite to cover it. + +9. **Silence a compiler warning**: The build process for many C-based projects often spew the odd compiler warning flag to the screen. +These warnings are usually not indicators of a problem, but they can look like it. +Having too many warnings can make the compiler sound like it's crying wolf. +Check to see if the code could actually be hiding a bug.If not, modifying the source to silence helps to hide these false positives. + +10. **Add a comment**: +When you're digging through the code, you may find some spots that are confusing. +Chances are if you were confused, others will be as well. Document them in the code and submit a patch. +Work with Documentation +Documentation is typically the part of a project that gets short shrift. +It also can suffer from having been written from the point of view of those who are familiar with the project, rather than through the eyes of someone just getting into it. +If you've ever read docs for a project where you think, "It's as though this manual expects that I already know how to use the package," you know what I'm talking about. +Often a set of fresh eyes can point out deficiencies in the documentation that those close to the project don't notice. + +11. **Create an example**: There is no project that has too many how-to examples. +Whether it's a web API, a library of routines, a GUI app like Gimp or a command line tool, +a good example of proper usage can more clearly and quickly explain proper usage of software than pages of documentation. +For an API or library, create an example program that uses the tool. This could even be extracted from code you've written, trimmed down to the bare necessities. +For a tool, show real-world examples of how you've used it in your daily life. If you’re visually oriented, +consider creating a screen-capture of an important process, such as how to install the application. + +Work with Community +Open source is only partly about code. Community makes open source work. Here are ways you can help build it up. + +12. **Answer a question**: The best way to help build the community is by helping others. +Answering a question, especially from someone who is just getting their feet wet, is crucial to helping the project grow and thrive. +The time you take to help a beginner, even if they're asking a question where you could easily throw back a quick "RTFM," pays off down the road in getting another active member of the community. +Everyone starts out somewhere, and projects need a constant inflow of people if they're to stay vital. + +13. **Write a blog post**: +If you've got a blog, write about your experiences with the project that you're using. +Tell about a problem you faced using the software and what you did to solve it. +You'll be helping in two ways, both by helping keep the project on the minds of others around you, +and by creating a record for anyone else who has your problem in the future and searches the web for the answer. +(A blog of your technical adventures is also an excellent way to show real-world experience with the software in question next time you go hunting for a job using it.) + +14. **Improve a website**: +If you've got skills in web design and can help improve the website, and thus the public-facing image of the project, that's time well spent. +Perhaps the project could use a graphic overhaul, or a logo to identify the project. +These may be skills lacking in the community. I know I'd love it if I could get some graphic design help on my projects' websites. + +Most of all, listen to what people around you discuss. See if you can recognize a pressing need. For instance, recently on the Parrot developers' mailing list, it was decided to use GitHub as the trouble ticket system, abandoning the old Trac installation they had. Some people were against the move because there was no way to convert the tickets to GitHub's system. After a day of back and forth arguing, I piped up and said "How about if I write a converter?" People were thrilled at the idea. I spent the time to write a conversion program for the 450+ tickets, so we lost none of our ticket history. It was a great success. I got to pitch in, and the core developers stayed focused on the business of working on Parrot. diff --git a/additional-material/git_workflow_scenarios/Useful-links-for-further-learning.md b/additional-material/git_workflow_scenarios/Useful-links-for-further-learning.md new file mode 100644 index 00000000000..81bf3e9df0e --- /dev/null +++ b/additional-material/git_workflow_scenarios/Useful-links-for-further-learning.md @@ -0,0 +1,45 @@ +# Useful Links + +This document is dedicated to all the tips and tricks websites, blog posts, and helpful sites that make our lives easier. They are a great reference to serve all of our needs, be it a beginner or an expert. This page should act as an index of all those useful links that would help everybody who is new in the open-source domain or someone who wants to learn more. + +## The List +1. [Interactive tutorial to git](https://try.github.io) +2. [Youtube: Git and GitHub for Beginners by freecodecamp](https://www.youtube.com/watch?v=RGOj5yH7evk) +3. [git - the simple guide](http://rogerdudler.github.io/git-guide/) +4. [On undoing, fixing, or removing commits in git](http://sethrobertson.github.io/GitFixUm/fixup.html) +5. [Git and GitHub tutorial translated to many languages](https://github.com/Roshanjossey/first-contributions) +6. [Merge Conflicts](https://www.git-tower.com/learn/git/ebook/en/command-line/advanced-topics/merge-conflicts) +7. [Resolving Merge Conflicts](https://githowto.com/resolving_conflicts) +8. [Basics of Git - The Simple Quick Start Guide](https://blog.praveen.science/basics-of-git-the-quick-start-guide/) +9. [Git Standards followed in our way of Spotify Agile Methodology](https://blog.praveen.science/git-standards-followed-in-our-way-of-spotify-agile-methodolgy/) +10. [Git Shortcuts](https://blog.praveen.science/git-shortcuts/) +11. [Official Git cheat sheet in many languages](https://services.github.com/on-demand/resources/cheatsheets) +12. [Git cheat sheet from Tower](https://www.git-tower.com/learn/cheat-sheets/git) +13. [Common Git Problems](https://www.codementor.io/citizen428/git-tutorial-10-common-git-problems-and-how-to-fix-them-aajv0katd) +14. [Git Rebase](https://blog.gitprime.com/git-rebase-an-illustrated-guide/) +15. [Beginner's Guide to Rebasing and Squashing](https://github.com/servo/servo/wiki/Beginner%27s-guide-to-rebasing-and-squashing) +16. [Git Cheatsheet that shows correlations between commands and files](http://ndpsoftware.com/git-cheatsheet.html) +17. [How to contribute](https://opensource.guide/how-to-contribute/) +18. [Getting started with Open Source](https://github.com/OpenSourceHelpCommunity/Getting-Started-With-Contributing-to-Open-Sources) +19. [How to contribute](https://github.com/freeCodeCamp/how-to-contribute-to-open-source) +20. [Atlassians Git Tutorials](https://www.atlassian.com/git) +21. [Pull request reviews](https://help.github.com/articles/about-pull-request-reviews/) +22. [Another Interactive tutorial for git](https://learngitbranching.js.org/) +23. [Git commandline cheat-sheet](https://gist.github.com/davfre/8313299) +24. [Programming Books](https://github.com/EbookFoundation/free-programming-books) +25. [E-Book of professional tip and secrets](https://goalkicker.com/GitBook/GitProfessionalTipsSecrets.pdf) +26. [tutorial about simple rules of become git professional](https://medium.freecodecamp.org/follow-these-simple-rules-and-youll-become-a-git-and-github-master-e1045057468f) +27. [A Note About Git Commit Messages](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) +28. [5 Useful Tips For A Better Commit Message](https://thoughtbot.com/blog/5-useful-tips-for-a-better-commit-message) +29. [Version Control using Git](https://ourcodingclub.github.io/2017/02/27/git.html) +30. [Version Control with Git](https://www.udacity.com/course/version-control-with-git--ud123) +31. [Audit the Coursera course from Google](https://www.coursera.org/learn/introduction-git-github) +32. [Using Version Control in VS Code](https://code.visualstudio.com/docs/editor/versioncontrol) +33. [Git vs Github: What's the Difference and How to Get Started with Both](https://kinsta.com/knowledgebase/git-vs-github/) +34. [Hello World Github guides](https://guides.github.com/activities/hello-world/) +35. [How To Use GitHub](https://www.edureka.co/blog/how-to-use-github/) +36. [10 Days of Git and Github](https://github.com/Asabeneh/10-days-of-git-and-github) +37. [Keyboard shortcuts for Github](https://docs.github.com/en/get-started/using-github/keyboard-shortcuts) +38. [Complete Git and GitHub Tutorial by Kunal Kushwaha](https://www.youtube.com/watch?v=apGV9Kg7ics&ab_channel=KunalKushwaha) +39. [Git workflow Cheat Sheet](https://drive.google.com/uc?export=download&id=1QPRh5YmqQm4DFfitelPYlBTWC2I6tTTM) +Keep adding more links, that you find helpful. diff --git a/additional-material/git_workflow_scenarios/additional-material.md b/additional-material/git_workflow_scenarios/additional-material.md new file mode 100644 index 00000000000..5dc1249086b --- /dev/null +++ b/additional-material/git_workflow_scenarios/additional-material.md @@ -0,0 +1,50 @@ +# Additional information + +We assume that you have already finished with the basic tutorial before coming here. This document will give you some additional information about advanced Git techniques. + +### [Amending a commit](amending-a-commit.md) +This document provides information about how to amend a commit on the remote repository. +> Use this when you need to adjust a commit you made. + +### [Configuring git](configuring-git.md) +This document provides information about how to configure user details and other options in git. +> Use this to better control your git configurations. + +### [Keeping your fork synced with the repository](keeping-your-fork-synced-with-this-repository.md) +This document provides information about how to keep your forked repository up-to-date with the base repository. This is important, as hopefully you and many others will contribute to the project. +> Follow these steps if your fork doesn't have any changes in parent repository. + +### [Moving a Commit to a different Branch](moving-a-commit-to-a-different-branch.md) +This document provides information about how to move a Commit to another Branch. +> Take these steps to move a commit to another branch. + +### [Removing a File](removing-a-file.md) +This document provides information about how to remove a file from your local repository. +> Follow these steps to learn how to remove a file prior to a commit + +### [Removing a branch from your repository](removing-branch-from-your-repository.md) +This document provides information about how to delete a branch from your repository. +> Only do these steps after your pull request get's merged. + +### [Resolving Merge Conflicts](resolving-merge-conflicts.md) +This document provides information about how to resolve merge conflicts. +> Take these steps to resolve the annoying merge conflicts. + +### [Reverting a commit](reverting-a-commit.md) +This document provides information about how to revert a commit on the remote repository. It will come in handy in case you need to undo a commit that has already been pushed to Github. +> Take these steps if you want to reverse a commit. + +### [Squashing Commits](squashing-commits.md) +This document provides information about how to squash commits with an interactive rebase. +> Use this if you want to open a PR in an open source project and the reviewer asks you to squash every commit into one, with an informative commit message. + +### [Undo-ing a local commit](undoing-a-commit.md) +This document provides information about how to undo a commit on your local repository. This is what you need to do when you feel you've messed up your local repository and wish to reset the local repository. +> Take these steps if you want to undo/reset a local commit. + +### [Useful Links](Useful-links-for-further-learning.md) +This document is dedicated to all the tips and tricks websites, blog posts, and helpful sites that make our lives easier. They are a great reference to serve all of our needs, be it a beginner or an expert. This page should act as an index of all those useful links that would help everybody who is new in the open-source domain or someone who wants to learn more. + +### [Creating a .gitignore file](creating-a-gitignore-file.md) +This document explains what a .gitignore file does, why to use it and how to create a .gitignore file. This file is used in almost all git projects. It helps commit only necessary files to git. + diff --git a/additional-material/git_workflow_scenarios/amending-a-commit.md b/additional-material/git_workflow_scenarios/amending-a-commit.md new file mode 100644 index 00000000000..6ae5608c38d --- /dev/null +++ b/additional-material/git_workflow_scenarios/amending-a-commit.md @@ -0,0 +1,48 @@ +# Amending a Commit + +What if you commit a change to your remote repository only to realize later that you have a typo in the commit message or you forgot to add a line in your most recent commit. +How do you edit that? This is what this tutorial covers. + +## Changing a recent commit message after you have pushed to Github. +To do this without opening a file: +* Type in the ```git commit --amend -m "followed by your new commit message"``` +* Run ```git push origin ``` to commit the changes to the repository. + +Note: If you type in just ```git commit --amend```, your text editor would open up prompting you to edit the commit message. +Adding the ``-m`` flags prevents it. + +## Modifying on a single commit + +So, what if we forgot to make a minor change to a file like changing a single word and we have already pushed the commit to our remote repository? + +To illustrate here is a log of my commits: +``` +g56123f create file bot file +a2235d updated contributor.md +a5da0d modified bot file +``` +Let's say I forgot to add a single word to the bot file + +There are 2 ways to go about this. The first is to have an entirely new commit that contains the change like so: +``` +g56123f create file botfile +a2235d updated contributor.md +a5da0d modified botfile +b0ca8f added single word to botfile +``` +The second way is to amend the a5da0d commit, add this new word and push it to Github as one commit. +The second sounds better since it is just a minor change. + +To achieve this, we would do the following: +* Modify the file. In this case, I will modify the botfile to include the word I omitted previously. +* Next, add the file to the staging area with ```git add ``` + +Usually after adding files to the staging area, the next thing we do is git commit -m "our commit message" right? +But since what we want to achieve here is to amend the previous commit, we would instead run: + +* ```git commit --amend``` + This would then bring up the text editor and prompt you to edit the message. You can decide to leave the message as it was before or change it. +* Exit the editor +* Push your changes with ```git push origin ``` + +That way, both changes would be in one single commit. diff --git a/additional-material/git_workflow_scenarios/check-commit-log.md b/additional-material/git_workflow_scenarios/check-commit-log.md new file mode 100644 index 00000000000..0a366e0603d --- /dev/null +++ b/additional-material/git_workflow_scenarios/check-commit-log.md @@ -0,0 +1,20 @@ +# Check commit log + +In order to check commit log for a branch, or, a file, following command can be used: + +`git log [options] [path]` + +The output of this command is given in reverse chronological order by default. + +## Command variations and options +- In order to log the commits reachable from a particular commit ids: (In this case, `foo` and `bar`)
+ `git log foo bar ` +- It is also possible to remove the commits reachable from a given commit id by adding a `^` in front of commit id: (In this case, `baz`)
+ `git log foo bar ^baz` +- Commit log for a particular file
+ `git log --all ` +- Limit number of commits in log (In this case, `5`)
+ `git log -n 5` + +## Refer +- [Official documentation](https://git-scm.com/docs/git-log) diff --git a/additional-material/git_workflow_scenarios/configuring-git.md b/additional-material/git_workflow_scenarios/configuring-git.md new file mode 100644 index 00000000000..1d0359d86b7 --- /dev/null +++ b/additional-material/git_workflow_scenarios/configuring-git.md @@ -0,0 +1,76 @@ +# Configuring git + +The first time you tried to commit using git, you might have gotten a prompt like the one below: + +```bash +$ git commit +*** Please tell me who you are. + +Run + +git config --global user.email "you@example.com" +git config --global user.name "Your Name" + +to set your account's default identity. +Omit --global to set the identity only in this repository. +``` + +Git needs to know who you are when you create a commit. When you are working collaboratively, you should be able to see who modified what parts of the project and when, and thus, git has been designed to create commits tied to a name and an email. + +There are multiple ways to provide the `git commit` command with your email and name, and we'll go through some of them below. + +### Global Config + +When you store something in the global config, it is accessible system wide in all the repositories you work on. This is the preferred way and works for most use cases. + +To store something in the global config, you use the `config` command as follows: + +`$ git config --global ` + +In the case of user details, we run it as follows: + +``` +$ git config --global user.email "you@example.com" +$ git config --global user.name "Your Name" +``` + +### Repository Config + +As the name says, these configurations are scoped to your current repository. If you want to commit to a particular repository, say, a work related project, with your company's email, then you could use this method. + +To store something in the repository config, you use the `config` command by omitting the `--global` flag as follows: + +`$ git config ` + +In the case of user details, we run it as follows: + +``` +$ git config user.email "you@alternate.com" +$ git config user.name "Your Name" +``` + +### Command-line Config + +These type of configurations are scoped to the current command only. All git commands take `-c` arguments before the action verb to set temporary configuration data. + +To store something in the command line config, run your command as follows: + +`$ git -c = -c = ` + +In our example, we would run the commit command as follows: + +`git -c user.name='Your Name' -c user.email='you@example.com' commit -m "Your commit message"` + +### Note on Precedence + +Among the three methods described here, the precedence order is `command-line > repository > global`. This means that, if a variable is configured in the command-line as well as globally, the command-line value would be used for the operation. + +## Beyond User Details + +We have dealt with only the user details till now while working with the config. However, there are several other configuration options available. Some of them are: + +1. `core.editor` - to specify the name of the editor used for writing commit messages, etc. +2. `commit.template` - to specify a file on the system as the initial commit template. +3. `color.ui` - to specify a boolean value for using colors in git's output. + +We have abstracted some details for ease of understanding. For further reading, head over to [git-scm.com](https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration). diff --git a/additional-material/git_workflow_scenarios/creating-a-gitignore-file.md b/additional-material/git_workflow_scenarios/creating-a-gitignore-file.md new file mode 100644 index 00000000000..fbf671f7c93 --- /dev/null +++ b/additional-material/git_workflow_scenarios/creating-a-gitignore-file.md @@ -0,0 +1,73 @@ +# .gitignore + +The .gitignore file is a text file that tells Git which files or folders to ignore in a project. + +A local .gitignore file is usually placed in the root directory of a project. You can also create a global .gitignore file and any entries in that file will be ignored in all of your Git repositories. + +## Why .gitignore +Now you may wonder why would you want git to ignore certain files and folders. Its because you don't want files like build files, cache files, other local configuration files like node modules, compilation files, temporary files IDE's create, etc to be tracked by git. It's usually used to avoid committing transient files from your working directory that aren't useful to other collaborators. + +## Getting started +To create a local .gitignore file, create a text file and name it .gitignore (remember to include the . at the beginning). Then edit this file as needed. Each new line should list an additional file or folder that you want Git to ignore. + +The entries in this file can also follow a matching pattern. + +``` +* is used as a wildcard match +/ is used to ignore path names relative to the .gitignore file +# is used to add comments to a .gitignore file + +This is an example of what the .gitignore file could look like: + +# Ignore Mac system files +.DS_store + +# Ignore node_modules folder +node_modules + +# Ignore all text files +*.txt + +# Ignore files related to API keys +.env + +# Ignore SASS config files +.sass-cache + +``` +To add or change your global .gitignore file, run the following command: + +``` +git config --global core.excludesfile ~/.gitignore_global + +``` +This will create the file ~/.gitignore_global. Now you can edit that file the same way as a local .gitignore file. All of your Git repositories will ignore the files and folders listed in the global .gitignore file. + +## How to Untrack Files Previously Committed from New Gitignore + +To untrack a single file, ie stop tracking the file but not delete it from the system use: + +``` +git rm --cached filename +``` + +To untrack every file in .gitignore: + +First, commit any outstanding code changes, and then run: + +``` +git rm -r --cached +``` + +This removes any changed files from the index(staging area), then run: + +``` +git add . +``` +Commit it: + +``` +git commit -m ".gitignore is now working" +``` + +To undo ```git rm --cached filename```, use ```git add filename``` diff --git a/additional-material/git_workflow_scenarios/delete-branch-locally.md b/additional-material/git_workflow_scenarios/delete-branch-locally.md new file mode 100644 index 00000000000..8c16d6ab506 --- /dev/null +++ b/additional-material/git_workflow_scenarios/delete-branch-locally.md @@ -0,0 +1,19 @@ +# Deleting a locally created Branch + +This will be handy when you accidentally misspelled a branch name. + +This can be done in *3* ways + +``` +git branch -D +``` + +``` +git branch --delete --force # Same as -D +``` + +``` +git branch --delete # Error on unmerge +``` + +-D stands for --delete --force which will delete the branch even it's not merged (force delete), but you can also use -d which stands for --delete which throws an error respective of the branch merge status... \ No newline at end of file diff --git a/additional-material/git_workflow_scenarios/gitflow.md b/additional-material/git_workflow_scenarios/gitflow.md new file mode 100644 index 00000000000..98f98eecaba --- /dev/null +++ b/additional-material/git_workflow_scenarios/gitflow.md @@ -0,0 +1,119 @@ +# Gitflow + +Gitflow is a branching model for Git made by Vincent Driessen. Here the discussion would be the requirements and use-cases of Gitflow.
+The Gitflow workflow defines a strict branching model designed around the project release, which provides a robust framework for managing larger projects. Gitflow is ideally suited for projects that have a scheduled release cycle and for the DevOps best practice of continuous delivery. It assigns very specific roles to different branches and defines how and when they should interact. It uses individual branches for preparing, maintaining and recording releases. + + +## Implementation + +1. **Develop and Master Branches**: Instead of a single master branch, Git Flow uses two branches to record the history of the project. It is based on two main branches with infinite lifetime namely master and develop: + - **Master Branch**: The master branch contains the production code and stores the official release history. + - **Develop Branch**: The develop branch contains pre-production code and serves as an integration branch for features. + - **Creating a Develop Branch**:
+ Without using the Gitflow extensions: + ``` + git branch develop + git push -u origin develop + ``` + Using the Gitflow extensions: When using the gitflow extension library, executing `git flow init` on an existing repo will create the develop branch. + ``` + git flow init + ``` +2. **Feature Branch**: Each new feature should reside in its branch, which can be pushed to the central repository for backup/collaboration. Feature branches use the latest develop as their parent branch. When a feature is complete, it gets merged back into develop. Features should never interact directly with the master branch. + - **Creating a Feature Branch**:
+ Without git-flow extensions: + ``` + git checkout develop + git checkout -b feature_branch + ``` + With gitflow extensions: + ``` + git flow feature start feature_branch + ``` + - **Finishing a Feature Branch**:
+ Without git-flow extensions: + ``` + git checkout develop + git merge feature_branch + ``` + With git-flow extensions: + ``` + git flow feature finish feature_branch + ``` +3. **Release Branch**: Once develop has acquired enough features for a release (or a predetermined release date is approaching), we fork a release branch off of develop. Creating this branch starts the next release cycle, so no new features can be added after this point—only bug fixes, documentation generation, and other release-oriented tasks should go in this branch. Release branch may branch off from develop and must merge into both master and develop.
+Using a dedicated branch to prepare releases makes it possible for one team to polish the current release while another team continues working on features for the next release. + - **Creating a Release Branch**:
+ Without the git-flow extensions: + ``` + git checkout develop + git checkout develop + git checkout -b release/0.1.0 + ``` + When using the git-flow extensions: + ``` + git flow release start 0.1.0 + ``` + Switched to a new branch 'release/0.1.0' + - **Finishing a Release Branch**:
+ Without git-flow extensions: + ``` + git checkout master + git merge release/0.1.0 + ``` + With git-flow extensions: + ``` + git flow release finish 0.1.0 + ``` +4. **Hotfix Branch**: Maintenance or “hotfix” branches are used to quickly patch production releases. Hotfix branches are necessary to act immediately upon an undesired status of master. Hotfix branches are a lot like release branches and feature branches except they’re based on master instead of develop. This is the only branch that should fork directly off of master. As soon as the fix is complete, it should be merged into both master and develop (or the current release branch), and the master branch should be tagged with an updated version number. + - **Creating a Hotfix Branch**:
+ Without git-flow extensions: + ``` + git checkout master + git checkout -b hotfix_branch + ``` + With git-flow extensions: + ``` + git flow hotfix start hotfix_branch + ``` + - **Finishing a Hotfix Branch**:
+ Without git-flow extensions: + ``` + git checkout master + git merge hotfix_branch + git checkout develop + git merge hotfix_branch + ``` + With git-flow extensions: + ``` + git branch -D hotfix_branch + git flow hotfix finish hotfix_branch + ``` + + +## Advantages + +- Ensures a clean state of branches at any given moment in the life cycle of a project. +- The naming convention of branches follows a systematic pattern making it easier to comprehend. +- Has extensions and support on most used git tools. +- Ideal in case of maintaining multiple versions in production. +- Great for a release-based software workflow. +- Offers a dedicated channel for hotfixes to production. + + +## Disadvantages + +- Git history becomes unreadable. +- The master/ develop branch split is considered redundant and makes the Continuous Delivery/ Integration harder. +- Not recommended in case of maintaining a single version in production. + + +## Summary + +Here we discussed the Git Flow Workflow. Git Flow is one of the many styles of Git workflows you and your team can utilize. Let’s summarize the whole workflow of Git Flow: +1. A develop branch is created from master. +1. Feature branches are created from develop. +1. When a feature is complete it is merged into the develop branch. +1. A release branch is created from develop. +1. When the release branch is done it is merged into develop and master. +1. If an issue in the master is detected a hotfix branch is created from master. +1. Once the hotfix is complete it is merged to both develop and master. diff --git a/additional-material/git_workflow_scenarios/keeping-your-fork-synced-with-this-repository.md b/additional-material/git_workflow_scenarios/keeping-your-fork-synced-with-this-repository.md new file mode 100644 index 00000000000..f3ff6e5cdd9 --- /dev/null +++ b/additional-material/git_workflow_scenarios/keeping-your-fork-synced-with-this-repository.md @@ -0,0 +1,45 @@ +# Keeping your fork synced with this repository + +First, the flow for a full sync should be understood, which is important. In this schema, there are 3 different repos: my public repo on Github `github.com/firstcontributions/first-contributions.git`, your fork of the repo on GitHub `github.com/Your-Name/first-contributions/` and your local machine's repo from which you are suppose to work. This kind of cooperation is typical for open source projects and called `Triangle Workflows`. + +triangle workflow + +To keep your two repos up-to-date with my public repo, we first have to fetch and merge the public repo with your local machine's repo. +Our second move will be to push your local repo to your GitHub fork. As you've seen earlier, it's only from your fork that you can ask for a "pull request". So your GitHub fork is the last repo to be updated. + +Now, let's see how to do it: + +First, you must be on your master branch. To know which branch you are on, check the first line of: +``` +git status +``` +if you are not already on master: +``` +git checkout master +``` + +Then you should add my public repo to your git with `add upstream remote-url`: +``` +git remote add upstream https://github.com/firstcontributions/first-contributions.git +``` +This is a way of telling git that another version of this project exists in the specified url and we're calling it `upstream`. Once your git has a name let's fetch the latest version of the public repository: +``` +git fetch upstream +``` + +You've just fetched the latest version of my fork (`upstream` remote). Now, you need to merge the public repository into your master branch. +``` +git rebase upstream/master +``` +Here you're merging the public repository with your master branch. Your local machine's master branch is now up-to-date. Lastly, if you push your master branch to your fork, your GitHub fork will also have the changes: +``` +git push origin master +``` +Notice here you're pushing to the remote named `origin`. + +If you want to fetch and merge the latest changes of my fork (`upstream` remote) to your local branch at same time then you can directly go for: +``` +git pull upstream master +``` + +So by now or at this point, all your repositories are up-to-date. Well done! You should do this, every time your GitHub repo tells you that you are a few commits behind. diff --git a/additional-material/git_workflow_scenarios/moving-a-commit-to-a-different-branch.md b/additional-material/git_workflow_scenarios/moving-a-commit-to-a-different-branch.md new file mode 100644 index 00000000000..40c8173fa72 --- /dev/null +++ b/additional-material/git_workflow_scenarios/moving-a-commit-to-a-different-branch.md @@ -0,0 +1,25 @@ +# Moving a commit to a different branch +What if you commit a change, and then realize that you committed to a different branch? +How can you change that? This is what this tutorial covers. + +## Moving the latest commits to an existing branch +To do this, type: + +```git reset HEAD~ --soft``` - Undoes the last commit, but leaves the changes available. +```git stash``` - Records the state of the directory. + +```git checkout name-of-the-correct-branch``` - Switches to another branch. +```git stash pop``` - Removes latest stashed state. +```git add .``` - Or try adding individual files. +```git commit -m "your message here"``` - Saves and Commits the changes. + +Now your changes are on the correct branch + + +### Moving the latest commits to a new Branch +To do this, type: +```git branch newbranch``` - Creates a new Branch. Saving all the Commits. +```git reset --hard HEAD~#``` - Move master back by # commits. Remember, these commits will be gone from master +```git checkout newbranch``` - Goes to the branch you created. It will have all the commits. + +Remember: Any changes not committed will be LOST. diff --git a/additional-material/git_workflow_scenarios/removing-a-file.md b/additional-material/git_workflow_scenarios/removing-a-file.md new file mode 100644 index 00000000000..b155a06df1a --- /dev/null +++ b/additional-material/git_workflow_scenarios/removing-a-file.md @@ -0,0 +1,23 @@ +# Removing a file from Git + +Sometimes, you may want to remove a file from Git but not delete it from your computer. You can achieve this by using the following command: + +``git rm --cached`` + +## So what happened? + +Git will no longer keep track of changes in the removed file. As far as Git knows, it's as if you had deleted the file. If you were to locate the file in your file system, you will notice that it's still there. + +Notice that in the example above, the flag `--cached` is used. If we didn't add this flag, Git will remove the file from not just the repo, but from your file system too. + +If you commit the change with `git commit -m "Remove file1.js"` and pushed it to the remote repository using `git push origin master`, the remote repository will remove the file. + +## Additional features + +- If you want to remove more than one file, you can include them all in the same command: + + `git rm file1.js file2.js file3.js --cached` + +- You can use a wildcard (*) to remove similar files. For example, if you would like to remove all .txt files from your local repository: + + `git rm *.txt --cached` diff --git a/additional-material/git_workflow_scenarios/removing-branch-from-your-repository.md b/additional-material/git_workflow_scenarios/removing-branch-from-your-repository.md new file mode 100644 index 00000000000..e65eea7f3e3 --- /dev/null +++ b/additional-material/git_workflow_scenarios/removing-branch-from-your-repository.md @@ -0,0 +1,31 @@ +# Remove a branch from your repository + +If you have followed the tutorial up-to-now, our `` branch has finished its purpose, it is time to delete it from your local machine's repo. This isn't necessary, but the name of this branch shows its rather special purpose. Its life can be made correspondingly short. + +First, let's merge your `` to your master, so to go to your master branch: +``` +git checkout master +``` + +Merge `` to master: +``` +git merge master +``` + +Remove `` on your local machine's repo: +``` +git branch -d +``` + +You have now deleted your local machine's `` branch and everything looks neat and tidy. +Though, at this point, you should still have the `` branch in your GitHub fork. However, before you delete this, remember that you have sent a "Pull request" to my repo from this remote branch. So unless I've already merged it, don't delete this branch. + +However, if I have merged your branch and you want to delete the remote branch, use: +``` +git push origin --delete +``` + +Now, you know how to tidy your branches. +With time, many commits will be added to my public repo. And the master branches of your local machine and of your GitHub fork won't be up-to-date. So in order to keep your repositories synchronized with mine, follow the steps below. + +#### [Keeping your fork synced with the repository](keeping-your-fork-synced-with-this-repository.md) diff --git a/additional-material/git_workflow_scenarios/resetting-a-branch.md b/additional-material/git_workflow_scenarios/resetting-a-branch.md new file mode 100644 index 00000000000..65bd64815c1 --- /dev/null +++ b/additional-material/git_workflow_scenarios/resetting-a-branch.md @@ -0,0 +1,18 @@ +# Reset a branch + +```reset``` is the command which can be used when we want to reset the repository with respect to a commit or a branch. A reset, as the name suggests, discards everything on the base(current) branch and makes it exactly same as the branch with which we chose to reset the base branch (calling it as origin branch). This essentially means, that we will have a copy of the origin branch with the name of base branch.
+However, the question is, why don't we just delete the base branch and checkout a new branch with the name of base branch from origin branch. Technically, it will have the same effect as resetting but in some industrial situations we do not have the access to delete a branch, or we can not delete a branch as it will hamper/disrupt a CI/CD pipeline or maybe an ongoing workflow. Hence, to avoid such situations which can lead to downtimes, we suggest using `git reset` whenever we want to reset a particular branch. + +## The Command + +Its very easy to execute a git reset for branch. +``` +git reset +``` + +An example could be: +``` +git reset stage master --hard +``` +The above command will reset the `stage` branch with `master` and therefore make `stage` exactly same as `master`. +You must be wondering about why `--hard` flag is used? This is to ignore all the changes which are or will be staged before/after the reset. diff --git a/additional-material/git_workflow_scenarios/resetting-a-commit.md b/additional-material/git_workflow_scenarios/resetting-a-commit.md new file mode 100644 index 00000000000..c52bcdbbbba --- /dev/null +++ b/additional-material/git_workflow_scenarios/resetting-a-commit.md @@ -0,0 +1,20 @@ +# Reset a commit + +```reset``` is the command which can be used when we want to move the repository back to a previous commit, discarding any changes made after that commit.
+The main difference between resetting and reverting a commit is that git reset ```unstages a file and bring our changes back to the working directory``` +and git revert ```removes the commits from the remote repository```.
+ +```git reset``` can be achieved using following commands: +- The following command will give summary of all the commits using following two parameters: + + - The first seven characters of the commit hash - this is what we need to refer to in our **reset** command. + - the commit message + + ``` + git log --oneline + ``` + + +- One can reset repository back to the specific commit using following command:
+ ```git reset commithash``` + where commithash being the first 7 characters of the commit hash we found in the log diff --git a/additional-material/git_workflow_scenarios/resolving-merge-conflicts.md b/additional-material/git_workflow_scenarios/resolving-merge-conflicts.md new file mode 100644 index 00000000000..dbe8a09e0f6 --- /dev/null +++ b/additional-material/git_workflow_scenarios/resolving-merge-conflicts.md @@ -0,0 +1,35 @@ +# What is a merge conflict? + +When you try to merge another branch into your current working branch, you are taking changes from another context and combining them with your current working files. +If two people have changed the same lines in the same file, or if one person decided to delete it while the other person decided to modify it, Git cannot identify which is the correct version. Git will then mark the file as having a conflict - which you'll have to resolve before you can continue your work. + +# How to resolve a merge conflict? + +When faced with a merge conflict, git will mark the problematic area in the file by enclosing it in “<<<<<<<< HEAD” and “>>>>>>>>>>[other branch name]” + +The contents after the first marker originate from your current working branch. After the angle brackets, Git tells us where (from which branch) the changes came from. A line with "=======" separates the two conflicting changes. +Our job is now to clean up these lines: when we're done, the file should look exactly as we want it to look. It is advisable to consult the teammate who wrote the conflicting changes to decide which version should be final. It could be either on of yours - or maybe a mixture between the two. + +e.g. : +``` + <<<<<<< HEAD:mergetest + This is my third line + ======= + This is a fourth line I am adding + >>>>>>> 4e2b407f501b68f8588aa645acafffa0224b9b78:mergetest +``` + +`<<<<<<<`: Indicates the start of the lines that had a merge conflict. The first set of lines are the lines from the file that you were trying to merge the changes into. +`=======`: Indicates the break point used for comparison. Breaks up changes that user has committed (above) to changes coming from merge (below) to visually see the differences. +`>>>>>>>`: Indicates the end of the lines that had a merge conflict. + +You resolve a conflict by editing the file and then manually merging the parts of the file that git had trouble merging. This may mean discarding either your changes or someone else's or going ahead with a mix of the two. You will also need to delete the '<<<<<<<', '=======', and '>>>>>>>' in the file. + + +Once you have resolved the conflict do a `git add`. Do not forget to run the tests, as you have to make sure that you have resolved the conflict. + +You can also download different plugins depending on the IDE you are using for an easier way to resolve merge conflicts. + + +# How to undo a merge? +If you want to undo a merge then you can do `git merge —abort` diff --git a/additional-material/git_workflow_scenarios/reverting-a-commit.md b/additional-material/git_workflow_scenarios/reverting-a-commit.md new file mode 100644 index 00000000000..762f73a08d3 --- /dev/null +++ b/additional-material/git_workflow_scenarios/reverting-a-commit.md @@ -0,0 +1,41 @@ +# Revert a commit + +To revert a commit simply means to create a brand new commit that undoes all +the changes made in a previous one. It is like doing a ```CTRL + Z ``` on git. + +Reversion is made easier in git because every commit you push to your remote repository has a unique alphanumeric key known as SHA(Secure Hash Algorithm) tied to it. +So this means you can revert any commit as long as you have the SHA. +But then, you have to be careful to reverse orderly so as not to mess your repository up. + + +To pick out the SHA of the specific commit we want to undo, a log of all the commits we have made so far would come in handy. +To get this, we would run the command: +```git log --oneline ``` +Running the ```git log``` command alone would also give us the SHAs (in long form) +However using the ```--oneline ``` flag tells git that we want it displayed in a concise (one line) manner for easy read. + +The first 7 characters displayed when you run this command is called the abbreviated commit hash. + +For example, here is what I get when I run ```git log --oneline ``` on this repository: +``` +389004d added spacing in title +c1b9fc1 Merge branch 'master' into tutorials +77eaafd added tutorial for reverting a commit +``` + +So this shows that with ```git log --oneline```, we can fetch a list of all the commits made on the repository together with the first 7 characters of its SHA. + +Now, Let's assume I want to undo my commit of "added spacing in title", here are the steps I would take: + +* Copy the SHA of the commit which, in this case is ```389004d``` +* Then, run the command ```git revert 389004d``` + +This would pop open my text editor and prompt me to edit the commit message. +You can decide to leave the commit message as the default git message which starts with the word `Revert` +or you can also decide to customize the message to your liking. + +* Next, I will save and close the text editor. +* Return to the command line. +* Run ```git push origin ``` to push the reverted changes to Github. + +And that is it, the change would be undone. In this case, my repository would be reverted to how it looked like in ```c1b9fc1``` diff --git a/additional-material/git_workflow_scenarios/squashing-commits.md b/additional-material/git_workflow_scenarios/squashing-commits.md new file mode 100644 index 00000000000..b31cc3b04ed --- /dev/null +++ b/additional-material/git_workflow_scenarios/squashing-commits.md @@ -0,0 +1,86 @@ +# What is squashing? + +In git, squashing refers to rewriting the history of your commits, so you end up with one commit with a description of the changes done. +It's usually done in open source projects because a lot of the history of a branch in open source projects is only relevant to the developer who created it, and this provides a simpler way to describe the changes made and also revert them if needed. + +# How do you squash commits? + +First, perform a git log to review the commits you would like to merge in your current branch. + +``` +git log +``` + +You should see a series of your commits like so: + +``` +commit blablabla +Author: omguhh +Date: 10/10/20 + Commit message 1 + +commit blablabla2 +Author: omguhh +Date: 10/10/20 + Commit message 2 +``` + +So now that you see the commits you wish to merge to one, we can move along into doing that with ```git rebase```. Assuming you're already familiar with ```git rebase```, we can starting squashing commits in the interactive mode of git rebase that you can activate like so: + +``` +git rebase -i +``` + +Now, with interactive rebasing you can specify the starting and end point of how far back you want to go with commits like so: + +``` +git rebase -i HEAD~2 +``` + +Running this command will show you something like the following: + +``` +pick blablabla Changing test01.txt file +pick blablabla2 Adding dummy01.txt file + +# +# Commands: +# p, pick = use commit +# r, reword = use commit, but edit the commit message +# e, edit = use commit, but stop for amending +# s, squash = use commit, but meld into previous commit +# f, fixup = like "squash", but discard this commit's log message +# x, exec = run command (the rest of the line) using shell +# +# These lines can be re-ordered; they are executed from top to bottom. +# +# If you remove a line here THAT COMMIT WILL BE LOST. +# +# However, if you remove everything, the rebase will be aborted. +# +# Note that empty commits are commented out +``` + +So if you want to squash ```blablabla2``` into ```blablablabla```, you would change the following : + +``` +pick blablabla Changing test01.txt file +squash blablabla2 Adding dummy01.txt file + +``` + +If all goes well, you'd get a result that looks like this: + +``` +# This is a combination of 2 commits. +# The first commit's message is: +commit message 1 + +# This is the 2nd commit message: + +commit message 2 +``` + +That you can freely change before you decide to exit the editor to save these changes. + +Running git log again should show you the commit message you entered before exiting the screen with the commits combined into one. diff --git a/additional-material/git_workflow_scenarios/stashing-a-file.md b/additional-material/git_workflow_scenarios/stashing-a-file.md new file mode 100644 index 00000000000..c3421d7376c --- /dev/null +++ b/additional-material/git_workflow_scenarios/stashing-a-file.md @@ -0,0 +1,137 @@ +# Stashing + +What if you are working on a big code and suddenly you need to switch the branch from which you are currently working on to some other branch. Since the code, is not complete, and without any tests, you probably don't want to commit it. But you cannot move to the other branch without committing the changes, Git won't let you break this flow. What do we do then? How do we prevent an unnecessary commit, while being able to jump branches? This is what this tutorial covers. + +## Stashing your work + +Let's assume you are working on a project's branch where you have changed some files. Now if you run ```git status``` you can see your changes in the files. + +``` +$ git status +# On branch master +# Changes to be committed: +# (use "git reset HEAD ..." to unstage) +# +# modified: index.html +# +# Changes not staged for commit: +# (use "git add ..." to update what will be committed) +# +# modified: lib/simplegit.rb +# +``` + +Now you want to switch your branch, but don't want to commit the changes yet; so you would stash the changes. +To push a new stash on to your stack, run ```git stash```: + +``` +$ git stash +Saved working directory and index state \ + "WIP on master: 049d078 added the index file" +HEAD is now at 049d078 added the index file +(To restore them type "git stash apply") +``` + +Now your working directory is clean, use ```git status``` : + +``` +$ git status +# On branch master +nothing to commit, working directory clean +``` + +Now you can switch to any branch and do your work; your stashed changes are stored in form of a stack. To see which stashes you have stored in the stack you can use ```git stash list```: + +``` +$ git stash list +stash@{0}: WIP on master: 049d078 added the index file +stash@{1}: WIP on master: c264051 Revert "added file_size" +stash@{2}: WIP on master: 21d80a5 added number to log +``` + +In case you want to re-apply the changes you just stashed, you can use the command ```git stash apply```. By using this command you can reapply the most recent stashed file. In order to reapply any other file, you can specify it by naming it like: ```git stash apply ```, in place of `````` write the name of the stash you need to reapply. + +``` +$ git stash apply +# On branch master +# Changes not staged for commit: +# (use "git add ..." to update what will be committed) +# +# modified: index.html +# modified: lib/simplegit.rb +# +``` + +You can see that git re-modifies the file that you uncommitted when you saved the stash. In this case, you had a clean working directory when you tried to apply the stash, and you tried to apply it on the same branch you saved it from; but having a clean working directory and applying it on the same branch aren’t necessary to successfully apply a stash. You can save a stash on one branch, switch to another branch later, and re-apply the changes in the new branch. You can also have modified and uncommitted files in your working directory when you apply a stash, git gives merge conflicts if anything no longer applies cleanly. + +The changes made to your files are reapplied, but the file you staged was not restaged. To do so you need to run the command ```git stash apply``` with a ```--index``` to tell the command to reapply the staged changes. If you have run that instead, you would have returned to your original position: + +``` +$ git stash apply --index +# On branch master +# Changes to be committed: +# (use "git reset HEAD ..." to unstage) +# +# modified: index.html +# +# Changes not staged for commit: +# (use "git add ..." to update what will be committed) +# +# modified: lib/simplegit.rb +# +``` + +The apply command only applies the stashed work, but you still have that on your stack. In order to remove it, you can run ```git stash drop``` with the name of the stash to remove. + +``` +$ git stash list +stash@{0}: WIP on master: 049d078 added the index file +stash@{1}: WIP on master: c264051 Revert "added file_size" +stash@{2}: WIP on master: 21d80a5 added number to log +$ git stash drop stash@{0} +Dropped stash@{0} (364e91f3f268f0900bc3ee613f9f733e82aaed43) +``` + +You can use ```git stash pop``` to un-stash the last changes drop it from your stash's stack. + +## Un-applying a Stash + +In some cases you want to apply stashed changes, do some work, but un-apply the changes that originally came from the stash. Git does not provide command like ```git unapply```, but it is possible to achieve this effect by simply retrieving the patch associated with a stash and applying it in reverse: + +```$ git stash show -p stash@{0} | git apply -R``` + +Again if you don't specify a stash, Git assumes the most recent stash: + +```$ git stash show -p | git apply -R``` + +You may want to create an alias and effectively add a ```stash-unapply``` command to your Git. For example: + +``` +$ git config --global alias.stash-unapply '!git stash show -p | git apply -R' +$ git stash apply +$ #... work work work +$ git stash-unapply +``` + +## Creating a Branch from Stash + +If you stash some work, leave it there for a while, and continue on the branch from which you stashed the work, you may have a problem reapplying the work. If the apply tries to modify a file that you’ve since modified, you’ll get a merge conflict and will have to resolve it. If you want an easier way to test the stashed changes again, you can run ```git stash branch```, which creates a new branch for you, checks out the commit you were on when you stashed your work, reapplies your work there, and then drops the stash if it applies successfully: + +``` +$ git stash branch testchanges +Switched to a new branch "testchanges" +# On branch testchanges +# Changes to be committed: +# (use "git reset HEAD ..." to unstage) +# +# modified: index.html +# +# Changes not staged for commit: +# (use "git add ..." to update what will be committed) +# +# modified: lib/simplegit.rb +# +Dropped refs/stash@{0} (f0dfc4d5dc332d1cee34a634182e168c4efc3359) +``` + +This is a nice shortcut to recover stashed work easily and work on it in a new branch. \ No newline at end of file diff --git a/additional-material/git_workflow_scenarios/undoing-a-commit.md b/additional-material/git_workflow_scenarios/undoing-a-commit.md new file mode 100644 index 00000000000..ba2d363d91d --- /dev/null +++ b/additional-material/git_workflow_scenarios/undoing-a-commit.md @@ -0,0 +1,55 @@ +# Undo local commits + +To undo a local commit, all you need to do is +``` +git reset +``` +This command will reset your staging area to your most recent commit, but the changes you made to your working directory will not change. So, you can still re-commit again what you've changed. +Or, if you only want to remove one file from your previous commit. Then, you can do the command below +``` +git reset +``` +The command will remove only the specified file from the staging area, but changes made on the file will still remain. + +Example of ```git reset``` usage +``` +# Make changes in index.php and tutorial.php +# Add files into the staging area +$ git add . +# Remembered both files need to be committed separately +# Unstage tutorial.php +$ git reset tutorial.php +# Commit index.php first +$ git commit -m "Changed index.php" +# Commit tutorial.php now +$ git add tutorial.php +$ git commit -m "Changed tutorial.php" +``` + +Let's say if you have messed up your local repository and you just want to reset it to your last commit. +Then, you can run the command below. +``` +git reset --hard +``` +The command will not only reset your staging area, but also revert all your changes on the files to your last commit. +The mode ```--hard``` tells Git to undo all the changes in the working directory too. +You should only run this when you are really sure of throwing your whole local development out. + +Example of ```git reset --hard``` usage +``` +# Decided to start a crazy experiment +# Create a new file 'crazy.php' and add some code to it +# Commit crazy.php +$ git add crazy.php +$ git commit -m "Started a crazy dev" +# Edit crazy.php file again and changed a lot of other files +# Commit all tracked files +$ git add . +$ git commit -m "Continued dev" +# Tested and things went out of hand +# Decided to remove the whole things +$ git reset --hard HEAD~2 +``` +The ```git reset --hard HEAD~2``` moves the current branch backward by 2 commit points at the same time reverting all changes you have made and remove the 2 snapshots we have just created from project history. + +P.s. Never perform ```git reset --hard``` if you've already pushed your commits to a shared repository as it will cause problems to everyone on that repository. diff --git a/additional-material/git_workflow_scenarios/why-using-branches.md b/additional-material/git_workflow_scenarios/why-using-branches.md new file mode 100644 index 00000000000..0ee58ea5ad4 --- /dev/null +++ b/additional-material/git_workflow_scenarios/why-using-branches.md @@ -0,0 +1,53 @@ +# WHY USING BRANCHES DURING CONTRIBUTING + +## What are branches. + +Branches are simply pointers to a commit. + +When you branch out, git is essentially making a new state of your current code, upon which you can work, without affecting the important main state of the code (which is in master branch). + +When you are happy with your experiments, and want to merge you experiments in main code, you run git merge + master. +This will tell git, to add in all changes from your experiment branch into master. + +This way, while working in an open source project with a number of contributors, it becomes easy to merge the best suited code without altering the main code or master branch. + +## How it works? + +A branch represents an independent line of development. Branches serve as an abstraction for the edit/stage/commit process. You can think of them as a way to request a brand new working directory, staging area, and project history. New commits are recorded in the history for the current branch, which results in a fork in the history of the project. + +The git branch command lets you create, list, rename, and delete branches. It doesn’t let you switch between branches or put a forked history back together again. For this reason, git branch is tightly integrated with the git checkout and git merge commands. + +## Why to use branches? + +If the question "Why do we use branching in version control like git?" still persists in your mind, here's a quick explanation: + +Let's take a simple example to understand the branching strategy. A production car needs a paint job before its launch. Prior to its official sale, it was decided that the car would come in 'olive green' color as default. But some of the members in the manufacturing team decided to showcase the car in 'red' color. Hence an ambiguous situation arises and to avoid this problem branching was introduced.The red color paint job is like a branch to the master repository 'Car'. Pushing this branch will suggest the red color. If merged with the master repository the car will get the red color otherwise it will continue with olive green. Merging a contributors branch to the master repo of the organization depends on the project head. + +## Example + +Alice is working on Feature A and Bob is working on Feature B. Alice is halfway done with Feature A and has made a few commits in alice. However, Feature A is quite hard to implement so Alice decides that she should rather work on Feature C and makes a few commits onto alice. Bob finished Feature B and decides that he would like to tackle Feature A and so pulls alice into bob. + +After Bob finishes Feature A he would like to merge bob into master. However, bob now contains Feature A, Feature B and parts of Feature C, but Feature C is not ready to be merged! It's easy to see that a workflow like this can lead to many confusing merge conflicts. + +The trick is that instead of having personal branches one should have feature branches. Alice should have a branch for Feature A and Feature C and Bob should have a branch for Feature B and Feature A. That way they both can work on different features without tramping on each other's toes. + +## How to create branches? + +#### Create a branch + +``` +git branch AnyBranchName +``` + +A new branch will be created named AnyBranchName and all the file changes in this branch will not be affected in the main branch. +For detailed explanation refer [How to create branch](https://www.atlassian.com/git/tutorials/using-branches) + +#### Delete the branch + +``` +git branch -d AnyBranchName +``` + +Branch name AnyBranchName will be deleted from the git repository. +Refer to [Removing branch from your repository](https://github.com/jashnimje/first-contributions/blob/7dcae72208e4b42fcf834b4f189fa8ee78238077/additional-material/git_workflow_scenarios/removing-branch-from-your-repository.md) diff --git a/additional-material/translations/Belarusian/Useful-links-for-further-learning.by.md b/additional-material/translations/Belarusian/Useful-links-for-further-learning.by.md new file mode 100644 index 00000000000..ea6d697b4c9 --- /dev/null +++ b/additional-material/translations/Belarusian/Useful-links-for-further-learning.by.md @@ -0,0 +1,36 @@ +# Карысныя спасылкі + +Гэты дакумент прысвечаны ўсіх сайтаў з парадамі і рэкамендацыямі, паведамленнях у блогах і карысным сайтам, якія палягчаюць наша жыццё. Яны з'яўляюцца выдатным арыенцірам для задавальнення ўсіх нашых патрэбаў, няхай гэта будзе пачатковец або эксперт. Гэтая старонка павінна служыць індэксам ўсіх тых карысных спасылак, якія дапамогуць усім, хто пачатковец у вобласці адкрытага зыходнага кода, ці каму-небудзь, хто хоча даведацца больш. + +## Спіс +1. [Interactive tutorial to git](https://try.github.io) +2. [git - the simple guide](http://rogerdudler.github.io/git-guide/) +3. [On undoing, fixing, or removing commits in git](http://sethrobertson.github.io/GitFixUm/fixup.html) +4. [Git and GitHub tutorial translated to many languages](https://github.com/Roshanjossey/first-contributions) +5. [Merge Conflicts](https://www.git-tower.com/learn/git/ebook/en/command-line/advanced-topics/merge-conflicts) +6. [Resolving Merge Conflicts](https://githowto.com/resolving_conflicts) +7. [Basics of Git - The Simple Quick Start Guide](https://blog.praveen.science/basics-of-git-the-quick-start-guide/) +8. [Git Standards followed in our way of Spotify Agile Methodology](https://blog.praveen.science/git-standards-followed-in-our-way-of-spotify-agile-methodolgy/) +9. [Git Shortcuts](https://blog.praveen.science/git-shortcuts/) +10. [Official Git cheat sheet in many languages](https://services.github.com/on-demand/resources/cheatsheets) +11. [Git cheat sheet from Tower](https://www.git-tower.com/learn/cheat-sheets/git) +12. [Common Git Problems](https://www.codementor.io/citizen428/git-tutorial-10-common-git-problems-and-how-to-fix-them-aajv0katd) +13. [Git Rebase](https://blog.gitprime.com/git-rebase-an-illustrated-guide/) +14. [Beginner's Guide to Rebasing and Squashing](https://github.com/servo/servo/wiki/Beginner%27s-guide-to-rebasing-and-squashing) +15. [Git Cheatsheet that shows correlations between commands and files](http://ndpsoftware.com/git-cheatsheet.html) +16. [How to contribute](https://opensource.guide/how-to-contribute/) +17. [Getting started with Open Source](https://github.com/OpenSourceHelpCommunity/Getting-Started-With-Contributing-to-Open-Sources) +18. [How to contribute](https://github.com/freeCodeCamp/how-to-contribute-to-open-source) +19. [Atlassians Git Tutorials](https://www.atlassian.com/git) +20. [Pull request reviews](https://help.github.com/articles/about-pull-request-reviews/) +21. [Another Interactive tutorial for git](https://learngitbranching.js.org/) +22. [Git commandline cheat-sheet](https://gist.github.com/davfre/8313299) +23. [Programming Books](https://github.com/EbookFoundation/free-programming-books) +24. [E-Book of professional tip and secrets](https://goalkicker.com/GitBook/GitProfessionalTipsSecrets.pdf) +25. [tutorial about simple rules of become git professional](https://medium.freecodecamp.org/follow-these-simple-rules-and-youll-become-a-git-and-github-master-e1045057468f) +26. [A Note About Git Commit Messages](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) +27. [5 Useful Tips For A Better Commit Message](https://thoughtbot.com/blog/5-useful-tips-for-a-better-commit-message) +28. [Version Control using Git](https://ourcodingclub.github.io/2017/02/27/git.html) +29. [Version Control with Git](https://www.udacity.com/course/version-control-with-git--ud123) + +Працягвайце дадаваць больш спасылак, якія вам падаюцца карыснымі. diff --git a/additional-material/translations/Belarusian/additional-material.by.md b/additional-material/translations/Belarusian/additional-material.by.md new file mode 100644 index 00000000000..182da7342af --- /dev/null +++ b/additional-material/translations/Belarusian/additional-material.by.md @@ -0,0 +1,46 @@ +# Дадатковая інфармацыя + +Тут мы мяркуем, што вы ўжо асвоілі асноўную інструкцыю. Дадатковая інфармацыя змяшчае некаторыя звесткі аб GIT камандах, необходимыж ў больш складаных сітуацыях. + +### [Выпраўленні ў каміты](amending-a-commit.by.md) +Дакумент змяшчае інфармацыю аб тым, як ўнесці выпраўлення ў commit ў аддаленым рэпазітары. +> Яна неабходная для тых выпадкаў, калі вы хочаце змяніць commit, які вы зрабілі раней. + +### [Канфігураванне GIT](configuring-git.by.md) +Дакумент змяшчае сведния пра тое, як змяніць інфармацыю аб карыстальніку і іншыя налады GIT. +> Ён будзе карысны, калі вы захочаце зрабіць ўстаноўкі GIT больш зручнымі. + +### [Сінхранізацыя вашага адгалінаванні з асноўным рэпазітаром](keeping-your-fork-synced-with-this-repository.by.md) +Дакумент распавядае аб тым, як забяспечыць сінхранізацыю вашага адгалінаванні з асноўным рэпазітаром. Забеспячэнне сінхранізацыі небходнасць, так як, наколькі можна спадзявацца, вы будзеце працаваць над праектам не ў адзіноце, а ўносіць змены ў яго, разам з іншымі ўдзельнікамі. +> Выканайце гэтыя дзеянні, калі ваша адгалінаванне не мае змяненняў у master галінцы рэпазітара. + +### [Перамяшчэнне камітаў ў іншую галінку](moving-a-commit-to-a-different-branch.by.md) +Дакумент змяшчае звесткі аб тым, як перамясціць commit ў іншую галінку. +> Выканайце названыя крокі, каб перамясціць комм ў іншую галінку. + +### [Выдаленне файла](removing-a-file.by.md) +Дакумент апісвае як выдаліць файл з вашага лакальнага рэпазітара. +> Азнаёмцеся з гэтымі камандамі каб зразумець як выдаліць файл перад тым, як зрабіць commit. + +### [Выдаленне галінкі з вашага рэпазітара](removing-branch-from-your-repository.by.md) +Дакумент змяшчае інфармацыю аб тым, як выдаліць галінку з вашага рэпазітара. +> Выкарыстоўвайце гэтыя каманды толькі пасля таго, як ваш pull-request быў задаволены. + +### [Дазвол канфліктаў пры зліцці галінак](resolving-merge-conflicts.by.md) +Дакумент змяшчае інфармацыю аб тым, як вырашаць канфлікты, якія ўзнікаюць пры зліцці галінак. +> Прапанаваныя тут крокі дапамогуць вам разабрацца з вельмі непрыемнымі выпадкамі канфліктаў якія ўзнікаюць пры зліцці галінак. + +### [Адмена камітаў](reverting-a-commit.by.md) +Дакумент інструктуе як адмяніць commit ў аддаленым рэпазітары. Такая аперацыя будзе карысная ў тых выпадках, калі вам неабходна адыграць назад той commit, які ўжо быў пасланы на Github (pushed). +> Выканайце названыя тут крокі каб адмяніць commit. + +### [Сумяшчэнне камітаў (squashing)](squashing-commits.by.md) +Дакумент апісвае, як сумяшчаць камітаў пры дапамозе інтэрактыўнага перабазавання. +> Выкарыстоўвайце гэтыя інструкцыі, калі вы стварылі пул-реквест ў open source праекце, але эксперт праекта просіць вас сумясціць усе вашыя камітаў ў адзін комм з змястоўным каментаром. + +### [Адмена лакальнага каміту](undoing-a-commit.by.md) +Дакумент утрымлівае інфармацыю, як адыграць назад commit ў вашым лакальным рэпазітары. Вам спатрэбіцца гэтая інфармацыя ў тым выпадку, калі вы вырашыце, што вы сапсавалі ваш рэпазітар і захочаце вярнуць яго змесціва да першапачатковага стану. +> Выконвайце гэтым інструкцыям, калі вы хочаце адмяніць тыя змены, якія былі зробленыя апошнім лакальным commit . + +### [Карысныя спасылкі](Useful-links-for-further-learning.by.md) +Гэты файл утрымлівае спасылкі на блог-пасты, карысныя вэб-сайты, вэб-сайты з пералікам рэкамендацыі і прыёмаў, якія часта палягчаюць наша жыццё. Як пачаткоўцам, так і экспертам мы рэкамендуем звяртацца да іх па меры неабходнасці. Гэты файл утрымлівае спіс карысных спасылак, якія напэўна дапамогуць і тым, хто робіць першыя крокі ў open source, і тым, хто захоча павялічыць свае веды ў гэтай галіне. \ No newline at end of file diff --git a/additional-material/translations/Belarusian/amending-a-commit.by.md b/additional-material/translations/Belarusian/amending-a-commit.by.md new file mode 100644 index 00000000000..b86667447ee --- /dev/null +++ b/additional-material/translations/Belarusian/amending-a-commit.by.md @@ -0,0 +1,46 @@ +# Выпраўленні ў каміты + +Уявіце, што вы зрабілі commit ў выдалены рэпазітар, а потым зразумелі, што дапусцілі памылку друку ў каментары да commit або забыліся ўставіць радок у гэты апошні па часе commit. Як паступіць у гэтай сітуацыі? Менавіта пра гэта і пойдзе гаворка ў гэтым дакуменце. + +## Як змяніць каментар да нядаўняга камітаў пасля таго, як ён быў пасланы на Github (pushed) +Каб зрабіць гэта, не адкрываючы файл для рэдагавання, +* Набярыце ```git commit --amend -m "followed by your new commit message"``` +* А затым выканаеце ```git push origin ``` для таго, каб паслаць змены на Github. + +Заўвага: Калі вы набярэце, толькі ```git commit --amend```, то адкрыецца тэкставы рэдактар і прапануе адрэдагаваць каментар да commit. +Выкарыстанне ключа `` -m`` адмяняе запуск рэдактара. + +## Як зрабіць змены ў адным commit + +Што калі мы забыліся зрабіць невялікае змяненне ў файле, напрыклад, замяніць адно слова ў commit, які ўжо пасланы ў выдалены рэпазітар? + +Хай, для прыкладу, запісы ў часопісе маіх commit выглядаюць наступным чынам: +`` ` +g56123f create file bot file +a2235d updated contributor.md +a5da0d modified bot file +`` ` +Дапусцім, я забыўся дадаць адно слова ў файл bot file + +Ёсць два спосабу выправіць гэта. Першы заключаецца ў стварэнні новага commit, які змяшчае гэта змена, напрыклад, так: +`` ` +g56123f create file botfile +a2235d updated contributor.md +a5da0d modified botfile +b0ca8f added single word to botfile +`` ` +Другі спосаб складаецца ў выпраўленні камітаў a5da0d, даданні гэтага прапушчанага слова і запушивании гэтых змяненняў на Github ў выглядзе аднаго камітаў. +Другі спосаб ўяўляецца пераважнай, паколькі справа ідзе толькі аб нязначным змене. + +Каб дамагчыся гэтага, мы паступім наступным чынам: +* Зменім файл. У дадзеным выпадку я змяню файл botfile, дадаўшы да яго слова, якое я прапусціў раней. +* Далей, праіндэксуем гэты файл пры дапамозе каманды ```git add ``` + +У звычайным выпадку адразу пасля індэксавання мы робім `` `git commit -m" коментар да нашага commit "` ``, правільна? Але паколькі ў дадзеным выпадку наша задача - выправіць папярэдні commit, - то замест гэтага мы выканаем такую каманду: + +* ```git commit --amend``` + У выніку адкрыецца акно тэкставага рэдактара, у якім мы маем магчымасць зрабіць змены ў каментары. Мы можам на самай справе адрэдагаваць каментар, ці пакінуць яго без зменаў. +* Выйдзем з рэдактара +* Запушим нашы змены пры дапамозе каманды ```git push origin ``` + +Такім чынам, абодва выпраўлення апынуцца ў адным commit. \ No newline at end of file diff --git a/additional-material/translations/Belarusian/configuring-git.by.md b/additional-material/translations/Belarusian/configuring-git.by.md new file mode 100644 index 00000000000..8cd9fda7ad5 --- /dev/null +++ b/additional-material/translations/Belarusian/configuring-git.by.md @@ -0,0 +1,76 @@ +# Канфігураванне GIT + +Калі вы ўпершыню паспрабавалі зрабіць commit, вы маглі ўбачыць такое паведамленне: + +```bash +$ git commit +*** Please tell me who you are. + +Run + +git config --global user.email "you@example.com" +git config --global user.name "Your Name" + +to set your account's default identity. +Omit --global to set the identity only in this repository. +``` + +Каб стварыць commit, GIT павінен ведаць хто з'яўляецца яго аўтарам. Пры сумеснай працы, неабходна ведаць кім і калі былі змененыя тыя ці іншыя часткі праекта, таму GIT прадугледжвае, што кожны commits пры яго стварэнні асацыюецца з імем і емейл адрасам карыстальніка. + +Існуе некалькі спосабаў, якія дазваляюць асацыяваць каманду `git commit` з вашым емейл і імем, і тут мы пералічым некаторыя з іх. + +### Глабальная канфігурацыя + +Інфармацыя, захаваная як частка глабальнай канфігурацыі, адносіцца да ўсёй сістэмы, г.зн. да ўсіх рэпазітароў, у якіх вы працуеце. Гэта пераважны спосаб, прыдатны для большасці з варыянтаў выкарыстання. + +Каб захаваць што-небудзь у глабальным канфігурацыі, вы выкарыстоўваеце каманду `config` наступным чынам: + +`$ git config --global ` + +Ва ўжыванні да інфармацыі пра карыстальніка, мы выконваем гэтыя каманды такім чынам: + +`` ` +$ git config --global user.email "you@example.com" +$ git config --global user.name "Your Name" +`` ` + +### Канфігурацыя рэпазітара + +Як вынікае з назвы, гэтыя канфігурацыі адносяцца да вашага бягучага сховішча. Калі вы хочаце прыняць удзел у пэўным сховішчы, скажам, на праекце, звязаным з працай, з электроннай поштай вашай кампаніі, то вы можаце скарыстацца гэтым метадам. + +Каб змяніць канфігурацыю на ўзроўні рэпазітара, варта апусціць ключ `--global` у камандзе` config` такім чынам: + +`$ git config ` + +Ва ўжыванні да інфармацыі пра карыстальніка, гэта выглядае наступным чынам: + +`` ` +$ git config user.email "you@alternate.com" +$ git config user.name "Your Name" +`` ` + +### Канфігурацыя ў камандным радку + +Гэты спосаб канфігурацыі адносіцца толькі да дадзенай камандзе. Усе каманды GIT дазваляюць выкарыстоўваць ключ `-c` перад дзеясловам ідэнтыфікуюць каманду для часовай ўстаноўкі канфігурацыйных параметеров. + +Для змены параметраў канфігурацыі, якія распаўсюджваюцца толькі на дадзеную каманду, карыстайцеся наступным фарматам каманд GIT: + +`$ git -c = -c = ` + +Для нашага выпадку Каманда для камітаў будзе вылядеть так: + +`git -c user.name='Your Name' -c user.email='you@example.com' commit -m "Your commit message"` + +### Заўвага аб парадку предшествования + +Парадак предшествования сярод трох згаданых тыпаў каманд канфігурацыі вызначаецца як `command-line > repository > global`. Гэта азначае, што калі якая-небудзь пераменная вызначана, як у глабальнай канфігурацыі, так і ў камандным радку, то будзе выкарыстана значэнне, прысвоенае у камандным радку. + +## Не толькі інфармацыя пра карыстальніка + +Да гэтага часу, абмяркоўваючы канфігурацыю GIT'а, мы дакраналіся толькі інфармацыі пра карыстальніка. Аднак GIT дазваляе канфігураваць яшчэ неслколько параметраў. Вось некторые з іх: + +1. `core.editor` - паказвае назва рэдактара для рэдагавання каментар для камітаў і да т.п., +2. `commit.template` - паказвае файл, які змяшчае першапачатковы темплат для камітаў, +3. `color.ui` - лагічная зменная, якая ўказвае ці варта испольовать каляровыя шрыфты ў паведамленнях на тэрмінале GIT'а. + +Для прастаты мы апусцілі некаторыя дэталі. Для больш падрабязнага азнаямлення звярніцеся да [git-scm.com](https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration). \ No newline at end of file diff --git a/additional-material/translations/Belarusian/keeping-your-fork-synced-with-this-repository.by.md b/additional-material/translations/Belarusian/keeping-your-fork-synced-with-this-repository.by.md new file mode 100644 index 00000000000..122b7cfd75f --- /dev/null +++ b/additional-material/translations/Belarusian/keeping-your-fork-synced-with-this-repository.by.md @@ -0,0 +1,42 @@ +# Сінхранізацыя вашага адгалінаванні з асноўным рэпазітаром + +Па-першае, варта разумець паток для поўнай сінхранізацыі, што важна. У гэтай схеме ёсць 3 розныя рэпазітары: мае адкрытыя сховішча ў Github `github.com / firstcontributions / first-doprino.git`, ваш відэлец сховішча на GitHub` github.com / Your-Name / first-donates / ` і сховішча мясцовай машыны, на якой вы павінны працаваць. Такі від супрацоўніцтва характэрны для праектаў з адкрытым зыходным кодам і называецца `Triangle Workflows`. + +triangle workflow + +Каб захаваць вашыя два сховішчы ў актуальным стане з маім адкрытым сховішчам, мы спачатку павінны здабыць і аб'яднаць агульнае сховішча з рэпазітарам вашай лакальнай машыны. +Наш другі крок - перанесці ваша мясцовае сховішча ў відэлец GitHub. Як вы ўжо бачылі раней, толькі "з відэльцам" вы можаце папрасіць "pull request". Такім чынам, відэлец GitHub - апошняе сховішча, якое трэба абнавіць. + +Зараз давайце паглядзім, як гэта зрабіць: + +Па-першае, вы павінны быць на сваім вядучым аддзяленні. Каб даведацца, на якой філіяле вы знаходзіцеся, праверце першы радок: +``` +git status +``` +калі вы яшчэ не на майстры: +``` +git checkout master +``` + +Затым вы павінны дадаць маё агульнадаступнае сховішча ў свой git з `add addstream stream-url`: +``` +git remote add upstream https://github.com/firstcontributions/first-contributions.git +``` + +Гэта спосаб сказаць Git, што іншая версія гэтага праекта існуе ў паказаным URL-адресе, і мы называем яго "вышэй". Пасля таго, як ваш git мае імя, давайце пазнаём апошнюю версію грамадскага сховішча: +``` +git fetch upstream +``` + +Вы толькі што атрымалі апошнюю версію майго відэльца (`upstream` remote). Зараз вам трэба аб'яднаць агульнадаступнае сховішча ў ваша галоўнае аддзяленне. +``` +git rebase upstream/master +``` +Тут вы аб'яднаеце грамадскае сховішча з вашай галоўнай галіной. Галоўнае аддзяленне вашай мясцовай машыны зараз актуальнае. І, нарэшце, калі вы націснеце галоўную галінку на відэлец, ваша відэлец GitHub таксама будзе змяняць: +``` +git push origin master +``` + +Звярніце ўвагу, вы націскаеце на remote імя `origin`. + +Такім чынам, да гэтага часу альбо ў гэты момант усе вашыя сховішчы актуальныя. Добра зроблена! Вы павінны рабіць гэта кожны раз, калі ваш сховішча GitHub паведамляе вам, што вы здзяйсняеце некалькі commits. \ No newline at end of file diff --git a/additional-material/translations/Belarusian/moving-a-commit-to-a-different-branch.by.md b/additional-material/translations/Belarusian/moving-a-commit-to-a-different-branch.by.md new file mode 100644 index 00000000000..69fb4eca30c --- /dev/null +++ b/additional-material/translations/Belarusian/moving-a-commit-to-a-different-branch.by.md @@ -0,0 +1,25 @@ +# Перамяшчэнне камітаў ў іншую галінку +Што рабіць, калі вы здзяйсняеце змены, а потым разумееце, што вы здзейснілі іншую галіну? +Як вы можаце гэта змяніць? Вось што ахоплівае гэты падручнік. + +## Перамяшчэнне апошніх камітаў ў існуючую галінку +Для такога перамяшчэння, набярыце: + +`` `git reset HEAD ~ --soft` `` - Адмяняе апошняе commit, але пакідае даступныя змены. +`` `git stash` `` - Захоўвае стан дырэкторыі. + +`` `git checkout <імя правільнай галінкі>` `` - Перамыкаецца на іншую галінку. +`` `git stash pop` `` - Вяртае апошняе захаванае стан. +`` `git add .` `` - Дадае індывідуальныя файлы. +`` `git commit -m "your message here"``` - Захоўвае і ўносіць змены. + +Зараз вашы змены - у правільнай галінцы. + + +### Перамяшчэнне апошніх камітаў ў новую галінку +Для такога перамяшчэння, набярыце: +`` `git branch newbranch` `` - Стварае новую галінку, захоўваючы ўсе камітаў. +`` `git reset --hard HEAD ~ [n]` `` - Вяртае галінку master назад на n камітаў. Майце на ўвазе, што змены змяшчаюцца ў гэтых камітаў будуць цалкам выдалены з галінкі master. +`` `git checkout newbranch` `` - Перамыкаецца на галінку, якую вы стварылі. Гэтая галінка цяпер змяшчае ўсе commits. + +Запомніце: Любыя змены, якія не былі ўключаныя ў commit, будуць цалкам страчаныя. \ No newline at end of file diff --git a/additional-material/translations/Belarusian/removing-a-file.by.md b/additional-material/translations/Belarusian/removing-a-file.by.md new file mode 100644 index 00000000000..6bae5ac286f --- /dev/null +++ b/additional-material/translations/Belarusian/removing-a-file.by.md @@ -0,0 +1,23 @@ +# Выдаленне файла з-пад GIT кантролю + +Часам можа ўзнікнуць неабходнасць выдаліць файл з-пад GIT кантролю, але захаваць яго на кампутары. Гэта можа быць дасягнута з дапамогай наступнай каманды: + +`` git rm <файл> --cached`` + +## Што ж адбылося? + +GIT больш не кантралюе змены ў аддаленым файле. З пункту гледжання GIT, гэты файл адсутнічае, але калі вы паспрабуеце лакалізаваць гэты файл у файлавай сістэме, то вы ўбачыце, што ён усё яшчэ на месцы. + +Звярніце ўвагу, што ў прыведзеным вышэй прыкладзе выкарыстоўваецца сцяг `--cached`. Калі мы не дадамо гэты сцяг, Git выдаліць файл не толькі з сховішча, але і з вашай файлавай сістэмы. + +Калі вы здзейсніце змяненне з дапамогай `git commit -m" Remove file1.js "` і перанеслі яго ў аддаленае сховішча з дапамогай `git push origin master`, выдалены рэпазітар выдаліць файл. + +## Дадатковая інфармацыя + +- Калі вы хочаце выдаліць больш за адзін файл, гэта можна зрабіць, пералічыўшы ўсе файлы ў адной камандзе: + + `git rm file1.js file2.js file3.js --cached` + +- Вы можаце выкарыстоўваць шаблон (*) для выдалення файлаў з блізкімі імёнамі, напрыклад, калі вы хочаце выдаліць усе .txt файлы з лакальнага рэпазітара, набярыце: + + `git rm * .txt --cached` \ No newline at end of file diff --git a/additional-material/translations/Belarusian/removing-branch-from-your-repository.by.md b/additional-material/translations/Belarusian/removing-branch-from-your-repository.by.md new file mode 100644 index 00000000000..ffbb7c81db4 --- /dev/null +++ b/additional-material/translations/Belarusian/removing-branch-from-your-repository.by.md @@ -0,0 +1,31 @@ +# Выдаленне галінкі з вашага рэпазітара + +Калі вы да гэтага часу выконвалі ўрок, то наша галіна `` скончыла сваё прызначэнне, прыйшоў час выдаліць яго з рэпазітара вашай лакальнай машыны. Гэта не абавязкова, але назва гэтай галіны паказвае сваё даволі спецыяльнае прызначэнне. Яго жыццё можа быць адпаведна кароткім. + +Спачатку давайце аб'яднаем ваша `` з вашым майстрам, каб перайсці да вашай галіны: +``` +git checkout master +``` + +Зліце `` у майстар: +``` +git merge master +``` + +Выдаліце `` у сховішчах вашай лакальнай машыны: +``` +git branch -d +``` + +Цяпер вы выдалілі галінку лакальнай машыны `` і ўсё выглядае акуратна і акуратна. +Хоць, у гэты момант у вашай раздзеле GitHub усё яшчэ павінна быць аддзяленне ``. Тым не менш, перш чым выдаліць гэта, памятайце, што вы адправілі "Pull request" у маё сховішча з гэтага аддаленага аддзялення. Таму, калі я ўжо аб'яднаў гэта, не выдаляйце гэтую галінку. + +Аднак калі я аб'яднаў вашу галіну і вы хочаце выдаліць аддаленую галінку, выкарыстоўвайце: +``` +git push origin --delete +``` + +Цяпер вы ведаеце, як прывесці ў парадак свае галіны. +З часам у маім публічным сховішчы будзе дададзена шмат камісій. І галоўныя галіны мясцовай машыны і вашага відэльца GitHub не будуць актуальнымі. Такім чынам, каб захаваць вашыя сховішча сінхранізаванымі з маімі, выканайце наступныя дзеянні. + +#### [Захоўваючы відэлец сінхранізаваным з сховішчам](keeping-your-fork-synced-with-this-repository.md) diff --git a/additional-material/translations/Belarusian/resolving-merge-conflicts.by.md b/additional-material/translations/Belarusian/resolving-merge-conflicts.by.md new file mode 100644 index 00000000000..d63fd705c74 --- /dev/null +++ b/additional-material/translations/Belarusian/resolving-merge-conflicts.by.md @@ -0,0 +1,33 @@ +# Што такое канфлікт зліцця? + +Пры спробе аб'яднаць іншую галінку з вашай бягучай працоўнай галіной, вы ўносіце змены ў іншы кантэкст і аб'ядноўваючы іх з вашымі бягучымі файламі. +Калі два чалавекі змянілі аднолькавыя радкі ў адным файле альбо калі адзін чалавек вырашыў выдаліць яго, а другі вырашыў змяніць яго, Git не зможа вызначыць, якая версія з'яўляецца правільнай. Затым Git пазначыць файл як канфлікт - які вам давядзецца вырашыць, каб працягнуць працу. + +# Як вырашыць канфлікт аб аб'яднанні? + +Сутыкнуўшыся з канфліктам зліцця, git пазначыць праблемную вобласць у файле, уключыўшы яе ў “<<<<<<<< HEAD” and “>>>>>>>>>>[other branch name]” + +Змесціва пасля першага маркера паходзіць з вашай бягучай галіны. Пасля кутніх дужак, Git паведамляе нам, адкуль (з якой галіны) адбыліся змены. Радок з "=======" падзяляе два супярэчлівыя змены. +Наша задача складаецца ў тым, каб ачысціць гэтыя радкі: калі мы скончым, файл павінен выглядаць так, як мы хочам, каб ён выглядаў. Пажадана звярнуцца да таварыша па камандзе, які напісаў супярэчлівыя змены, каб вырашыць, якая версія павінна быць канчатковай. Гэта можа быць альбо ваша - альбо можа быць сумесь паміж імі. + +напрыклад: +``` + <<<<<<< HEAD:mergetest + This is my third line + ======= + This is a fourth line I am adding + >>>>>>> 4e2b407f501b68f8588aa645acafffa0224b9b78:mergetest +``` + +`<<<<<<<`: Пазначае пачатак радкоў, якія мелі канфлікт аб'яднання. Першы набор радкоў - гэта радкі з файла, у які вы спрабавалі аб'яднаць змены. +`=======`: Паказвае кропку перапынку, якая выкарыстоўваецца для параўнання. Разбівае змены, якія карыстальнік здзейсніў (вышэй) да зменаў, якія адбываюцца ад аб'яднання (унізе), каб візуальна ўбачыць адрозненні. +`>>>>>>>`: Пазначае канец радкоў, якія мелі канфлікт зліцця. + +Вы можаце вырашыць канфлікт, адрэдагаваўшы файл, а затым злучыўшы яго ўручную. Гэта можа азначаць адмену альбо змены альбо чыё-небудзь ці далейшае спалучэнне двух. Вам таксама трэба выдаліць файлы <<<<<<<< ',' ======= 'і' >>>>>>> '. + +Пасля развязання канфлікту зрабіце `git add`. Не забудзьцеся запусціць тэсты, бо вы павінны пераканацца, што вы вырашылі канфлікт. + +Вы таксама можаце загрузіць розныя плагіны ў залежнасці ад IDE, які вы выкарыстоўваеце для больш простага спосабу ўрэгулявання канфліктаў аб'яднання. + +# Як адмяніць зліццё? +Калі вы хочаце адмяніць зліццё, то можаце зрабіць `git merge —abort` diff --git a/additional-material/translations/Belarusian/reverting-a-commit.by.md b/additional-material/translations/Belarusian/reverting-a-commit.by.md new file mode 100644 index 00000000000..3bbfc371276 --- /dev/null +++ b/additional-material/translations/Belarusian/reverting-a-commit.by.md @@ -0,0 +1,40 @@ +# Вярнуць каміт + +Скасаваць абавязацельства проста азначае стварыць зусім новы дакумент, які адмяняе ўсе +змены, унесеныя ў папярэдні. Гэта як рабіць `` CTRL + Z `` `на git. + +У Git пераўтварэнне палягчаецца, таму што кожны ўклад, які вы commit на свой аддалены сховішча, мае ўнікальны алфавітна-лічбавы ключ, вядомы пад назвай SHA (Secure Hash Algorithm). +Такім чынам, гэта азначае, што вы можаце вярнуць любыя абавязацельствы, пакуль у вас ёсць SHA. +Але потым, вы павінны быць асцярожныя, каб змяніць упарадкаванасць, каб не сапсаваць ваша сховішча. + +Каб выбраць SHA канкрэтнага абавязацельства, якое мы хочам адмяніць, зручны быў бы часопіс усіх дасягнутых намі абавязкаў. +Каб атрымаць гэта, мы запусцім каманду: +`` `git log --oneline` `` +Адзінае выкананне каманды `` git log`` таксама дасць нам SHA (у доўгай форме) +Аднак выкарыстанне сцяга `` --oneline `` кажа git, што мы хочам, каб ён быў адлюстраваны ў сціслым (адным радку) парадку для зручнага чытання. + +Першыя 7 знакаў, якія адлюстроўваюцца пры выкананні гэтай каманды, называюцца скарочаным хэшам фіксацыі. + +Напрыклад, вось што я атрымліваю, калі ў гэтым рэпазітары запускаю `` git log --oneline ``: +``` +389004d added spacing in title +c1b9fc1 Merge branch 'master' into tutorials +77eaafd added tutorial for reverting a commit +``` + +Гэта паказвае, што з дапамогай `` git log --oneline``, мы можам атрымаць спіс усіх абавязацельстваў, зробленых у сховішча, разам з першымі 7 сімваламі яго SHA. + +Давайце выкажам здагадку, што я хачу адмяніць здзяйсненне "дадання прамежкаў у загалоўку". Вось наступныя дзеянні: + +* Скапіруйце SHA дакумента, які ў дадзеным выпадку з'яўляецца `` 389004d `` +* Затым запусціце каманду ```git revert 389004d``` + +Гэта адкрые мой тэкставы рэдактар і прапануе мне адрэдагаваць паведамленне пра commit. +Вы можаце вырашыць пакінуць паведамленне commit як паведамленне па змаўчанні git, якое пачынаецца са слова `Revert` +альбо вы таксама можаце вырашыць наладзіць паведамленне па сваім гусце. + +* Далей я буду захоўваць і закрываць тэкставы рэдактар. +* Вярнуцца да каманднага радка. +* Запусціце `` `git push origin ` ``, каб націснуць на зваротныя змены ў Github. + +І гэта ўсё, змены будуць адменены. У гэтым выпадку маё сховішча будзе зменена на тое, як яно выглядала ў `` c1b9fc1`` diff --git a/additional-material/translations/Belarusian/squashing-commits.by.md b/additional-material/translations/Belarusian/squashing-commits.by.md new file mode 100644 index 00000000000..d700fee670e --- /dev/null +++ b/additional-material/translations/Belarusian/squashing-commits.by.md @@ -0,0 +1,86 @@ +# Што такое squashing? + +У git, squashing маецца на ўвазе перапісванне гісторыі вашых учынкаў, таму вы ў канчатковым выніку займаецеся апісаннем зробленых змяненняў. +Звычайна гэта робіцца ў праектах з адкрытым зыходным кодам, таму што шмат гісторыяў філіялаў у праектах з адкрытым зыходным кодам мае дачыненне толькі да распрацоўшчыка, які іх стварыў, і гэта дае больш просты спосаб апісаць унесеныя змены, а таксама пры неабходнасці аднавіць іх. + +# Як вы робіце squash камітаў? + +Па-першае, выканаць часопіс git, каб прааналізаваць каміт, якія вы хацелі б аб'яднаць у вашай бягучай галіны. + +``` +git log +``` + +Вы павінны ўбачыць шэраг сваіх абавязацельстваў так: + +``` +commit blablabla +Author: omguhh +Date: 10/10/20 + Commit message 1 + +commit blablabla2 +Author: omguhh +Date: 10/10/20 + Commit message 2 +``` + +Такім чынам, зараз, калі вы бачыце каміты, якія вы хочаце злучыць з адным, мы можам перайсці да гэтага з `` git rebase `` . Зыходзячы з таго, што вы ўжо знаёмыя з `` git rebase `` , мы можам пачаць squashing камітаў ў інтэрактыўным рэжыме git rebase, які можна актываваць так: + +``` +git rebase -i +``` + +Цяпер, пры дапамозе інтэрактыўнага rebasing вы можаце вызначыць пачатковую і канчатковую кропку таго, як далёка вы хочаце ісці з такімі ўчынкамі: + +``` +git rebase -i HEAD~2 +``` + +Запуск гэтай каманды пакажа вам нешта падабаецца наступнае: + +``` +pick blablabla Changing test01.txt file +pick blablabla2 Adding dummy01.txt file + +# +# Commands: +# p, pick = use commit +# r, reword = use commit, but edit the commit message +# e, edit = use commit, but stop for amending +# s, squash = use commit, but meld into previous commit +# f, fixup = like "squash", but discard this commit's log message +# x, exec = run command (the rest of the line) using shell +# +# These lines can be re-ordered; they are executed from top to bottom. +# +# If you remove a line here THAT COMMIT WILL BE LOST. +# +# However, if you remove everything, the rebase will be aborted. +# +# Note that empty commits are commented out +``` + +Такім чынам, калі вы хочаце squash ``` blablabla2``` на ``` blablablabla```, вы змяніце наступнае: + +``` +pick blablabla Changing test01.txt file +squash blablabla2 Adding dummy01.txt file + +``` + +Калі ўсё пойдзе добра, вы атрымаеце такі вынік: + +``` +# This is a combination of 2 commits. +# The first commit's message is: +commit message 1 + +# This is the 2nd commit message: + +commit message 2 +``` + +Што вы можаце свабодна змяніць, перш чым вырашыць выйсці з рэдактара, каб захаваць гэтыя змены. + +Запуск часопіса git павінен паказаць вам паведамленне аб здзяйсненні, якое вы ўвялі перад выхадам на экран, з абавязацельствамі, аб'яднанымі ў адзін. diff --git a/additional-material/translations/Belarusian/stashing-a-file.by.md b/additional-material/translations/Belarusian/stashing-a-file.by.md new file mode 100644 index 00000000000..bec8fc103d9 --- /dev/null +++ b/additional-material/translations/Belarusian/stashing-a-file.by.md @@ -0,0 +1,137 @@ +# Прыхаваць + +Што рабіць, калі вы працуеце над вялікім кодам і раптам вам трэба пераключыць галіну, з якой вы зараз працуеце, на іншую. Паколькі код не з'яўляецца поўным і без якіх-небудзь тэстаў вы, верагодна, не хочаце яго commit. Але вы не можаце перайсці ў іншую галіну без унясення змяненняў, Git не дазволіць вам парушыць гэты паток. Што мы тады робім? Як мы прадухіляем непатрэбнае commit, маючы магчымасць скакаць з галінак? Вось што ахоплівае гэты падручнік. + +## Схаванне працы + +Дапусцім, што вы працуеце ў аддзяленні праекта, дзе вы змянілі некаторыя файлы. Цяпер, калі вы запусціце ``git status``, вы можаце ўбачыць змены ў файлах. + +``` +$ git status +# On branch master +# Changes to be committed: +# (use "git reset HEAD ..." to unstage) +# +# modified: index.html +# +# Changes not staged for commit: +# (use "git add ..." to update what will be committed) +# +# modified: lib/simplegit.rb +# +``` + +Цяпер вы хочаце пераключыць сваю галіну, але пакуль не хочаце ўносіць змены; каб вы захавалі змены. +Каб націснуць на stack новы сродак, запусціце `` git stash``: + +``` +$ git stash +Saved working directory and index state \ + "WIP on master: 049d078 added the index file" +HEAD is now at 049d078 added the index file +(To restore them type "git stash apply") +``` + +Цяпер ваш працоўны каталог чысты, выкарыстоўвайце ```git status```: + +``` +$ git status +# On branch master +nothing to commit, working directory clean +``` + +Цяпер вы можаце перайсці ў любую галіну і зрабіць сваю працу; схаваныя змены захоўваюцца ў выглядзе stack. Каб даведацца, якія stashes вы захоўваеце ў stack, вы можаце выкарыстоўваць `` git stash list``: + +``` +$ git stash list +stash@{0}: WIP on master: 049d078 added the index file +stash@{1}: WIP on master: c264051 Revert "added file_size" +stash@{2}: WIP on master: 21d80a5 added number to log +``` + +У выпадку, калі вы хочаце паўторна ўжыць змены, якія вы толькі што схавалі, вы можаце скарыстацца камандай `` git stash apply``. З дапамогай гэтай каманды вы можаце паўторна ўжыць апошні захованы файл. Для таго, каб паўторна прымяніць любы іншы файл, вы можаце пазначыць яго, назваўшы яго так: ```git stash apply ```, замест `` `` `` напішыце імя stash i трэба зноў падаваць. + +``` +$ git stash apply +# On branch master +# Changes not staged for commit: +# (use "git add ..." to update what will be committed) +# +# modified: index.html +# modified: lib/simplegit.rb +# +``` + +Вы можаце бачыць, што git паўторна змяняе файл, які вы выдалілі, калі вы захавалі пазыцыю. У гэтым выпадку ў вас быў чысты рабочы каталог, калі вы спрабавалі прымяніць stash, і вы паспрабавалі прымяніць яго ў той жа галіны, ад якой вы захавалі; але мець чыстую працоўную дырэкторыю і ўжываць яе ў той жа галінцы не трэба, каб паспяхова ўжываць скрыні. Вы можаце захаваць скрыні на адной галінцы, перайсці на іншую галінку пазней і зноў ужыць змены ў новай галінцы. Вы таксама можаце мець змененыя і неадкрытыя файлы ў вашым працоўным каталогу, калі вы ўжываеце stash, git дае канфлікты зліцця, калі што-небудзь больш не ўжываецца чыста. + +Змены, унесеныя ў вашыя файлы, паўторна ўжываюцца, але файл, які вы стварылі, не быў перазагружаны. Для гэтага вам трэба выканаць каманду `` git stash apply`` з ```--index```, каб сказаць камандзе зноў прымяняць паэтапныя змены. Калі б вы запусцілі гэта, вы вярнуліся ў зыходнае становішча: + +``` +$ git stash apply --index +# On branch master +# Changes to be committed: +# (use "git reset HEAD ..." to unstage) +# +# modified: index.html +# +# Changes not staged for commit: +# (use "git add ..." to update what will be committed) +# +# modified: lib/simplegit.rb +# +``` + +Каманда ўжываць прымяняецца толькі для зачыненай працы, але ў вас усё яшчэ ёсць у вашым stack. Для таго, каб выдаліць яго, вы можаце запусціць `` git stash drop`` з іменем stack для выдалення. + +``` +$ git stash list +stash@{0}: WIP on master: 049d078 added the index file +stash@{1}: WIP on master: c264051 Revert "added file_size" +stash@{2}: WIP on master: 21d80a5 added number to log +$ git stash drop stash@{0} +Dropped stash@{0} (364e91f3f268f0900bc3ee613f9f733e82aaed43) +``` + +Вы можаце выкарыстоўваць `` git stash pop``, каб выдаліць апошнія змены, выдаліўшы іх са свайго stack. + +## Адмена прымянення stash + +У некаторых выпадках вы хочаце прымяніць затоеныя змены, выканаць некаторыя працы, але ўжываць змены, якія першапачаткова прыйшлі з stash. Git не падае такую каманду, як `` git unapply` ``, але можна дасягнуць гэтага эфекту, проста здабыўшы patch, звязаны са stash, і прымяніць яго ў зваротным парадку: + +```$ git stash show -p stash@{0} | git apply -R``` + +Зноў жа, калі вы не ўкажыце stash, Git мяркуе самую свежую stash: + +```$ git stash show -p | git apply -R``` + +Магчыма, вы захочаце стварыць псеўданім і эфектыўна дадаць каманду `` stash-unapply`` у свой Git. Напрыклад: + +``` +$ git config --global alias.stash-unapply '!git stash show -p | git apply -R' +$ git stash apply +$ #... work work work +$ git stash-unapply +``` + +## Стварэнне аддзялення з stash + +Калі вы захоўваеце якую-небудзь працу, пакіньце яе там на некаторы час і працягвайце працу на той галінцы, з якой вы схавалі працу, у вас могуць паўстаць праблемы пры паўторнай працы. Калі заяўка паспрабуе змяніць файл, які вы ў свой час змянілі, у вас атрымаецца канфлікт аб'яднання, і вам прыйдзецца яго вырашыць. Калі вы хочаце больш проста пратэставаць схаваныя змены, вы можаце запусціць `` git stash branch``, які стварае для вас новае аддзяленне, правярайце абавязацельствы, якія вы выконвалі, калі вы прыхавалі працу, і зноў адпраўляе сваю працу. там, а затым скідае скрыню, калі яна паспяхова ўжываецца: + +``` +$ git stash branch testchanges +Switched to a new branch "testchanges" +# On branch testchanges +# Changes to be committed: +# (use "git reset HEAD ..." to unstage) +# +# modified: index.html +# +# Changes not staged for commit: +# (use "git add ..." to update what will be committed) +# +# modified: lib/simplegit.rb +# +Dropped refs/stash@{0} (f0dfc4d5dc332d1cee34a634182e168c4efc3359) +``` + +Гэта добры цэтлік, каб лёгка аднавіць схаваную працу і працаваць над ёй у новым аддзяленні. \ No newline at end of file diff --git a/additional-material/translations/Belarusian/undoing-a-commit.by.md b/additional-material/translations/Belarusian/undoing-a-commit.by.md new file mode 100644 index 00000000000..9480aade576 --- /dev/null +++ b/additional-material/translations/Belarusian/undoing-a-commit.by.md @@ -0,0 +1,59 @@ +# Адмяніць мясцовыя каміты + +Каб адмяніць мясцовыя каміты, усё, што вам трэба зрабіць, гэта +``` +git reset +``` + +Гэтая каманда прывядзе да скіду staging вобласці да апошні каміт, але змены, якія ўнесены ў ваш працоўны каталог, не зменіцца. Такім чынам, вы ўсё яшчэ можаце зноў камітаць тое, што вы змянілі. +Ці, калі вы хочаце выдаліць толькі адзін файл з папярэдняга каміту. Затым вы можаце зрабіць каманду ніжэй + +``` +git reset +``` +Каманда выдаліць толькі пазначаны файл з staging вобласці, але змены, унесеныя ў файл, усё яшчэ застануцца. + +Прыклад выкарыстання ```git reset``` +``` +# Make changes in index.php and tutorial.php +# Add files into the staging area +$ git add . +# Remembered both files need to be committed separately +# Unstage tutorial.php +$ git reset tutorial.php +# Commit index.php first +$ git commit -m "Changed index.php" +# Commit tutorial.php now +$ git add tutorial.php +$ git commit -m "Changed tutorial.php" +``` + +Дапусцім, калі вы пераблыталі сваё лакальнае сховішча і проста хочаце скінуць яго на апошні ўдзел. +Затым вы можаце запусціць каманду ніжэй. +``` +git reset --hard +``` + +Каманда не толькі скіне ваша staging вобласць, але і верне ўсе вашы змены ў файлах да вашай апошняй commit. +Рэжым `` --hard `` загадвае Git таксама адмяняць усе змены ў працоўным каталогу. +Вы павінны запускаць гэта толькі тады, калі вы сапраўды ўпэўненыя ў тым, што выкінеце цэлае local development. + +Прыклад выкарыстання ```git reset --hard``` +``` +# Decided to start a crazy experiment +# Create a new file 'crazy.php' and add some code to it +# Commit crazy.php +$ git add crazy.php +$ git commit -m "Started a crazy dev" +# Edit crazy.php file again and changed a lot other files +# Commit all tracked files +$ git add . +$ git commit -m "Continued dev" +# Tested and things went out of hand +# Decided to remove the whole things +$ git reset --hard HEAD~2 +``` + +```git reset --hard HEAD~2``` перамяшчае бягучую галінку назад на 2 commits адначасова, аднаўляючы ўсе зробленыя вамі змены і выдаляючы 2 здымкі, якія мы толькі што стварылі з гісторыі праектаў. + +P.s. Ніколі не выконвайце `` git reset --hard```, калі вы ўжо перанеслі свае commits ў агульнае сховішча, паколькі гэта прывядзе да праблем з усімі рэпазітарамі. diff --git a/additional-material/translations/Chinese/addtional-material.cht.md b/additional-material/translations/Chinese/addtional-material.cht.md new file mode 100644 index 00000000000..590d4d57e2a --- /dev/null +++ b/additional-material/translations/Chinese/addtional-material.cht.md @@ -0,0 +1,46 @@ +# 附加資料 + +我們認為你在來到這裡以前已經完成基本教學。附加資料會給你關於 Git 進階技術的資訊。 + +### [從你的 repository 刪除分支](../removing-branch-from-your-repository.md) +這份文件教你如何從 repository 刪除分支。 +> 在做這些步驟前確定你的 pull request 是被合併的 + +### [保持你的分叉與 repository 同步](../keeping-your-fork-synced-with-this-repository.md) +這份文件提供保持分叉與原始 repository 同步的資料。這件事情是很重要的，因為有其他人會對 project 做出貢獻。 +> 如果你的分叉沒有對原始 repository 做改變，根據這些步驟做操作。 + +### [回復 commit](../reverting-a-commit.md) +這份文件提供如何對遠端 repository 回復 commit。這項操作適用在你需要回復 commit，但你已經 push 到 Github。 +> 如果你想要回復 commit，根據這些步驟操作。 + +### [修訂 commit](../amending-a-commit.md) +這份文件教你如何在修訂在遠端的 commit。 +> 在你需要調整 commit 的時候使用這個。 + +### [回復本地的 commit](../undoing-a-commit.md) +這份文件教你如何回復本地的 commit。在你覺得你搞砸了本地的 repository，並且希望重置你的 repository時，照著做就對了。 +> 如果你需要回復/重置 commit 時，跟著做吧。 + +### [解決合併時的衝突](../resolving-merge-conflicts.md) +這份文件教你解決合併時的衝突。 +> 跟著這些步驟來解決煩人的衝突。 + +### [刪除檔案](../removing-a-file.md) +這份文件教你從本地 repository 中刪除檔案。 +> 跟著這些步驟學習如何從之前的 commit 中刪除檔案。 + +### [移動 commit 到另一個分支](../moving-a-commit-to-a-different-branch.md) +這份文件教你如何移動 commit 到另一個分支。 +> 跟著步驟移動 commit 到另一個分支。 + +### [配置 git](../configuring-git.md) +這份文件教你設定 git 的使用者資料與其他選項。 +> 閱讀這份文件讓你對 git 配置更有掌握。 + +### [好用的連結](../Useful-links-for-further-learning.md) +這份文件包含許多好用的部落格文章、網站、提示和小技巧，了解這些讓我們可以更容易上手。這一頁應該當做好用連結的索引，讓開源的新手還有想認識開源的人可以了解更多。 + +### [擠壓 commits](../squashing-commits.md) +這份文件教你如何藉由互動式 rebase 擠壓 commits。 +> 如果你想要發出一個 PR，但檢閱者要求你將一部份 commits 擠壓成一個 commits 藉由互動式 rebase。 diff --git a/additional-material/translations/French/additional-material.fr.md b/additional-material/translations/French/additional-material.fr.md new file mode 100644 index 00000000000..93247569142 --- /dev/null +++ b/additional-material/translations/French/additional-material.fr.md @@ -0,0 +1,49 @@ +# Additional information +Nous partons du principe que vous avez déjà lu le tutoriel basique avant de vous rendre ici. Ce document vous donnera des informations complémentaires +sur les techniques avancées de Git. + +### [Modifier un commit](amending-a-commit.md) +Cette page vous donnera les informations dont vous avez besoin pour modifier un commit sur un répertoire distant : +> Utilisez ceci pour corriger un commit que vous avez réalisé. + +### [Configurer git](configuring-git.md) +Cette page vous donnera les informations dont vous avez besoin pour configurer les détails utilisateur vous concernant et d'autres options dans git : +> A utiliser pour un meilleur contrôle de la configuration de votre git. + +### [Gardez votre embranchement (fork) synchronisé avec le répertoire](keeping-your-fork-synced-with-this-repository.md) +Ce document vous donne les informations pour conserver un répertoire "fork" à jour avec le répertoire source. Ceci est important et nous espérons que vous et beaucoup d'autres vont contribuer à ce projet. +> Suivez ces étapes si vous ne voyez aucun changement sur votre embranchement dans le répertoire parent. + +### [Déplacer un Commit vers une Branche différente](moving-a-commit-to-a-different-branch.md) +Cette page vous donnera les informations dont vous avez besoin pour déplacer un Commit vers une Branche différente : +> Suivez ces étapes pour déplacer un Commit vers une Branche différente. + +### [Supprimer un Fichier](removing-a-file.md) +Cette page vous donnera les informations dont vous avez besoin pour supprimer un Fichier depuis votre répertoire local : +> Suivez ces étapes pour apprendre comment supprimer un fichier avant d'effectuer un commit. + +### [Supprimer une branche dans votre répertoire](removing-branch-from-your-repository.md) +Cette page vous donnera les informations dont vous avez besoin pour supprimer une branche de votre répertoire : +> Ne suivez ces étapes qu'une fois que votre demande de tirage a été fusionnée. + +### [Résoudre les conflits de fusion (Merge Conflicts)](resolving-merge-conflicts.md) +Cette page vous donnera les informations dont vous avez besoin pour résoudre les problèmes de fusion : +> Suivez ces étapes pour résoudre ces problèmes de fusion (souvent pénibles). + +### [Revenir à un commit](reverting-a-commit.md) +Cette page vous aidera si vous avez besoin de revenir à un commit précédent, sur le répertoire distant. Ceci est pratique dans le cas où vous auriez besoin d'annuler un commit que vous auriez déjà poussé sur Github. +> Suivez ces étapes si vous souhaitez reprendre un commit. + +### [Applatir des Commits](squashing-commits.md) +Cette page vous apprendra comment applatir plusieurs commits en un seul. +> A utiliser si vous voulez ouvrir une demande de révision (pull request) et que l'évaluateur vous demande d'"applatir" tous les commits en un seul, contenant un message d'information global. + +### [Annuler un commit local](undoing-a-commit.md) +Cette page vous donne les informations dont vous avez besoin pour annuler un commit sur votre répertoire local. C'est ce que vous aurez besoin de faire si vous sentez que vous avez fait une erreur dans votre répertoire local et que vous voulez revenir à l'état précédent. +> Suivez ces instructions si vous voulez annuler / revenir à l'état précédent sur un commit local. + +### [liens utiles](Useful-links-for-further-learning.md) +Cette page est dédiée à tous les sites de trucs et astuces, les blogs, et en règle générale les site qui nous aident à rendre nos vies plus faciles. Ils sont d'excellentes références pour répondre à tous vos besoins, que vous soyez débutant ou expert. Cette page devrait être un index de tous ces liens utiles qui aideront tous ceux qui sont nouveaux dans le domaine de l'open-source ou ceux qui veulent approfondir leurs connaissances. + +### [Créer un fichier .gitignore](creating-a-gitignore-file.md) +Ce document explique à quoi sert un fichier .gitignore, pourquoi l'utiliser et comment le créer. Ce fichier est utilisé dans quasiment tous les projets git. Il aide à ne prendre en compte dans les commits que les fichiers nécessaires. diff --git a/additional-material/translations/French/amending-a-commit.fr.md b/additional-material/translations/French/amending-a-commit.fr.md new file mode 100644 index 00000000000..b99167e8a2d --- /dev/null +++ b/additional-material/translations/French/amending-a-commit.fr.md @@ -0,0 +1,52 @@ +# Modifier un commit + +Imaginons que vous avez effectué un commit sur votre répertoire distant et que vous vous rendez compte plus tard qu'il +y a une coquille dans le message de commit ou que vous avez oublié d'ajouter une ligne dans votre tout dernier commit. +Comment faire pour rectifier cette erreur ? C'est le sujet de ce tutoriel. + +## Changer un message de commit récent après l'avoir poussé sur Github +Pour se faire sans même ouvrir un fichier : +* Taper la commande ```git commit --amend -m "suivi de votre nouveau message de commit"``` +* Lancer la commande ```git push origin ``` pour effectuer un commit vers le répertoire. + +NB : Si vous tapez uniquement ```git commit --amend```, l'éditeur de texte s'ouvre et vous demande de modifier le +message de commit. Ajoutez l'option ``-m`` pour éviter de passer par l'éditeur de texte. + +## Modifier un commit précis + +Donc, qu'est-ce qu'il se passe si vous oubliez de faire un changement mineur sur un fichier, comme changer un mot et +que vous avez déjà poussé ce commit vers notre répertoire distant ? + +Pour illustrer ce propos, voici un log de mes commits ; +``` +g56123f création d'un fichier bot +a2235d mise à jour de contributeur.md +a5da0d modification du fichier bot +``` +Imaginons que j'ai oublié d'ajouter un mot dans le fichier bot. + +Il y a deux façons de régler ce problème. Le premier est de faire un nouveau commit qui contient le changement comme ceci : +``` +g56123f création d'un fichier bot +a2235d mise à jour de contributeur.md +a5da0d modification du fichier bot +b0ca8f ajout d'un mot dans le fichier bot +``` +La seconde façon est de modifier le commit a5da0d et d'ajouter ce nouveau mot puis le pousser sur Github le tout dans un seul commit. +Cette deuxième option semble plus adaptée, étant donné qu'il s'agit d'un changement mineur. + +Pour se faire, il faut suivre les étapes suivantes : +* Modifier le fichier. Dans notre cas, on modifie le fichier bot pour y inclure le mot oublié. +* Ensuite, ajouter le fichier dans la zone de transit avec la commande ```git add ``` + +D'habitude, après avoir ajouté des fichiers dans la zone de transit, l'étape suivante est d'exécuter la commande +git commit -m "notre message de commit", n'est-ce pas ? Mais comme ce qu'on veut ici c'est modifier le commit +précédent, on va plutôt lancer les commandes : + +* ```git commit --amend``` + Cela va faire apparaître l'éditeur de texte qui vous demande de modifier le message. Vous pouvez décider de laisser le + message tel quel ou bien le changer. +* Quitter l'éditeur +* Pousser vos changements avec la commande ```git push origin ``` + +De cette façon, les deux changements se trouvent dans un même commit. diff --git a/additional-material/translations/Hindi/moving-a-commit-to-a-different-branch.hi.md b/additional-material/translations/Hindi/moving-a-commit-to-a-different-branch.hi.md new file mode 100644 index 00000000000..59164dd5eaf --- /dev/null +++ b/additional-material/translations/Hindi/moving-a-commit-to-a-different-branch.hi.md @@ -0,0 +1,25 @@ +# एक कमिट शाखा को एक अलग शाखा में ले जाना +क्या होगा यदि आप कोई बदलाव कमिट करते हैं, और फिर महसूस करें कि आप एक अलग शाखा में आए हैं? +आप इसे कैसे बदल सकते हैं? यह ट्यूटोरियल कवर करता है। + +## सबसे मौजूदा काम को मौजूदा शाखा में ले जाना +ऐसा करने के लिए, टाइप करें: + +``` git reset HEAD~ --soft ```- अंतिम कमिट को पूर्ववत करता है, लेकिन उपलब्ध परिवर्तनों को छोड़ दें। +``` git stash ```- निर्देशिका की स्थिति रिकॉर्ड करता है। + +``` git checkout name-of-the-correct-branch ``` - दूसरी शाखा में स्विच करता है। +``` git stash pop ``` - आखिरी स्टेशेड स्टेटस को हटा देता है। +``` git add ``` - या अलग-अलग फाइलों को एक साथ स्टेज करने का प्रयास करें। +``` git commit -m "आपका संदेश यहां" ``` - परिवर्तनों को सुरक्षित कर देता है और कमिट करता है। + +अब आपके परिवर्तन सही शाखा पर हैं + + +### सबसे पुराना काम एक नई शाखा में ले जाना +ऐसा करने के लिए, टाइप करें: +``` git branch newbranch```- एक नई शाखा बनाता है। सभी कमिट को सुरक्षित कर देता है। +``` git reset --hard HEAD~#``` - मास्टर को वापस #कमिट में ले जाएं। याद रखें, यह काम मास्टर से जा चूका होगा +``` git checkout newbranch``` - आपके द्वारा बनाई गई शाखा में जाता है। इसमें सभी कमिट होंगे। + +याद रखें: कोई भी बदलाव कमिट नहीं किया गया तो खो जाएगा। \ No newline at end of file diff --git a/additional-material/translations/Hindi/nepali.np.md b/additional-material/translations/Hindi/nepali.np.md new file mode 100644 index 00000000000..59164dd5eaf --- /dev/null +++ b/additional-material/translations/Hindi/nepali.np.md @@ -0,0 +1,25 @@ +# एक कमिट शाखा को एक अलग शाखा में ले जाना +क्या होगा यदि आप कोई बदलाव कमिट करते हैं, और फिर महसूस करें कि आप एक अलग शाखा में आए हैं? +आप इसे कैसे बदल सकते हैं? यह ट्यूटोरियल कवर करता है। + +## सबसे मौजूदा काम को मौजूदा शाखा में ले जाना +ऐसा करने के लिए, टाइप करें: + +``` git reset HEAD~ --soft ```- अंतिम कमिट को पूर्ववत करता है, लेकिन उपलब्ध परिवर्तनों को छोड़ दें। +``` git stash ```- निर्देशिका की स्थिति रिकॉर्ड करता है। + +``` git checkout name-of-the-correct-branch ``` - दूसरी शाखा में स्विच करता है। +``` git stash pop ``` - आखिरी स्टेशेड स्टेटस को हटा देता है। +``` git add ``` - या अलग-अलग फाइलों को एक साथ स्टेज करने का प्रयास करें। +``` git commit -m "आपका संदेश यहां" ``` - परिवर्तनों को सुरक्षित कर देता है और कमिट करता है। + +अब आपके परिवर्तन सही शाखा पर हैं + + +### सबसे पुराना काम एक नई शाखा में ले जाना +ऐसा करने के लिए, टाइप करें: +``` git branch newbranch```- एक नई शाखा बनाता है। सभी कमिट को सुरक्षित कर देता है। +``` git reset --hard HEAD~#``` - मास्टर को वापस #कमिट में ले जाएं। याद रखें, यह काम मास्टर से जा चूका होगा +``` git checkout newbranch``` - आपके द्वारा बनाई गई शाखा में जाता है। इसमें सभी कमिट होंगे। + +याद रखें: कोई भी बदलाव कमिट नहीं किया गया तो खो जाएगा। \ No newline at end of file diff --git a/additional-material/translations/Hindi/removing-a-file.hi.md b/additional-material/translations/Hindi/removing-a-file.hi.md new file mode 100644 index 00000000000..246812e2fa8 --- /dev/null +++ b/additional-material/translations/Hindi/removing-a-file.hi.md @@ -0,0 +1,20 @@ +# गिट से एक फाइल को हटाना +कभी-कभी, आप किसी फ़ाइल को Git से हटाना चाहते हैं, लेकिन उसे अपने कंप्यूटर से हटाना नहीं चाहते हैं। आप निम्न आदेश का उपयोग करके इसे प्राप्त कर सकते हैं: + +``git rm --cached`` + +## तो क्या हुआ? +Git अब हटाए गए फ़ाइल में परिवर्तनों का ट्रैक नहीं रखेगा। जहां तक Git को पता है, ऐसा लगता है कि आपने फाइल को डिलीट कर दिया है। यदि आप अपने फाइल सिस्टम में फाइल का पता लगाने वाले थे, तो आप देखेंगे कि यह अभी भी वहीं है। + +ध्यान दें कि ऊपर के उदाहरण में, ``--cached`` फ्लैग का प्रयोग किया गया है। यदि हमने इस ध्वज को नहीं जोड़ा है, तो Git न केवल रेपो से, बल्कि आपके फ़ाइल सिस्टम से भी फ़ाइल को हटा देगा। + +यदि आप git commit ``-m "Remove file1.js"`` के साथ परिवर्तन करते हैं और इसे ``git push origin master`` का उपयोग करके दूरस्थ रिपॉजिटरी में धकेलते हैं, तो दूरस्थ रिपॉजिटरी फ़ाइल को हटा देगी। + +## अतिरिक्त सुविधाये +- यदि आप एक से अधिक फ़ाइलों को हटाना चाहते हैं, तो आप उन सभी को एक ही कमांड में शामिल कर सकते हैं: + +``git rm file1.js file2.js file3.js --cached`` + +- आप समान फ़ाइलों को निकालने के लिए वाइल्डकार्ड (*) का उपयोग कर सकते हैं। उदाहरण के लिए, यदि आप अपने स्थानीय भंडार से सभी .txt फ़ाइलों को हटाना चाहते हैं: + +``git rm *.txt --cached`` \ No newline at end of file diff --git a/additional-material/translations/Hindi/removing-branch-from-your-repository.hi.md b/additional-material/translations/Hindi/removing-branch-from-your-repository.hi.md new file mode 100644 index 00000000000..5f80032dfac --- /dev/null +++ b/additional-material/translations/Hindi/removing-branch-from-your-repository.hi.md @@ -0,0 +1,31 @@ +# अपने रिपॉजिटरी से एक शाखा निकालें + +यदि आपने अब तक ट्यूटोरियल का पालन किया है, तो हमारी `` शाखा ने अपना उद्देश्य पूरा कर लिया है, अब यह आपके स्थानीय मशीन के रेपो से इसे हटाने का समय है। यह आवश्यक नहीं है, लेकिन इस शाखा का नाम इसके बजाय विशेष उद्देश्य दिखाता है। इसका जीवन संगत रूप से छोटा हो सकता है। + +सबसे पहले, अपने मास्टर में अपने `` को मर्ज करें, इसलिए अपनी मास्टर शाखा पर जाएं: +``` +git checkout master +``` + +उसके बाद मास्टर में ``मर्ज करें: +``` +git merge master +``` + +फिर अपने स्थानीय मशीन के रेपो से `` निकालें: +``` +git branch -d +``` + +अब आपने अपनी स्थानीय मशीन की `` शाखा हटा दी है और सब कुछ साफ़ सुथरा लग रहा है। +हालांकि, इस समय, आपके पास अभी भी आपके गिटहब फोर्क में `` शाखा होनी चाहिए। हालांकि, इससे पहले कि आप इसे हटा दें, याद रखें कि आपने इस रिमोट शाखा से अपने रेपो को "पुल रिक्वेस्ट" भेजा है। इसलिए जब तक कि मैं इसे मर्ज नहीं करता हूं, इस शाखा को न हटाएं। + +हालांकि, अगर मैंने आपकी शाखा मर्ज कर ली है और आप रिमोट शाखा को हटाना चाहते हैं, तो इसका उपयोग करें: +``` +git push origin --delete +``` + +अब, आप जानते हैं कि अपनी शाखाओं को कैसे साफ किया जाए। +समय के साथ, मेरे सार्वजनिक रिपो में कई रेपो जोड़े जाएंगे। और आपकी स्थानीय मशीन और आपके गिटहब फर्क की मास्टर शाखाएं अद्यतित नहीं होंगी। तो अपने रेपोसिटोरिएस को मेरे साथ सिंक्रनाइज़ करने के लिए, नीचे दिए गए चरणों का पालन करें। + +#### [अपने फोर्क को रिपॉजिटरी के साथ सिंक रखना] (keeping-your-fork-synced-with-this-repository.md) \ No newline at end of file diff --git a/additional-material/translations/Indonesian/additional-material.id.md b/additional-material/translations/Indonesian/additional-material.id.md new file mode 100644 index 00000000000..259edea81a4 --- /dev/null +++ b/additional-material/translations/Indonesian/additional-material.id.md @@ -0,0 +1,46 @@ +# Informasi tambahan + +Kami berasumsi anda sudah menyelesaikan tutorial dasar sebelum datang ke sini. Informasi tambahan ini akan memberikan beberapa informasi mengenai teknik Git yang lebih tinggi. + +### [Hapus cabang dari repositori anda](removing-branch-from-your-repository.md) +Dokumen ini memberikan informasi mengenai bagaimana menghapus sebuah cabang dari repositori anda. +> Lakukan langkah ini setelah pull request anda digabungkan (merge). + +### [Agar fork anda tetap sinkron dengan repositori](keeping-your-fork-synced-with-this-repository.md) +Dokumen ini memberikan informasi mengenai bagaimana agar repositori yang kita fork tetap uptodate dengan repositori dasar. Hal ini penting, karena bisa jadi anda dan banyak kontributor lain berkontribusi dalam proyek tersebut. +> Ikuti langkah-langkahnya agar fork anda tidak punya banyak perubahan dengan repositori induk. + +### [Membatalkan commit](reverting-a-commit.md) +Dokumen ini memberikan informasi bagaimana caranya membatalkan commit di repositori remote. Langkah ini perlu jika sewaktu-waktu anda harus membatalkan sebuah commit yang telanjur sudah didorong ke GitHub. +> Ikuti langkah-langkahnya untuk membatalkan sebuah commit. + +### [Mengubah sebuah commit](amending-a-commit.md) +Dokumen ini memberikan informasi mengenai cara mengubah sebuah commit di repositori remote. +> Gunakan ini ketika kamu harus mengubah commit yang sudah dibuat. + +### [Membatalkan commit lokal](undoing-a-commit.md) +Dokumen ini memberikan informasi mengenai cara membatalkan sebuah commit di repositori lokal anda. Hal ini diperlukan ketika anda berpikir sudah merusak repositori lokal dan ingin me-reset repositori tersebut. +> Lakukan cara ini jika ingin membatalkan/reset commit di lokal. + +### [Mengatasi Merge Conflicts](resolving-merge-conflicts.md) +Dokumen ini memberikan informasi mengenai cara mengatasi saat terjadi konflik ketika melakukan merge. +> Lakukan langkah tersebut untuk mengatasi konflik merge yang mengganggu. + +### [Menghapus sebuah berkas](removing-a-file.md) +Dokumen ini memberikan informasi mengenai cara menghapus sebuah berkas dari repositori lokal. +> Ikuti langkah tersebut untuk mempelajari bagaimana menghapus sebuah berkas sebelum di-commit. + +### [Memindahkan Commit ke Cabang berbeda](moving-a-commit-to-a-different-branch.md) +Dokumen ini memberikan informasi mengenai cara memindahkan sebuah commit ke cabang lain. +> Ikuti langkah tersebut untuk memindahkan sebuah commit ke cabang lain. + +### [Mengonfigurasi git](configuring-git.md) +Dokumen ini memberikan informasi mengenai cara mengonfigurasi detil pengguna dan opsi lain di git. +> Gunakan langkah ini agar konfigurasi git anda menjadi lebih baik. + +### [Tautan bermanfaat](Useful-links-for-further-learning.id.md) +Dokumen ini didedikasikan untuk semua pos blog, laman yang sangat membantu, situs tip dan trik yang akan membuat hidup kita lebih mudah. Tautan tersebut tidak hanya untuk pemula, namun juga bagi yang sudah mahir. Halaman ini akan menjadi indeks untuk semua tautan yang bermanfaat yang mungkin saja bisa membantu siapapun yang baru terjun di dunia open-source atau siapapun yang ingin belajar lebih lanjut. + +### [Menyatukan banyak Commit](squashing-commits.md) +Dokumen ini menyediakan informasi mengenai bagaimana menyederhanakan banyak commit dengan rebase interaktif. +> Gunakan ini jika anda mau membuka sebuah PR dalam proyek open source dan periview meminta kamu untuk menyatukan setiap commit menjadi satu, dengan pesan commit yang informatif. diff --git a/additional-material/translations/Indonesian/removing-a-file.id.md b/additional-material/translations/Indonesian/removing-a-file.id.md new file mode 100644 index 00000000000..ae0d26bd657 --- /dev/null +++ b/additional-material/translations/Indonesian/removing-a-file.id.md @@ -0,0 +1,23 @@ +# Menghapus file + +Terkadang Anda ingin menghapus file dari Git, tetapi Anda tidak ingin menghapusnya dari komputer Anda. Anda dapat melakukan ini dengan menggunakan perintah berikut: + +`git rm --cached` + +## Apa yang terjadi? + +Git tidak akan lagi melacak perubahan pada file yang dihapus. Adapun Git, file ini sudah tidak ada lagi. Jika Anda mencari file di disk Anda, Anda melihat bahwa file itu masih ada. + +Pada contoh di atas, kita menggunakan flag `--cached`. Jika kita tidak menggunakannya, Git juga akan menghapus file dari disk kita. + +Jika sekarang kita membuat komit dengan `git commit -m "Hapus file1.js"` dan kirimkan ke repositori jarak jauh dengan perintah `git push origin master`, file tersebut juga akan dihapus dari repositori jarak jauh. + +## Opsi tambahan + +- Jika Anda ingin menghapus banyak file, Anda dapat memasukkan semuanya dalam satu perintah: + + `git rm file1.js file2.js file3.js --cached` + +- Anda dapat menggunakan wildcard (\*) untuk menghapus file serupa. Misalnya, untuk menghapus semua file .txt dari repositori Anda, gunakan perintah: + + `git rm *.txt --cached` diff --git a/additional-material/translations/Italian/removing-a-file.it.md b/additional-material/translations/Italian/removing-a-file.it.md new file mode 100644 index 00000000000..dbd42bb6dbc --- /dev/null +++ b/additional-material/translations/Italian/removing-a-file.it.md @@ -0,0 +1,23 @@ +# Rimuovere un file da Git + +Può succedere che tu voglia rimuovere un file da Git, mantenendolo comunque nel tuo computer. Lo puoi fare eseguendo questo comando: + +``git rm --cached`` + +## Cosa fa questo comando? + +Git non terrà più conto dei cambiamenti inclusi nel file rimosso. Per Git, è come se tu avessi cancellato il file. Se però vai a cercare il file nel tuo sistema, vedrai che comunque è ancora lì. + +Come vedi, nell'esempio qui sopra viene usato il flag `--cached`. Senza questo flag Git rimuoverebbe il file non solamente dal repository, ma anche dal tuo sistema. + +Se decidi di validare questo cambiamento con `git commit -m "Remove file1.js"` e successivamente invii le modifiche al repository remoto usando `git push origin master`, vedrai che il repository remoto avrà rimosso il file. + +## Funzioni aggiuntive + +- Per rimuovere più di un file, puoi aggiungerli tutti allo stesso comando in questo modo: + + `git rm file1.js file2.js file3.js --cached` + +- Puoi usare il metacarattere asterisco (*) per rimuovere i file simili tra loro. Per esempio, se vuoi rimuovere tutti i file con estensione .txt dal tuo repository locale puoi farlo così: + + `git rm *.txt --cached` diff --git a/additional-material/translations/Korean/additional-material.ko.md b/additional-material/translations/Korean/additional-material.ko.md new file mode 100644 index 00000000000..7a05ff539e6 --- /dev/null +++ b/additional-material/translations/Korean/additional-material.ko.md @@ -0,0 +1,42 @@ +# 추가 정보 + +여러분이 여기에 오기 전에 기본실습 과정을 이미 완료했다고 가정합니다. 이곳에서는 고급 Git 기술에 대한 정보를 제공합니다. + +### [여러분의 저장소에서 브랜치 삭제하기](removing-branch-from-your-repository.ko.md) +이 문서는 저장소에서 브랜치를 삭제하는 방법에 대한 정보를 제공합니다. +> PR(pull request) 요청이 병합 된 후에 본 단계를 수행하십시오. + +### [여러분이 포크한 저장소와 싱크상태 유지하기](keeping-your-fork-synced-with-this-repository.ko.md) +이 문서는 포크 된 저장소를 기본 저장소로 최신 상태로 유지하는 방법에 대한 정보를 제공합니다. 여러분과 다른 많은 사람들이 프로젝트에 기여하기를 바랍니다. +> 포크 된 상위 저장소가 변경되지 않은 경우 다음 단계를 수행하십시오. + +### [커밋 되돌리기](reverting-a-commit.ko.md) +이 문서는 원격 저장소에서 커밋을 되돌리는 방법에 대한 정보를 제공합니다. 이미 Github에 푸시 된 커밋을 되돌리려는 경우 유용합니다. +> 커밋을 되돌리려면 이 단계를 수행하십시오. + +### [커밋 수정하기](amending-a-commit.ko.md) +이 문서는 원격 저장소에서 커밋을 수정하는 방법에 대한 정보를 제공합니다. +> 당신이 만든 커밋을 수정해야 할 때 사용하십시오. + +### [로컬 커밋 되돌리기](undoing-a-commit.ko.md) +이 문서는 로컬 저장소에서 커밋을 실행 취소하는 방법에 대한 정보를 제공합니다. 로컬 저장소가 엉망이라고 느껴 당신이 로컬 저장소를 리셋하고자 할 때 당신이 해야 할 일입니다. +> 로컬 커밋을 취소하려면 이 단계를 수행하십시오. + +### [병합 충돌 해결하기](resolving-merge-conflicts.ko.md) +이 문서는 병합 충돌을 해결하는 방법에 대한 정보를 제공합니다. +> 이 단계를 수행하여 곤란한 병합 충돌을 해결하십시오. + +### [커밋을 다른 브랜치로 이동하기](moving-a-commit-to-a-different-branch.ko.md) +이 문서는 커밋을 다른 브랜치로 이동하는 방법에 대한 정보를 제공합니다. +> 이 단계를 수행하여 커밋을 다른 브랜치로 이동하십시오. + +### [git 설정하기](../configuring-git.md) +이 문서는 git에서 사용자 정보 및 기타 옵션을 구성하는 방법에 대한 정보를 제공합니다. +> git 설정을 더 잘 다루려면 이 단계를 수행하십시오. + +### [유용한 링크](../Useful-links-for-further-learning.md) +이 문서는 모든 블로그 게시물, 유용한 사이트, 유용한 정보 및 웹 사이트에 대한 내용을 담고 있습니다. 우리가 모든 필요를 위해 참조하는 것은 초심자 또는 전문가 일 것입니다. 이 페이지는 오픈 소스 도메인을 처음 접하거나 더 많은 것을 배우고자 하는 사람들을 돕는 지표 역할을 해야 합니다. + +### [스쿼시 커밋하기](../squashing-commits.md) +이 문서는 대화형 리베이스로 커밋을 스쿼시하는 방법에 대한 정보를 제공합니다. +> 오픈 소스 프로젝트에서 PR을 보낼 때 리뷰어가 모든 커밋을 하나로 스쿼시하도록 요청하는 경우 유익한 커밋 메시지와 함께 이것을 사용하십시오. diff --git a/additional-material/translations/Korean/amending-a-commit.ko.md b/additional-material/translations/Korean/amending-a-commit.ko.md new file mode 100644 index 00000000000..8c609915f31 --- /dev/null +++ b/additional-material/translations/Korean/amending-a-commit.ko.md @@ -0,0 +1,46 @@ +## 커밋 수정하기 + +만약 커밋 메시지에 오타가 있거나 가장 최근의 커밋에서 몇줄을 빼먹은 걸 나중에 깨닫고 원격 저장소로 커밋을 수정하고자 하는 경우 어떻게 할까요? 이 자습서는 이러한 내용을 다룹니다. + +### Github에 이미 푸시한 후에 최근 커밋 메시지 변경하기 +파일을 열지 않고 수행할 경우: +* 다음을 타이핑합니다. ```git commit --amend -m "followed by your new commit message"``` +* 변경사항을 저장소에 커밋하려면 다음을 실행합니다. ```git push origin ``` + +참고: 단지 ```git commit --amend``` 이것만 입력한다면, 텍스트 편집기가 커밋 메시지를 입력하라고 할 것입니다. ``-m`` 플래그를 추가하면 이것을 막을 수 있습니다. + +### Modifying on a single commit + +그럼 한 단어를 변경하는 것과 같이 사소한 변경사항을 깜빡하고 커밋을 이미 원격 저장소에 푸시했다면 어떻게 해야 할까요? + +이를 설명하기 위해 여기 제 커밋 로그가 있습니다: +``` +g56123f create file bot file +a2235d updated contributor.md +a5da0d modified bot file +``` +봇 파일에 한 단어를 추가하는 것을 깜빡했다고 해 봅시다. + +이 경우 두가지 방법이 있습니다. 첫번째는 다음과 같이 변경사항을 포함하는 완전히 새로운 커밋을 수행하는 것입니다: +``` +g56123f create file botfile +a2235d updated contributor.md +a5da0d modified botfile +b0ca8f added single word to botfile +``` +두번째 방법은 a5da0d 커밋을 수정하고, 새 단어를 추가하고 이를 하나의 커밋으로 Github에 푸시하는 것 입니다. +이 방법은 사소한 변화이기 때문에 더 나을수도 있습니다. + +이를 위해 다음을 수행하십시오: +* 파일을 수정하십시오. 이 경우, 이전에 빠뜨린 단어를 포함하여 봇 파일을 수정합니다. +* 그 다음, ```git add ``` 을 실행하여 파일을 스테이징 영역으로 추가합니다. + +보통 파일을 스테이징 영역에 추가하고 나면, 다음으로 우리가 해야할 일은 git commit -m "our commit message" 입니다. +그러나 여기서 우리가 원하는 것은 이전 커밋을 수정하는 것이므로, 다음을 실행합니다: + +* ```git commit --ammend``` +그러면 텍스트 편집기가 뜨고 메시지를 수정하라는 프롬프트가 뜰 것입니다. 이전 그대로 메시지를 두거나 변경할 수 있습니다. +* 에디터를 빠져나오십시오. +* ```git push origin + +여러분의 두 개의 저장소들을 제 공개 저장소의 최신 상태와 싱크상태를 유지하기 위해서는 제일 먼저여러분의 로컬머신에 위치한 저장소를 제 공개 저장소와 fetch와 merge를 해야합니다. +두번째는 여러분의 로컬 저장소를 포크된 GitHub의 저장소에 push하는 것 입니다. 이전 과정에서 봤듯이 "pull request"를 요청할 수 있는 곳은 오직 포크된 저장소에서만 가능합니다. 따라서 마지막으로 업데이트 되어야하는 저장소는 포크된 GitHub입니다. +자, 어떻게하는지 보겠습니다: +먼저 여러분은 master 브랜치에 위치해 있어야합니다. 현재 어떤 브래치에 있는지 확인합니다.: +``` +git status +``` +현재 master 브랜치가 아니라면 변경합니다.: +``` +git checkout master +``` + +제 공개 저장소를 아직 여러분의 git에 추가하지 않았다면 다음 명령으로 추가합니다. `add upstream remote-url`: +``` +git remote add upstream https://github.com/Roshanjossey/first-contributions +``` +지정한 URL을 이용해 현재 프로젝트의 또 다른 최신 버전이 있는지 git에게 확인을 요청하는 방법입니다. 그리고 우리는 이를 `upstream` 이라고 부르기로합니다. 일단 git이 이러한 이름을 가지고 있다면 다음과 같이 공개 저장소의 최진 버전을 가지고 옵니다. : +``` +git fetch upstream +``` + +여러분은 이제 제 포크(upstream remote)에서 최신 버전을 내려 받았습니다. 이제 공개 저장소의 변경된 내용을 여러분의 master 브랜치에 병합해야합니다. +``` +git rebase upstream/master +``` + +여러분의 master 브랜치와 공개 저장소를 병합하고 나면 이제 여러분의 로컬머신의 master 브랜치는 최신 상태입니다. 마지막으로 여러분의 master 브랜치를 여러분의 포크에 push하게 되면 포크한 GitHub 또한 변경사항들이 반영됩니다.: +``` +git push origin master +``` +origin으로 명명된 리모트에 push하는 것에 주의하세요. +이제 여러분의 모든 저장소가 최신 상태를 유지하게 되었습니다. +잘 하셨습니다! GitHub 저장소에 커밋이 추가적으로 발생할 때마다 이러한 작업을 해야합니다. + + diff --git a/additional-material/translations/Korean/moving-a-commit-to-a-different-branch.ko.md b/additional-material/translations/Korean/moving-a-commit-to-a-different-branch.ko.md new file mode 100644 index 00000000000..0a7d6d0d2ed --- /dev/null +++ b/additional-material/translations/Korean/moving-a-commit-to-a-different-branch.ko.md @@ -0,0 +1,28 @@ +## 커밋을 다른 브랜치로 옮기기 + +What if you commit a change, and then realize that you committed to a different branch? +How can you change that? This is what this tutorial covers. +만일 변경사항을 반영했는데 전혀 다른 브랜치에 커밋한 사실을 알았다면 어떻게할까요? +이걸 어떻게 바로잡을 수 있을까요? 바로 이 장에서 다룰 내용입니다. + +### 가장 최근 커밋들을 기존에 있는 브랜치로 이동시키기 +사용예: + +```git reset HEAD~ --soft``` - 마지막 커밋을 되돌립니다. 물론 수정한 내용은 그대로 남아있습니다. +```git stash``` - 현재까지 수정한 모든 작업내용들의 상태를 저장합니다. + +```git checkout name-of-the-correct-branch``` - 실제 반영하고자하는 브랜치를 체크아웃합니다. +```git stash pop``` - 마지막으로 저장한(stash) 변경내역들을 현재 브랜치에 반영하고 저장한 내역에서 삭제합니다. +```git add .``` - 또는 커밋에 반영할 변경내역들을 개별적으로 추가합니다. +```git commit -m "your message here"``` - 저장하고 변경내역을 커밋합니다. + +자 이제 변경사항이 올바른 브랜치에 반영되었습니다. + +### 가장 최근 커밋들을 신규 브랜치를 생성하여 이동시키기 + +사용예: +```git branch newbranch``` - 신규 브랜치를 생성하고 모든 커밋들을 저장합니다. +```git reset --hard HEAD~#``` - master 브랜치의 #번째 커밋을 되돌립니다. 되돌린 커밋들은 master에서 완전히 삭제되므로 주의하세요. +```git checkout newbranch``` - 생성한 브랜치로 이동합니다. 모든 커밋들을 가지고 있을겁니다. + +주의: 커밋하지 않은 변경사항들은 사라집니다. diff --git a/additional-material/translations/Korean/removing-branch-from-your-repository.ko.md b/additional-material/translations/Korean/removing-branch-from-your-repository.ko.md new file mode 100644 index 00000000000..b1e51ca2f96 --- /dev/null +++ b/additional-material/translations/Korean/removing-branch-from-your-repository.ko.md @@ -0,0 +1,30 @@ +## 여러분의 저장소에서 브랜치 삭제하기 + +지금까지의 튜토리얼을 수행했다면, 우리의 `` 브랜치가 목적을 완료했습니다. 이제는 로컬 저장소에서 삭제할 차례입니다. 필수사항은 아니지만 이 브랜치의 이름은 다소 특별한 목적을 나타내므로 이미 병합되었다면 그 수명을 다했다고 할 수 있습니다. +First, let's merge your `` to your master, so to go your master branch: +먼저, ``을 마스터에 합쳐야합니다. 마스터 브랜치로 이동합니다.: +``` +git checkout master +``` + +``를 마스터에 병합합니다.: +``` +git merge master +``` + +``를 로컬 저장소에서 삭제합니다.: +``` +git branch -d +``` + +이제 로컬 머신의 ``브랜치를 삭제했고 모든 것이 깔끔하게 보입니다. +이 시점에서 GitHub 포크에 여전히 `` 브랜치가 있어야합니다. 그러나 이것을 삭제하기 전에 이 원격지의 브랜치에서 상위 저장소로 "PR(Pull request)"을 보냈음을 기억하십시오. 따라서 아직 병합되지 않았다면이 브랜치를 삭제하지 마십시오. +그러나 해당 브래치를 이미 병합했고 원격 브랜치를 삭제하려면 다음을 사용하십시오.: +``` +git push origin --delete +``` + +자, 여러분은 이제 자신의 브래치를 정리하는 법을 배웠습니다. +시간이 지나면 많은 커밋이 저장소에 추가됩니다. 그리고 로컬 머신과 GitHub 포크의 마스터 브랜치는 최신 버전이 아닙니다. 따라서 저장소를 내 것과 동기화 된 상태로 유지하려면 아래 단계를 따르십시오. + +#### [여러분이 포크한 저장소와 싱크상태 유지하기](keeping-your-fork-synced-with-this-repository.ko.md) diff --git a/additional-material/translations/Korean/resolving-merge-conflicts.ko.md b/additional-material/translations/Korean/resolving-merge-conflicts.ko.md new file mode 100644 index 00000000000..a8b103ec93d --- /dev/null +++ b/additional-material/translations/Korean/resolving-merge-conflicts.ko.md @@ -0,0 +1,43 @@ +# 병합 충돌이 무엇인가요? + +여러분이 또 다른 브랜치에서 현재 작업중인 브랜치로 병합하고자할 때, 또 다른 변경사항들도 같이 반영되어야 하므로 여러분의 현재 작업중인 파일들에 같이 결합이 이루어지게 됩니다. +만일 이때 두 사람이 같은 파일의 똑 같은 라인을 (각자 다르게)변경했거나 다른 사람이 수정 반영한 곳을 삭제하려고 한다면 Git은 어느 변경사항이 옳은 것인지 쉽게 판단할 수 없습니다. +이때 Git은 여러분 스스로 이 문제를 반드시 해결하도록 충돌이 있음을 파일에 표시합니다. + + +# 병합 충돌은 어떻게 해결하나요? + +병합 충돌이 발생하면 Git은 문제가 되는 부분에 “<<<<<<<< HEAD” 와 “>>>>>>>>>>[other branch name]” 으로 감싸서 표시합니다. + +이때 여러분이 현재 작업중인 브랜치가 먼저 표기됩니다. 꺽쇠기호 뒤를 보면 어느 브랜치에서 변경사항이 반영되었는지 알 수 있습니다. +"=======" 기호는 충돌이 발생한 부분을 각각 구분해줍니다. +여러분이 해야할 일은 바로 위와 같은 충돌표시들을 원하는 코드만 보이도록 깨끗하게 정리하는 것입니다. +따라서 충돌을 발생케한 여러분의 동료와 어느 변경사항이 옳은 것인지 서로 이야기를 나눠야합니다. +여러분의 변경사항이 옳을 수도 있고 그렇지 않을 수도 있습니다. 아니면 양자 모두의 변경사항을 합쳐야만 하는 경우도 있을 수 있겠죠. + + +예시: +``` + <<<<<<< HEAD:mergetest + This is my third line + ======= + This is a fourth line I am adding + >>>>>>> 4e2b407f501b68f8588aa645acafffa0224b9b78:mergetest +``` + +<<<<<<<: 병합 충돌이 시작되는 곳을 표시합니다. 여러분이 병합하고자하는 변경한 라인들로 이루어진 부분이 첫번째로 표기됩니다. +=======: 비교하기 위한 구분선을 나타냅니다. 쉽게 차이를 파악할 수 있도록 사용자가 커밋한 변경사항(위)과 병합을 위해 로드된 부분(아래)으로 구분되어 있습니다. +>>>>>>>: 병합 충돌이 발생한 마지막 위치를 표시합니다. + + +Git에서 병합하는 것에 문제가 있는 부분을 일일이 수작업으로 편집해서 병합하면서 충돌문제를 해결합니다. +이는 여러분의 수정사항을 삭제하거나 다른 누군가의 변경사항을 지우는 일이며 또는 이 두 부분을 하나로 합치는 것을 의미합니다. +그리고 해당 파일에서 '<<<<<<<', '=======', 그리고 '>>>>>>>'을 지워야합니다. + +일단 충돌을 해결했다면 `git add`를 실행합니다. +아울러 충돌이 올바르게 해결되었는지 확인하기 위해 반드시 테스트를 수행하는 것을 잊지마십시요. + +병합 충돌을 보다 쉽게 해결하려면 여러분이 사용하는 각각의 IDE에 맞는 적절한 플러그인을 다운로드 받아 설치하세요. + +# 병합을 어떻게 되돌리나요? +병합을 취소하려면 `git merge —abort` 명령을 실행하세요. diff --git a/additional-material/translations/Korean/reverting-a-commit.ko.md b/additional-material/translations/Korean/reverting-a-commit.ko.md new file mode 100644 index 00000000000..c94f408e392 --- /dev/null +++ b/additional-material/translations/Korean/reverting-a-commit.ko.md @@ -0,0 +1,35 @@ +## 커밋 되돌리기 + +커밋을 되돌리려면 이전 커밋에서 수행 된 모든 변경 사항을 취소하는 새로운 커밋을 만드는 것입니다. 그것은 git에서 ```CTRL + Z ``` 를 실행하는 것과 같습니다. + +원격 저장소에 푸시하는 모든 커밋에는 SHA(Secure Hash Algorithm)라고 하는 고유한 알파벳 키가 있으므로 git에서 되돌리기가 쉬워집니다. 즉, SHA를 사용하는 한 언제든지 커밋을 되돌릴 수 있습니다. 하지만 그렇게 하면, 당신의 저장소가 엉망이 되지 않도록 조심스럽게 순서대로 배열해야 합니다. + +실행 취소하려는 특정 커밋의 SHA를 선택하려면 지금까지 작성한 모든 커밋의 로그가 도움이 될 것입니다. +이를 위해 다음 명령을 실행합니다: +```git log --oneline ``` +```git log``` 명령만 실행하면 SHA(긴 형식)을 얻을 수 있지만 ```--oneline ``` 플래그를 사용하면 보다 가독성이 좋은(한줄) 방식으로 표시할 수 있습니다. + +이 명령을 실행할 때 표시되는 첫번째 7개의 문자는 축약 커밋 해시라고 합니다. + +예를 들어, 이 저장소에서 ```git log --oneline ``` 을 실행하면 다음과 같은 결과를 얻을 수 있습니다: +For example, here is what I get when I run ```git log --oneline ``` on this repository: +``` +389004d added spacing in title +c1b9fc1 Merge branch 'master' into tutorials +77eaafd added tutorial for reverting a commit +``` + +따라서 ```git log --oneline``` 을 사용하면 SHA의 처음 7개의 문자와 함께 저장소에서 작성한 모든 커밋 목록을 가져올 수 있습니다. + +이제 "added spacing in title"에 대한 커밋을 취소하고 싶다고 가정하고, 다음 단계를 수행하겠습니다. + +* 커밋의 SHA를 복사합니다. 여기서는 ```389004d``` 입니다. +* 그리고 나서 ```git revert 389004d``` 명령을 싱행합니다. + +이렇게 하면 텍스트 편집기가 열리고 커밋 메시지를 편집하라는 메시지가 표시됩니다. 커밋 메시지를 `Revert` 라는 단어로 시작하는 기본 git 메시지로 남겨두거나 원하는대로 메시지를 작성할 수도 있습니다. + +* 다음으로, 텍스트 편집기를 저장하고 닫습니다. +* 커맨드 라인으로 돌아갑니다. +* ```git push origin ``` 을 실행하여 되돌린 변경사항을 Github에 푸시하십시오. + +그리고 바로 변경사항이 원상태로 돌아갈 것입니다. 이 경우에 저장소가 ```c1b9fc1``` 의 상태로 되돌아갑니다. diff --git a/additional-material/translations/Korean/undoing-a-commit.ko.md b/additional-material/translations/Korean/undoing-a-commit.ko.md new file mode 100644 index 00000000000..e7fedb0f72e --- /dev/null +++ b/additional-material/translations/Korean/undoing-a-commit.ko.md @@ -0,0 +1,59 @@ +## 로컬 커밋 되돌리기 + +로컬에서 커밋을 위해 스테이징 영역에 추가한 작업 내용을 되돌리기 위해서는 다음 명령을 실행합니다. +``` +git reset +``` + +위 명령어는 수정한 코드가 반영된 스테이징 영역을 가장 최근에 반영한 커밋상태로 되돌립니다. +하지만 여러분의 작업 디렉토리에 수정한 내용들은 변경되지 않습니다. 따라서 여러분이 수정한 소스를 다시 커밋할 수 있습니다. +만일 이미 스테이징 영역에 반영된 수정한 파일들 중에서 하나의 파일만 커밋에서 제거하기를 원할 경우, 아래 명령을 실행합니다. + +``` +git reset +``` +이 명령어는 스테이징 영역에서 해당 파일만 제거합니다. 그러나 작업 디렉토리에는 변경된 파일 상태 그대로 남아 있습니다. + +다음은 ```git reset``` 사용법에 관한 예제입니다. +``` +# 먼저 index.php 와 tutorial.php 파일을 수정합니다. +# 스테이징 영역에 파일을 추가합니다. +$ git add . +# 두 파일을 각각 커밋해야하므로 +# tutorial.php 파일을 스테이징 영역에서 제거합니다. +$ git reset tutorial.php +# index.php 파일을 먼저 커밋합니다. +$ git commit -m "Changed index.php" +# 다음으로 tutorial.php 파일을 커밋합니다. +$ git add tutorial.php +$ git commit -m "Changed tutorial.php" +``` + +로컬 저장소에 문제가 생겨 여러분의 코드를 마지막 커밋 상태로 모두 되돌리고 싶다면 아래 명령을 실행할 수 있습니다. +``` +git reset --hard +``` + +이 명령어는 스테이징 영역을 마지막 커밋 상태로 되돌리는 것 뿐만 아니라 여러분의 로컬에 변경된 파일도 되돌릴 수 있습니다. +```--hard``` 모드는 Git으로 하여금 작업 디렉토리에 대한 변경들도 되돌릴 수 있도록 합니다. +따라서 로컬에서 개발한 모든 개발 내용을 초기화해도 되는지 반드시 확인 후 실행하셔야 합니다. + +다음은 ```git reset --hard``` 사용에 관한 예제입니다. +``` +# 엉뚱한 실험을 시작하기로 결정했습니다. +# 먼저 'crazy.php' 파일을 만들고 코드를 추가합니다. +# 그리고 crazy.php 파일을 커밋합니다. +$ git add crazy.php +$ git commit -m "Started a crazy dev" +# crazy.php 파일을 다시 수정하고 기타 여러 파일들을 생성하고 수정합니다. +# 그리고 수정한 모든 파일을 스테이징 영역에 추가하고 커밋합니다. +$ git add . +$ git commit -m "Continued dev" +# 테스트하고 마칩니다. +# 실험하기 전 상태로 되돌리기 위해 모든 수정사항을 제거합니다. +$ git reset --hard HEAD~2 +``` +```git reset --hard HEAD~2``` 명령어는 현재 브랜치에서 여러분이 수정한 이전의 커밋들 중에 2번째 커밋 포인트 상태로 이동함과 동시에 해당 커밋들에 대한 변경사항들이 이전 상태로 복구됩니다. 그리고 프로젝트 히스토리에서 이전에 추가된 2개의 스냅샷이 제거됩니다. + +P.s. 만일 여러분의 공유 저장소로 이미 push를 완료한 상태에서 ```git reset --hard``` 명령을 실행할 경우, 해당 저장소를 사용하는 모든 사람들에게 문제를 일으킬 수 있으므로 절대 실행해서는 안됩니다. + diff --git a/additional-material/translations/Portuguese/additional-material.pt_br.md b/additional-material/translations/Portuguese/additional-material.pt_br.md new file mode 100644 index 00000000000..c93d6275114 --- /dev/null +++ b/additional-material/translations/Portuguese/additional-material.pt_br.md @@ -0,0 +1,46 @@ +# Informações Adicionais + +Nós imaginamos que você já tenha terminado o tutorial básico antes de vir aqui. As informações adicionais te darão algumas informações sobre técnicas mais avançadas de Git. + +### [Emendando um commit](../git_workflow_scenarios/amending-a-commit.md) +Esse documento provê informações sobre como emendar um commit no repositório remoto. +> Use isso quando você precisar ajustar um commit que você tenha feito. + +### [Configurando o git](../git_workflow_scenarios/configuring-git.md) +Esse documento provê informações sobre como configurar detalhes de usuário e outras opções do git. +> Use isso para melhor controlar as suas configurações do git. + +### [Mantendo o seu fork em sincronia com o repositório](../git_workflow_scenarios/keeping-your-fork-synced-with-this-repository.md) +Esse documento provê informações sobre como manter o seu fork atualizado com o repositório base. Isso é importante, já que se espera que você e muitas outras pessoas contribuem com o projeto. +> Siga esses passos se o seu fork não possui as mesmas alterações do repositório pai. + +### [Movendo um Commit para um Branch diferente](../git_workflow_scenarios/moving-a-commit-to-a-different-branch.md) +Esse documento provê informações sobre como mover um Commit para outro Branch. +> Siga esses passos para mover um commit para outro branch. + +### [Removendo um arquivo](../git_workflow_scenarios/removing-a-file.md) +Esse documento provê informações sobre como remover um arquivo do seu repositório local. +> Siga esses passos para aprender como remover um arquivo do seu repositório local. + +### [Removendo um Branch do seu repositório](../git_workflow_scenarios/removing-branch-from-your-repository.md) +Esse documento provê informações sobre como deletar um Branch do seu repositório. +> Apenas siga esses passos após o seu pull request ter sido mesclado. + +### [Resolvendo conflitos de Merge](../git_workflow_scenarios/resolving-merge-conflicts.md) +Esse documento provê informações sobre como resolver conflitos de Merge. +> Siga esses passos para resolver conflitos de Merge irritantes. + +### [Revertendo um commit](../git_workflow_scenarios/reverting-a-commit.md) +Esse documento provê informações sobre como reverter um commit feito no repositório remoto. Isso é muito útil quando você precisa desfazer um commit que tenha sido publicado no GitHub. +> Siga esses passos se você quiser reverter um commit. + +### [Comprimir Commits juntos](../git_workflow_scenarios/squashing-commits.md) +Esse documento provê informações sobre como esmagar commits juntos em um só realizando um rebase. +> Use esses passos se você quiser realizar um PR em um projeto open source e a pessoa que realizou o review pedir para você mesclar todos os commits em um só, com uma mensagem de commit informativa. + +### [Desfazendo um commit local](../git_workflow_scenarios/undoing-a-commit.md) +Esse documento provê informações sobre como desfazer um commit no seu repositório local. Isso é o que você precisa fazer quando você sente que fez alguma besteira no seu repositório e deseja desfazer. +> Take these steps if you want to undo/reset a local commit. + +### [Links úteis](../git_workflow_scenarios/Useful-links-for-further-learning.md) +Esse documento é dedicado a todos os blog posts, sites úteis, dicas e truques que fazem a nossa vida mais simples. Seja você um expert ou um iniciante, essa pagina deve servir como um index para todos esses links úteis para ajudar qualquer um que seja novo no mundo de projetos open-source ou alguém que queira prender mais a respeito. diff --git a/additional-material/translations/Portuguese/amending-a-commit.pt_br.md b/additional-material/translations/Portuguese/amending-a-commit.pt_br.md new file mode 100644 index 00000000000..1b6d92cdcf7 --- /dev/null +++ b/additional-material/translations/Portuguese/amending-a-commit.pt_br.md @@ -0,0 +1,52 @@ +# Corrigindo um Commit + +E se você fizer o commit de uma alteração para o seu repositório remoto, e posteriormente acabar percebendo que ele possui um erro na mensagem do commit, ou você se esqueceu de adicionar uma linha de código no seu commit mais recente? +Como você editaria isso? É isso que esse tutorial cobre. + +## Alterando uma mensagem de commit recente após ter dado push para o Github + +Para fazer isto sem abrir um arquivo: +* Digite o comando ```git commit --amend -m "seguido da sua nova mensagem de commit"``` +* Execute ```git push origin ``` para fazer o commit das mudanças para o repositório. + +Nota: Se você digitar apenas ```git commit --amend```, seu editor de texto abrirá te pedindo para editar a mensagem de commit. +Adicionar a flag ``-m`` previne isso. + +## Fazendo modificações em um único commit + +E se nós nos esquecermos de fazer uma pequena mudança em um arquivo, como adicionar uma única palavra, mas nós já demos push no commit para o nosso repositório remoto? + +Para ilustrar, aqui está um log dos meus commits: +``` +g56123f arquivo bot criado +a2235d atualizado contributor.md +a5da0d arquivo bot modificado +``` + +Supomos que eu esqueci de adicionar uma palavra no arquivo bot. + +Há 2 modos de resolver esse problema. O primeiro é fazer um novo commit que contém a mudança, dessa forma: + +``` +g56123f arquivo bot criado +a2235d atualizado contributor.md +a5da0d arquivo bot modificado +b0ca8f adicionada palavra no arquivo bot +``` + +O segundo modo é corrigir o commit a5da0d, adicionar essa nova palavra e dar push para o Github como um único commit. +Essa ação soa melhor, já que é apenas uma pequena alteração. + +Para fazer isso, nós faríamos o seguinte: +* Modificar o arquivo. Nesse caso, modificarei o arquivo bot para incluir a palavra que eu esqueci anteriormente. +* Em seguida, adicionar o arquivo para a área de preparação (*staging area*) com o comando ```git add ``` + +Normalmente, após adicionar arquivos na área de preparação, a próxima coisa que nós fazemos é entrar com o comando ```git commit -m "nossa mensagem de commit"```, certo? +Mas, como o que nós queremos fazer aqui é corrigir o commit anterior, nós ao invés disso iremos rodar: + +* ```git commit --amend``` + Isso irá inicializar o editor de texto para que possamos editar a mensagem. Você decide se irá deixar a mensagem como ela estava antes, ou editá-la. +* Sair do editor salvando as alterações +* Dar push nas suas alterações com o comando ```git push origin ``` + +Dessa forma, ambas as alterações agora estarão em um único commit. diff --git a/additional-material/translations/Portuguese/confinguring-git.pt-br.md b/additional-material/translations/Portuguese/confinguring-git.pt-br.md new file mode 100644 index 00000000000..bd00142ba73 --- /dev/null +++ b/additional-material/translations/Portuguese/confinguring-git.pt-br.md @@ -0,0 +1,73 @@ +#Configurando GIT + +A primeira vez que você tentar fazer um commit usando git, deve ter recebido uma como esta: + +```bash +$ git commit +*** Please tell me who you are. + +Rode: + +git config --global user.email "you@example.com" +git config --global user.name "Your Name" + +Para definir a identidade padrão da sua conta. +Omita “--global” para definir a identidade apenas nesse repositório + +o Git precisa saber quem você é ao criar um commit. Quando você está trabalhando colaborativamente, deve ser capaz de ver quem modificou quais partes do projeto e quando, e assim, o git foi projetado para criar commits vinculados a um nome e um email. + +Existem várias maneiras de fornecer o comando “git commit” com seu email e nome. Veremos algumas delas a seguir. + + +### Configuração global +Quando você armazena algo na configuração global, fica acessível em todos os sistemas e repositórios nos quais você trabalha. Essa é principal forma e funciona para a maioria dos casos de uso. + +Para armazenar algo na configuração use o comando “config” da seguinte maneira: + +$ git config --global + +No caso dos detalhes do usuário, nós os executamos da seguinte maneira: + +$ git config --global user.email "you@example.com" +$ git config --global user.name "Your Name" + +### Configuração do repositório + +Como o nome diz, essas configurações tem como alvo seu repositório atual. Se você quiser se comprometer com um repositório específico, por exemplo, um projeto relacionado a trabalho, com o email de sua empresa, então você pode usar esse método. + +Para armazenar algo na configuração do repositório, você usa o comando “config” omitindo a sinalização “--global”, da seguinte forma: + +$ git config + +No caso dos detalhes do usuário, nós o executamos da seguinte maneira: + +$ git config user.email "you@alternate.com" +$ git config user.name "Your Name" + +### Configuração da linha de comando + +Esse tipo de configuração tem como alvo apenas o comando atual. Todos os comandos git usam argumentos “-c” antes do verbo de ação para definir dados de configurações temporários + +Para armazenar algo na configuração da linha de comando. Execute seu comando da seguinte maneira: + +$ git -c = -c = + +No exemplo citado, executaríamos o comando commit da seguinte forma: + +git -c user.name='Your Name' -c user.email='you@example.com' commit -m "Your commit message" + +### Nota sobre precedência + +Entre os três metodos descritos aqui, a ordem de precedência é “linha de comando > repositório > global”. Isso significa que, se uma variável for configurada na linha de comando e também globalmente, o valor da linha de comando será usado para a operação. + +## Além dos detalhes do usuário: + +Nós lidamos apenas com os detalhes do usuário até agora, enquanto trabalhamos com a configuração. No entanto, existem várias outras opcões disponíveis. Algumas delas são: + +1. `core.editor` - para especificar o nome do editor usado para escrever mensagens de commit etc +2. `commit.template` - para especificar um arquivo no sistema como o modelo de commit inicial +3. `color.ui` - para especificar um valor booleano para usar cores na saída do git + +Nós abstraimos alguns detalhes para facilitar o entendimento. Para ler mais, acesse: + +[git-scm.com](https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration). \ No newline at end of file diff --git a/additional-material/translations/Portuguese/keeping-your-fork-synced-with-this-repository.pt_br.md b/additional-material/translations/Portuguese/keeping-your-fork-synced-with-this-repository.pt_br.md new file mode 100644 index 00000000000..474a7f44165 --- /dev/null +++ b/additional-material/translations/Portuguese/keeping-your-fork-synced-with-this-repository.pt_br.md @@ -0,0 +1,40 @@ +## Mantendo o seu Fork sincronizado com este repositório + +Primeiro, o fluxo para uma sincronização completa precisa ser entendido. Nesse cenário, temos 3 repositórios diferentes: o meu repositório público no Github `github.com/Roshanjossey/first-contributions/`, seu Fork no GitHub `github.com/Seu-Nome/first-contributions/` e o repositório local, no qual você deve trabalhar. Esse tipo de cooperação é típica de projetos de *open source* (código aberto) e é chamado de `Triangle Workflows`. + +triangle workflow + +Para manter seus dois repositórios atualizados com meu repositório público, o primeiro passo é dar um Fetch (buscar) e então um Merge (mesclar) do repositório público ao seu repositório local. +O segundo passo é fazer um Push do repositório local para o seu Fork no GitHub. Como vimos anteriormente, é somente a partir do seu Fork que você consegue fazer um Pull Request. Por isso, esse Fork é o último repositório a ser atualizado. + +Agora, vamos ver como fazer isso: + +Primeiro, você precisa estar em seu Branch principal (master). Para saber em qual Branch você está, verifique a primeira linha que aparece como resultado do seguinte comando: +``` +git status +``` +Se você não está no master, vá para ele: +``` +git checkout master +``` + +Em seguida, você deve adicionar meu repositório público ao seu git com `add upstream url-remoto`: +``` +git remote add upstream https://github.com/Roshanjossey/first-contributions +``` +Esta é uma forma de dizer ao Git que existe uma outra versão deste projeto na URL especificada e estamos chamando-a de `upstream`. Agora busque a nova versão do meu repositório: +``` +git fetch upstream +``` + +Aqui você está buscando todas as mudanças no meu Fork (o remoto `upstream`). Agora, você precisa mesclá-lo ao repositório público no seu Branch principal. +``` +git rebase upstream/master +``` +Aqui você está aplicando todas as mudanças que buscou ao seu Branch principal (master). Seu repositório local agora está atualizado. Por último, se você fizer um Push do seu Branch master para o seu Fork, seu GitHub também terá as alterações: +``` +git push origin master +``` +Note que aqui você está fazendo um Push para o repositório remoto chamado `origin`. + +Agora, todos os seus repositórios estão atualizados. Bom trabalho! Você deve seguir esses passos sempre que seu repositório no GitHub avisar que está alguns Commits atrás do meu repositório. diff --git a/additional-material/translations/Portuguese/moving-a-commit-to-a-different-branch.pt_br.md b/additional-material/translations/Portuguese/moving-a-commit-to-a-different-branch.pt_br.md new file mode 100644 index 00000000000..b96ae5a815a --- /dev/null +++ b/additional-material/translations/Portuguese/moving-a-commit-to-a-different-branch.pt_br.md @@ -0,0 +1,25 @@ +# Movendo um commit para outra branch +E se apenas depois de ter realizado o commit de uma alteração, vocẽ perceber que fez esse commit na branch errada? +Como você poderia corrigir isso? É sobre isso que este tutorial se trata. + +## Movendo os últimos commits para uma branch existente +Para fazer isso, digite: + + +```git reset HEAD~ --soft``` - Desfaz o último commit, mas mantém as alterações disponíveis. +```git stash``` - Grava o estado do diretório. + +```git checkout name-of-the-correct-branch``` - Alterna para a outra branch. +```git stash pop``` - Recupera o último estado salvo. +```git add .``` - Ou tente adicionar arquivos individualmente. +```git commit -m "your message here"``` - Faça o commit das alterações. + +Agora suas alterações estão na branch correta + +### Movendo o último commit para uma branch nova +Para fazer isso, digite: +```git branch newbranch``` - Cria uma nova branch, mantendo todos os commits. +```git reset --hard HEAD~#``` - Retrocede a branch uma quantidade # de commits. Atenção, estes commits serão removidos da branch. +```git checkout newbranch``` - Vá para a nova branch que você criou, ela possuíra todos os commits. + +Lembre-se: Qualquer alteração não comitada será PERDIDA. diff --git a/additional-material/translations/Portuguese/removing-a-file.pt_br.md b/additional-material/translations/Portuguese/removing-a-file.pt_br.md new file mode 100644 index 00000000000..237c7698a3e --- /dev/null +++ b/additional-material/translations/Portuguese/removing-a-file.pt_br.md @@ -0,0 +1,24 @@ +# Removendo um arquivo do Git + +Às vezes, você pode querer remover um arquivo do Git, mas não excluí-lo do seu computador. Você pode fazer isso usando o seguinte comando: + +``git rm --cached`` + +## Então o que aconteceu? + +O Git não irá mais controlar as mudanças no arquivo removido. Pelo que Git sabe, é como se você tivesse excluído o arquivo. Se você localizar o arquivo em seu sistema de arquivos, notará que ele ainda está lá. + +Observe que no exemplo acima, o sinalizador `--cached` é utilizado. Se não adicionarmos esse sinalizador, o Git removerá o arquivo não apenas do repositório, mas também do seu sistema de arquivos. + +Se você confirmar a mudança com `git commit -m" Remove file1.js "` e enviar para o repositório remoto usando `git push origin master`, o repositório remoto removerá o arquivo. + + +## Características adicionais + +- Se você deseja remover mais de um arquivo, pode incluí-los todos no mesmo comando: + + `git rm file1.js file2.js file3.js --cached` + +- Você pode utilizar o caractere coringa (*) para remover todos os arquivos semelhantes. Por exemplo se você deseja remover todos os .txt do seu repositório local: + + `git rm *.txt --cached` diff --git a/additional-material/translations/Portuguese/removing-branch-from-your-repository.pt_br.md b/additional-material/translations/Portuguese/removing-branch-from-your-repository.pt_br.md new file mode 100644 index 00000000000..663e75d1fb9 --- /dev/null +++ b/additional-material/translations/Portuguese/removing-branch-from-your-repository.pt_br.md @@ -0,0 +1,31 @@ +## Removendo o Branch do seu repositório + +Se você seguiu o tutorial até agora, seu Branch `` concluiu seu objetivo, e é hora de deletá-lo do seu repositório local. Isso não é necessário, mas o próprio nome desse Branch mostra como seu objetivo é específico. Sua vida pode ser tornada curta por causa dessa especificidade. + +Primeiro, vamos mesclar o Branch `` ao seu Branch principal (master), então vamos para ela: +``` +git checkout master +``` + +Mescle `` ao master: +``` +git merge master +``` + +Remova `` do seu repositório local: +``` +git branch -d +``` + +Agora você deletou seu Branch local `` e tudo está limpo e arrumado. +Nesse ponto, você ainda deve ter o Branch `` no seu Fork. Antes de deletá-lo, lembre-se que você mandou um Pull Request para o meu repositório a partir desse Branch remoto. Então, a não ser que eu já tenha mesclado o Branch, não o delete. + +Porém, se eu já tiver mesclado seu Branch e você quer deletar o Branch remoto, use: +``` +git push origin --delete +``` + +Agora, você sabe como arrumar seus Branches. +Com o tempo, muitos Commits serão adicionados ao meu repositório público. E os Branches principais (master) da sua máquina local e do seu Fork não estarão mais atualizados. Então, para manter seus repositórios sincronizados com o meu, siga os passos abaixo. + +#### [Mantendo o seu Fork sincronizado com este repositório](keeping-your-fork-synced-with-this-repository.pt_br.md) diff --git a/additional-material/translations/Russian/additional-material.ru.md b/additional-material/translations/Russian/additional-material.ru.md new file mode 100644 index 00000000000..522cd41ed28 --- /dev/null +++ b/additional-material/translations/Russian/additional-material.ru.md @@ -0,0 +1,46 @@ +# Дополнительная информация + +Здесь мы предполагаем, что вы уже освоили основную инструкцию. Дополнительная информация содержит некоторые сведения о GIT командах, необходимыж в более сложных ситуациях. + +### [Исправления в коммите](amending-a-commit.md) +Документ содержит информацию о том, как внести исправления в коммит в удаленном репозитории. +> Она необходима для тех случаев, когда вы хотите изменить коммит, который вы сделали ранее. + +### [Конфигурирование GITа](configuring-git.md) +Документ содержит сведния о том, как изменить информацию о пользователе и другие настройки GITа. +> Он будет полезен, если вы захотите сделать установки GITа более удобными. + +### [Синхронизация вашего ответвления с основным репозиторием](keeping-your-fork-synced-with-this-repository.md) +Документ рассказывает о том, как обеспечить синхронизацию вашего ответвления с основным репозиторием. Обеспечение синхронизации небходимо, так как, насколько можно надеяться, вы будете работать над проектом не в одиночестве, а вносить изменения в него, наряду с другими участниками. +> Выполните эти действия, если ваше ответвление не имеет изменений в master ветке репозитория. + +### [Перемещение коммита в другую ветку](moving-a-commit-to-a-different-branch.md) +Документ содержит сведения о том, как переместить коммит в другую ветку. +> Выполните указанные шаги, чтобы переместить коммит в другую ветку. + +### [Удаление файла](removing-a-file.md) +Документ описывает как удалить файл из вашего локального репозитория. +> Ознакомьтесь с этими командами чтобы понять как удалить файл перед тем, как сделать коммит. + +### [Удаление ветки из вашего репозитория](removing-branch-from-your-repository.md) +Документ содержит информацию о том, как удалить ветку из вашего репозитория. +> Используйте эти команды только после того, как ваш пул-реквест был удовлетворен. + +### [Разрешение конфликтов при слиянии веток](resolving-merge-conflicts.md) +Документ содержит информацию о том, как разрешать конфликты, возникающие при слиянии веток. +> Предложенные здесь шаги помогут вам разобраться с весьма неприятными случаями конфликтов возникающих при слиянии веток. + +### [Отмена коммита](reverting-a-commit.md) +Документ инструктирует как отменить коммит в удаленном репозитории. Такая операция будет полезна в тех случаях, когда вам необходимо отыграть назад тот коммит, который уже был послан на Github (pushed). +> Выполните указанные здесь шаги чтобы отменить коммит. + +### [Совмещение коммитов (squashing)](squashing-commits.md) +Документ описывает, как совмещать коммиты при помощи интерактивного перебазирования. +> Используйте эти инструкции, если вы создали пул-реквест в open source проекте, но эксперт проекта просит вас совместить все ваши коммиты в один коммит с содержательным комментарием. + +### [Отмена локального коммита](undoing-a-commit.md) +Документ информирует, как отыграть назад коммит в вашем локальном репозитории. Вам понадобится эта информация в том случае, если вы решите, что вы испортили ваш репозиторий и захотите вернуть его содержимое к первоначальному состоянию. +> Следуйте этим инструкциям, если вы хотите отменить те изменения, котрые были сделаны последним локальным коммитом. + +### [Полезные ссылки](Useful-links-for-further-learning.md) +Этот файл содержит ссылки на блог-посты, полезные веб-сайты, веб-сайты с перечислением рекоммендаций и приемов, которые часто облегчают нашу жизнь. Как начинающим, так и экспертам мы рекомендуем обращаться к ним по мере необходимости. Этот файл содержит список полезных линьков, которые наверняка помогут и тем, кто делает первые шаги в open source, и тем, кто захочет рассширить свои знания в этой области. \ No newline at end of file diff --git a/additional-material/translations/Russian/amending-a-commit.ru.md b/additional-material/translations/Russian/amending-a-commit.ru.md new file mode 100644 index 00000000000..e1416073957 --- /dev/null +++ b/additional-material/translations/Russian/amending-a-commit.ru.md @@ -0,0 +1,45 @@ +# Исправления в коммите + +Представьте, что вы сделали коммит в удаленный репозиторий, а потом поняли, что допустили опечатку в комментарии к коммиту или забыли вставить строку в этот последний по времени коммит. Как поступить в такой ситуации? Именно об этом и пойдет речь в этом документе. + +## Как изменить комментарий к недавнему коммиту после того, как он был послан на Github (pushed) +Чтобы сделать это, не открывая файл для редактирования, +* наберите ```git commit --amend -m "здесь следует текст нового комментария"``` +* а затем исполните ```git push origin <имя-ветки>``` для того, чтобы послать изменения на Github. + +Примечание: Если вы наберете, только ```git commit --amend```, то откроется текстовый редактор и предложит отредактировать комментарий к коммиту. Использование ключа ``-m`` отменяет запуск редактора. + +## Как сделать изменения в одном коммите + +Что если мы забыли сделать небольшое изменение в файле, например, заменить одно слово в коммите, который уже послан в удаленный репозиторий? + +Пусть, для примера, записи в журнале моих коммитов выглядят следующим образом: +``` +g56123f создай файл bot file +a2235d исправлен contributor.md +a5da0d изменен bot file +``` +Допустим, я забыл добавить одно слово в файл bot file + +Есть два способа исправить это. Первый заключается в создании нового коммита, содержащего это изменение, например, так: +``` +g56123f создай файл bot file +a2235d исправлен contributor.md +a5da0d изменен botfile +b0ca8f добавлено одно слово в botfile +``` +Второй способ состоит в исправлении коммита a5da0d, добавлении этого пропущенного слова и запушивании этих изменений на Github в виде одного коммита. +Второй способ представляется предпочтительным, поскольку дело идёт лишь о незначительном изменении. + +Чтобы добиться этого, мы поступим следующим образом: +* Изменим файл. В данном случае я изменю файл botfile, добавив к нему слово, которое я пропустил ранее. +* Далее, проиндексируем этот файл при помощи команды ```git add <имяфайла>``` + +В обычном случае сразу после индексирования мы делаем ```git commit -m "комментраий к нашему коммиту"```, правильно? Но поскольку в данном случае наша задача - исправить предыдущий коммит, - то вместо этого мы выполним такую команду: + +* ```git commit --amend``` + В результате откроется окно текстового редактора, в котором мы имеем возможность сделать изменения в комментарии. Мы можем в самом деле отредактировать комментарий, или оставить его без изменений. +* Выйдем из редактора +* Запушим наши изменения при помощи команды ```git push origin <имя-ветки>``` + +Таким образом, оба исправления окажутся в одном коммите. diff --git a/additional-material/translations/Russian/configuring-git.ru.md b/additional-material/translations/Russian/configuring-git.ru.md new file mode 100644 index 00000000000..769f4fc803f --- /dev/null +++ b/additional-material/translations/Russian/configuring-git.ru.md @@ -0,0 +1,76 @@ +# Конфигурирование GITа + +Когда вы впервые попытались сделать коммит, вы могли увидеть такое сообщение: + +```bash +$ git commit +*** Please tell me who you are. [Пожалуйста, сообщите, кто вы.] + +Исполните следующие команды: + +git config --global user.email "you@example.com" +git config --global user.name "Your Name" + +чтобы идентифицировать пользователя по умолчанию для данной учетной записи. +Опустите ключ --global если вы хотите указать пользователя только для данного репозитория. +``` + +Чтобы создать коммит, GIT должен знать кто является его автором. При совместной работе, необходимо знать кем и когда были изменены те или иные части проекта, поэтому GIT предусматривает, что каждый коммит при его создании ассоциируется с именем и емейл адресом пользователя. + +Существует несколько способов, которые позволяют ассоциировать команду `git commit` с вашим емейлом и именем, и здесь мы перечислим некоторые из них. + +### Глобальная конфигурация + +Информация, сохраненная как часть глобальной конфигурации, относится ко всей системе, т.е. ко всем репозиториям, в которых вы работаете. Это предпочтительный способ, подходящий для большинства из вариантов использования. + +Для сохранения данных в глобальной конфигурации пользуйтесь коммандой `config` в следующей форме: + +`$ git config --global <название переменной> <значение переменной>` + +В применении к информации о пользователе, мы исполняем эти команды таким образом: + +``` +$ git config --global user.email "you@example.com" +$ git config --global user.name "Your Name" +``` + +### Конфигурация репозитория + +Как указывает заголовок, такая конфигурация работает в пределах данного репозитория. Если вы хотите сделать коммит в определенном репозитории, скажем содержащем проект связанный с вашим бизнесом, используя емейл вашей компании, тогда вы можете использовать этот способ конфигурации. + +Чтобы изменить конфигурацию на уровне репозитория, следует опустить ключ `--global` в команде `config` таким образом: + +`$ git config <название переменной> <значение переменной>` + +В применении к информации о пользователе, это выглядит следующим образом: + +``` +$ git config user.email "you@alternate.com" +$ git config user.name "Your Name" +``` + +### Конфигурация в командной строке + +Этот способ конфигурации относится только к данной команде. Все команды GIT'а позволяют использовать ключ `-c` перед глаголом идентифицирующим команду для временной установки конфигурационных параметеров. + +Для изменения параметров конфигурации, распространяющихся только на данную команду, пользуйтесь следующим форматом команд GIT'a: + +`$ git -c <переменная-1>=<значение переменной-1> -c <переменная-2>=<значение переменной-2> <команда>` + +Для нашего случая комманда для коммита будет вылядеть так: + +`git -c user.name='Your Name' -c user.email='you@example.com' commit -m "Ваш комментарий к коммиту"` + +### Замечание о порядке предшествования + +Порядок предшествования среди трех упомянутых типов команд конфигурации определяется как `конфигурация в командной строке > конфигурация репозитория > глобальная конфигурация`. Это означает, что если какая-либо переменная определена, как в глобальной конфигурации, так и в командной строке, то будет использовано значение, присвоенное в командной строке. + +## Не только информация о пользователе + +До сих пор, обсуждая конфигурацию GIT'а, мы касались лишь информации о пользователе. Однако GIT позволяет конфигурировать еще неслколько параметров. Вот некторые из них: + +1. `core.editor` - указывает название редактора для редактирования комментарий для коммита и т.п., +2. `commit.template` - указывает файл, который содержит первоначальный темплат для коммита, +3. `color.ui` - логическая переменная, указывающая следует ли испольовать цветные шрифты в сообщениях на терминале GIT'а. + +Для простоты мы опустили некоторые детали. Для более подробного ознакомления обратитесь к [git-scm.com](https://git-scm.com/book/ru/v1/Введение-Первоначальная-настройка-Git). \ No newline at end of file diff --git a/additional-material/translations/Russian/moving-a-commit-to-a-different-branch.ru.md b/additional-material/translations/Russian/moving-a-commit-to-a-different-branch.ru.md new file mode 100644 index 00000000000..dbf8c5a2ba5 --- /dev/null +++ b/additional-material/translations/Russian/moving-a-commit-to-a-different-branch.ru.md @@ -0,0 +1,25 @@ +# Перемещение коммита в другую ветку +Что если вы сделали коммит, а затем поняли, что изменили неправильную ветку? +Как исправить такую ошибку? На этот вопрос отвечает данная инструкция. + +## Перемещение последних коммитов в существующую ветку +Для такого перемещения, наберите: + +```git reset HEAD~ --soft``` - Отменяет последний коммит, но сохраняет сделанныые изменения. +```git stash``` - Сохраняет состояние директории. + +```git checkout <имя правильной ветки>``` - Переключается на другую ветку. +```git stash pop``` - Возвращает последнее сохраненное состояние. +```git add .``` - Добавляет индивидуальные файлы. +```git commit -m "ваш комментарий"``` - Сохраняет и делает коммит изменений. + +Теперь ваши изменения - в правильной ветке. + + +### Перемещение последних коммитов в новую ветку +Для такого перемещения, наберите: +```git branch newbranch``` - Создает новую ветку, сохраняя все коммиты. +```git reset --hard HEAD~[n]``` - Возвращает ветку master назад на n коммитов. Имейте в виду, что изменения содержащиеся в этих коммитах будут полностью удалены из ветки master. +```git checkout newbranch``` - Переключается на ветку, которую вы создали. Эта ветка теперь содержит все коммиты. + +Запомните: Любые изменения, которые не были включены в коммит, будут полностью ПОТЕРЯНЫ. diff --git a/additional-material/translations/Russian/removing-a-file.ru.md b/additional-material/translations/Russian/removing-a-file.ru.md new file mode 100644 index 00000000000..eabe0f1c1be --- /dev/null +++ b/additional-material/translations/Russian/removing-a-file.ru.md @@ -0,0 +1,23 @@ +# Удаление файла из-под GIT контроля + +Иногда может возникнуть необходимость удалить файл из-под GIT контроля, но сохранить его на компьютере. Это может быть достигнуто с помощью следующей команды: + +``git rm <файл> --cached`` + +## Что же произошло? + +GIT более не контролирует изменения в удалённом файле. С точки зрения GIT'а, этот файл отсутствует, но если вы попробуете локализовать этот файл в файловой системе, то вы увидите, что он всё еще на месте. + +Заметьте, что в приведенной выше комманде используется ключ `--cached`. Если бы мы не добавили этот ключ, GIT уничтожил бы файл не только из репозитория, но также и из файловой системы. + +Если вы сделаете коммит при помощи команды `git commit -m "Удалить file1.js"` и затем запушите его в удалённый репозиторий командой `git push origin master`, файл будет стёрт также и из удалёного репозитория. + +## Дополнительная информация + +- Если вы хотите удалить более одного файла, это можно сделать, перечислив все файлы в одной команде: + + `git rm file1.js file2.js file3.js --cached` + +- Вы можете использовать шаблон (*) для удаления файлов с близкими именами, например, если вы хотите удалить все .txt файлы из локального репозитория, наберите: + + `git rm *.txt --cached` diff --git a/additional-material/translations/Slovenian/additional-material.sl.md b/additional-material/translations/Slovenian/additional-material.sl.md new file mode 100644 index 00000000000..57c1271e45b --- /dev/null +++ b/additional-material/translations/Slovenian/additional-material.sl.md @@ -0,0 +1,46 @@ +# Dodatne informacije + +Predvidevamo da ste že končali osnovni vodič. Sedaj boste dobili dodatne informacije o napredni uporabi Git-a. + +### [Popravljanje commita](amending-a-commit.sl.md) +Informacije o tem kako spremeniti commit v oddaljenem repositoryu. +> Uporabi, ko moraš spremeniti že narejeni commit. + +### [Nastavljanje Git-a](configuring-git.sl.md) +Informacije o tem kako nastaviti uporabnika in druge možnosti v Git-u. +> Uporabi za boljši nadzor nad svojo Git konfiguracijo. + +### [Kako imeti svojo različico sinhronizirano z oddaljenim repository-em](keeping-your-fork-synced-with-this-repository.sl.md) +Informacije o tem kako obdržati svojo različico v skladu z glavnim repository-em. To je pomembno, ker lahko veliko ljudi prispeva k projektu. +> Sledi tem korakom, če tvoja verzija nima nobenih sprememb v nadrejenem imeniku (parent directory). + +### [Premikanje commita v drugo vejo](moving-a-commit-to-a-different-branch.sl.md) +Informacije o tem kako premakniti commit v drugo vejo. +> Sledi tem korakom in premakni commit v drugo vejo. + +### [Odstranjevanje datoteke](removing-a-file.sl.md) +Informacije o tem kako odstraniti datoteko z svojega lokalnega repository-ja. +> Sledi tem korakom in odstrani datoteko pred commitom. + +### [Odstrani vejo s svojega repository-ja](removing-branch-from-your-repository.sl.md) +Informacije o tem kako zbrisati vejo s svojega repository-ja. +> Sledi tem korakom šele potem, ko je bil tvoj pull-request že združen. + +### [Razreševanje sporov pri združevanju](resolving-merge-conflicts.sl.md) +Informacije o tem kako razrešiti spore pri združevanju (resolve merge conflicts). +> Sledi tem korakom pri razreševanju nadležnih sporov pri združevanju. + +### [Povrnitev commita](reverting-a-commit.sl.md) +Informacije o tem kako povrniti commit na oddaljenem repository-ju v prejšnje stanje. Zelo uporabno, če moraš razveljaviti commit, ki je bil že poslan na GitHub. +> sledi tem korakom, če želiš povrniti commit v prejšnje stanje. + +### [Stiskanje commit-ov](squashing-commits.sl.md) +Informacije o tem kako stisnite commite z interaktivnim rebase-om. +> Uporabi te korake, če želiš narediti pull-request v odprto-kodni projekt in te pregledovalec prosi, da stisni (squash) vse commite v enega in dodaj informativno commit sporočilo. + +### [Razveljavljanje lokalnega commita](undoing-a-commit.sl.md) +Informacije o tem kako razveljaviti commit v svojem localnem repository-ju. Uporabno, ko si naredil zmešnjavo v lokalnem repository-ju in ga želiš postaviti na prejšnje stanje. +> Sledi korakom, ko želiš razveljaviti lokalni commit. + +### [Uporabne povezave](../git_workflow_scenarios/Useful-links-for-further-learning.md) +Ta dokument je namenjem vsem blogom, uporabnim stranem, spletnim stranem s triki in namigi, ki naredijo naša življenja lažja. Stran naj bi bila kazalo teh uporabnih povezav, ki lahko pomagajo vsem novincem v odprto-kodnem svetu in vsem, ki imajo željo po dodatnem znanju. diff --git a/additional-material/translations/Slovenian/amending-a-commit.sl.md b/additional-material/translations/Slovenian/amending-a-commit.sl.md new file mode 100644 index 00000000000..1881495c6de --- /dev/null +++ b/additional-material/translations/Slovenian/amending-a-commit.sl.md @@ -0,0 +1,48 @@ +# Popravljanje Commita + +Kaj narediti, če pošlješ commit v oddaljeni repository in potem ugotoviš da si se zatipkal ali pa pozabil dodati vrstico kode v svoj zadnji commit. +Kako to popraviti? O tem govori ta vodič. + +## Spreminjanje komentarja commit-a, ki je bil pred kratkim poslan na GitHub +To lahko naredimo brez da bi odprli datoteko: +* V terminal vpiši ```git commit --amend -m "followed by your new commit message"``` +* Zaženi ```git push origin ``` da pošlješ commit s spremembo v repository. + +Opomba: Če vtipkaš samo ```git commit --amend```, se odpre tvoj urejevalnik besedil in te pozove da spremeniš komentar commit-a. +Zastavica ``-m`` to prepreči. + +## Sprememba enega commit-a + +No, kaj storiti, če pozabimo narediti eno malo spremembo v datoteki, kot na primer spremeniti eno besedo, vendar smo že poslali commit v oddaljeni repository? + +Prikaz praktičnega primera (zgodovina commit-ov tega repository-a): +``` +g56123f create file botfile +a2235d updated contributor.md +a5da0d modified botfile +``` +Recimo da smo pozabili dodati eno samo besedo datoteki botfile. + +Obstajata dva načina kako se stvari lotiti. Prvi primer je da naredimo nov commit, ki vsebuje spremembo: +``` +g56123f create file botfile +a2235d updated contributor.md +a5da0d modified botfile +b0ca8f added single word to botfile +``` +Drugi način je, da spremenimo commit a5da0d, mu dodamo pozabljeno besedo in ga pošljemo v GitHub, vse skupaj kot en commit. +Drugi način nam je bolj všeč, ker imamo opravka z manjšo spremembo. + +Da to dosežemo, storimo naslednje: +* Spremenimo datoteko. V tem primeru bomo spremenili datoteko botfile in ji dodali spuščeno besedo. +* Nato bomo dodali datoteko v čakalnico z ```git add ```. + +Običajno ko dodamo datoteke v čakalnico, je naslednji korak, da naredimo commit s komentarjem ( git commit -m "our commit message" ). +V tem primeru pa želimo popraviti že narejen commit, zato namesto tega izvedemo: + +* ```git commit --amend``` + Ukaz nam v tem primeru prikaže urejevalnik besedila in nam omogoči da spremenimo komentar. Sami se odločimo, ali spremenimo komentar, ali pustimo prejšnjega. +* Zapustimo urejevalnik besedil. +* Pošljemo spremembe z `` `git push origin ` ``. + +Na ta način bosta obe spremembi združeni v enem commit-u. diff --git a/additional-material/translations/Slovenian/configuring-git.sl.md b/additional-material/translations/Slovenian/configuring-git.sl.md new file mode 100644 index 00000000000..591bb4c9493 --- /dev/null +++ b/additional-material/translations/Slovenian/configuring-git.sl.md @@ -0,0 +1,77 @@ +# Nastavljanje Git okolja + +Ko si prvič poskusil narediti commit z Git-om, je možno da se je prikazalo naslednje sporočilo: + +```bash +$ git commit +*** Please tell me who you are. + +Run + +git config --global user.email "you@example.com" +git config --global user.name "Your Name" + +to set your account's default identity. +Omit --global to set the identity only in this repository. +``` + +Git mora vedeti kdo si, da lahko ustvari commit. Ko delaš v skupini z več ljudmi, naj bi se vedno vedelo kdo je naredil katero spremembo v projektu in kdaj jo je nardil. V ta namen je bil Git ustvarjen tako, da so commit-i vezani na ime in e-pošto. + +Obstaja več načinov kako ukazu `git commit` podati svoje ime in e-pošto in nekaj jih bomo pregledali v naslednjih vrsticah. + +### Globalna konfiguracija + +Ko nekaj shranimo v globalno konfiguracijo (global config), je ta nastavitev dosegljiva vsem repository-em na katerih delaš. Ta način se priporoča in deluje v večini primerov. + +Da nekaj shranimo v globalno konfiguracijo, uporabimo ukaz `config`: + +`$ git config --global ` + +V primeru uporabniških podatkov: + +``` +$ git config --global user.email "you@example.com" +$ git config --global user.name "Your Name" +``` + +### Konfiguracija repository-ja + +Kot nam že samo ime pove, so te konfiguracije omejene samo na en repository. Če želiš narediti commit v točno določen repository, recimo službeni projekt, s svojo službeno e-pošto, potem uporabimo to metodo. + +Da nekaj shranimo v konfiguracijo repository-ja, uporabimo ukaz `config` in spustimo zastavico `--global`: + + +`$ git config ` + +V primeru uporabniških podatkov: + +``` +$ git config user.email "you@alternate.com" +$ git config user.name "Your Name" +``` + +### Konfiguracija ukazne vrstice + +Te konfiguracije so omejene samo na trenutno ukazno vrstico. Vsi Git ukazi sprejmejo predpono `-c` pred glagolom ukaza. S tem ustvarimo začasno konfiguracijo. + +Da nekaj shranimo v konfiguracijo ukazne vrstice: + +`$ git -c = -c = ` + +V našem primeru bi ukaz commit uporabili takole: + +`git -c user.name='Your Name' -c user.email='you@example.com' commit -m "Your commit message"` + +### O prednosti + +Zaporedje uporabe med zgoraj omenjenimi metodami je sledeče `command-line > repository > global`. To pomeni da, če je spremenljivka shranjena v ukazni vrstici in globalno, bi bila uporabljena vrednost v konfiguraciji ukazne vrstice. + +## Dodatno + +Do sedaj smo delali samo z nastavitvami uporabnika, vendar obstaja še nekaj drugih konfiguracij. Nekatere med njimi so: + +1. `core.editor` - za določitev urejevalnika besedila, ki se uporabi za pisanje komentarjev, itd. +2. `commit.template` - za določitev datoteke v sistemu, ki se uporabi kot začetna predloga za commit +3. `color.ui` - za določitev boolean vrednosti za uporabo barv v Git-ovem izpisu. + +Nekaj podrobnosti smo poenostavili za lažje razumevanje. Več si lahko prebereš na [git-scm.com](https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration). diff --git a/additional-material/translations/Slovenian/keeping-your-fork-synced-with-this-repository.sl.md b/additional-material/translations/Slovenian/keeping-your-fork-synced-with-this-repository.sl.md new file mode 100644 index 00000000000..7422557b822 --- /dev/null +++ b/additional-material/translations/Slovenian/keeping-your-fork-synced-with-this-repository.sl.md @@ -0,0 +1,40 @@ +# Kako imeti svojo različico sinhronizirano z oddaljenim repository-em + +Najprej moramo razumeti kako poteka sinhronizacija. V tej shemi so trije različni repository-ji: moj javni repository na GitHub-u `github.com/Roshanjossey/first-contributions/`, tvoja različica tega repository-ja na GitHub-u `github.com/Your-Name/first-contributions/` in lokalni repository na tvojem računalniku. Ta način delovanja je značilen za odprto-kodne projekte in se imenuje `Triangle Workflow`. + +triangle workflow + +Da obdržimo tvoja dva repository-ja sinhronizirana z mojim javnim repository-jem, moramo najprej pridobiti javni repository in ga združiti s tvojim lokalnim repository-jem ( fetch and merge ). +Naslednji korak bo, da pošljemo tvoj lokalni repository v tvojo GitHub različico. Kot smo že prej videli, lahko samo iz GitHub različice zahtevamo "pull request". Zato je tvoja GitHub različica zadnji repository, ki se ga posodobi na zadnjo verzijo. + +No pa poglejmo kako se to naredi: + +Najprej moraš biti v svoji glavni veji ( master branch ). Da izveš na kateri veji si trenutno, izvedi ta ukaz in poglej prvo vrstico odgovora: +``` +git status +``` +Če nisi na glavni veji uporabi: +``` +git checkout master +``` + +Potem dodaš moj javni repository svojemu git-u z ukazom `add upstream remote-url`: +``` +git remote add upstream https://github.com/Roshanjossey/first-contributions +``` +Na ta način povemo git-u da obstaja še ena verzija tega projekta na podanem naslovu in da jo imenujemo `upstream`. Sedaj, ko ima tvoj git ime in naslov, lahko s tega naslova pridobimo zadnjo verzijo javnega repository-ja z ukazom `fetch`: +``` +git fetch upstream +``` + +Pravkar ste pridobili zadnjo verzijo moje različice (`upstream` remote). Sedaj pa je potrebno še združiti javni repository v tvojo glavno vejo (master branch). +``` +git rebase upstream/master +``` +Tukaj združuješ javni repository s svojo glavno vejo. Glavna veja na tvojem računalniku je sedaj posodobljena. Na koncu pošlješ še svojo glavno vejo v tvojo različico (fork) na GitHub-u in tudi ta bo posodobljena z zadnjimi spremembami: +``` +git push origin master +``` +Tukaj lahko vidiš da pošiljaš v oddaljeni repository imenovan `origin`. + +Na tej točki, so vsi tvoji repository-ji posodobljeni. Dobro opravljeno! To stori vsakič, ko te tvoj GitHub repository opozori, da ni sinhroniziran z ostalimi repository-ji. diff --git a/additional-material/translations/Slovenian/moving-a-commit-to-a-different-branch.sl.md b/additional-material/translations/Slovenian/moving-a-commit-to-a-different-branch.sl.md new file mode 100644 index 00000000000..3074388ec80 --- /dev/null +++ b/additional-material/translations/Slovenian/moving-a-commit-to-a-different-branch.sl.md @@ -0,0 +1,24 @@ +# Premikanje commita v drugo vejo +Kaj storiti, če izvedeš commit svojih sprememb, in potem ugotoviš da si izvedel commit v napačni veji? Kako lahko to spremenimo? To je razloženo v tem vodiču. + +## Premikanje zadnjega commita v obstoječo vejo +To storiš z naslednjimi ukazi: + +```git reset HEAD~ --soft``` - Razveljavi zadnji commit, spremembe ostanejo na voljo. +```git stash``` - Posname stanje direktorija in ga shrani v `stash`. + +```git checkout name-of-the-correct-branch``` - Prestavi v drugo vejo. +```git stash pop``` - Vzame zadno shranjeno stanje iz `stash-a`. +```git add .``` - Ali dodaš posamezne datoteke. +```git commit -m "your message here"``` - Shrani in izvede commit sprememb. + +Sedaj so tvoje spremembe na pravi veji. + + +### Premikanje zadnjih nekaj commitov v novo vejo +To storiš z naslednjimi ukazi: +```git branch newbranch``` - Ustvariš novo vejo. Nova veja ima vse prej ustvarjene commite. +```git reset --hard HEAD~#``` - Premakni glavno vejo ( master ) nazaj za # commit-ov. Ti commit-i bodo izbrisani z glavne veje! +```git checkout newbranch``` - Prestaviš se v novo vejo, ki ima vse prej ustvarjene commit-e. + +Pomembno: Vse spremembe, ki niso bile commit-ane, bodo IZGUBLJENE! \ No newline at end of file diff --git a/additional-material/translations/Slovenian/removing-a-file.sl.md b/additional-material/translations/Slovenian/removing-a-file.sl.md new file mode 100644 index 00000000000..7b75f583bf0 --- /dev/null +++ b/additional-material/translations/Slovenian/removing-a-file.sl.md @@ -0,0 +1,23 @@ +# Odstranjevanje datoteke + +Včasih si želiš odstraniti datoteko z Git-a, vendar je ne želiš odstraniti s svojega računalnika. To lahko storiš z uporabo naslednjega ukaza: + +``git rm --cached`` + +## Kaj se je zgodilo? + +Git ne bo več sledil spremembam v odstranjeni datoteki. Kar se tiče Git-a, ta datoteka ne obstaja več. Če poiščeš datoteko na svojem disku, vidiš da še vedno obstaja. + +V zgornjem primeru smo uporabili zastavico `--cached`. Če je ne bi uporabili, bi Git odstranil datoteko tudi z našega diska. + +Če sedaj ustvarimo commit z `git commit -m "Remove file1.js"` in ga pošljemo v oddaljeni repository z ukazom `git push origin master`, bo datoteka odstranjena tudi iz oddaljenega repository-ja. + +## Dodatne možnosti + +- Če želiš odstraniti več datotek, jih lahko vse vljučiš v en ukaz: + + `git rm file1.js file2.js file3.js --cached` + +- Lahko uporabiš nadomestni znak (*) da odstraniš podobne datoteke. Na primer, če želiš odstraniti vse datoteke s končnico .txt s svojega repository-ja, uporabi ukaz: + + `git rm *.txt --cached` diff --git a/additional-material/translations/Slovenian/removing-branch-from-your-repository.sl.md b/additional-material/translations/Slovenian/removing-branch-from-your-repository.sl.md new file mode 100644 index 00000000000..21be17418ac --- /dev/null +++ b/additional-material/translations/Slovenian/removing-branch-from-your-repository.sl.md @@ -0,0 +1,30 @@ +# Odstrani vejo s svojega repository-ja + +Če si sledil vodiču do tukaj, sedaj tvoja veja `` ni več uporabna in jo lahko zbrišeš z lokalnega repository-ja. To ni nujno potrebno, vendar ime te veje kaže njen namen obstoja. Ker je opravila svoje delo, jo lahko zbrišeš. + +Najprej združiš `` z glavno ( master ) vejo, zato se postavi vanjo: +``` +git checkout master +``` + +Združi `` z master: +``` +git merge master +``` + +Odstrani `` z lokalnega repository-ja: +``` +git branch -d +``` + +Sedaj si zbrisal `` vejo s svojega računalnika in vse zgleda urejeno. Vendar ta veja še vedno obstaja v tvoji GitHub različici ( fork ). Preden jo zbrišeš tudi tam, vedi da moraš najprej poslati "Pull request" mojemu repository-ju. Tako da, če je še nisem združil v moj repository, te veje na GitHub-u še ne zbriši! + +Če pa je tvoja GitHub veja že združena v moj projekt, in jo želiš zbrisati, uporabi naslednji ukaz: +``` +git push origin --delete +``` + +Sedaj veš kako počistiti neuporabne veje s svojega repository-ja. +S časom bo veliko commit-ov dodanih v moj javni repository, in glavni veji na tvojem računalniku in GitHub različici ne bosta več posodobljeni na zadnjo verzijo. Da bodo vsi tvoji repository-ji sinhronizirani z mojim, sledi korakom v tem vodiču: + +#### [Kako imeti svojo različico sinhronizirano z oddaljenim repository-em](keeping-your-fork-synced-with-this-repository.sl.md) diff --git a/additional-material/translations/Slovenian/resolving-merge-conflicts.sl.md b/additional-material/translations/Slovenian/resolving-merge-conflicts.sl.md new file mode 100644 index 00000000000..1eb3ad264c6 --- /dev/null +++ b/additional-material/translations/Slovenian/resolving-merge-conflicts.sl.md @@ -0,0 +1,34 @@ +# Kaj je spor pri združevanju? + +Ko poskusiš združiti drugo vejo v vejo v kateri trenutno delaš, vzameš spremembe iz drugega konteksta in jih združiš z datotekami s katerimi trenutno delaš. +Če dve osebi spremenita vrstico v isti datoteki, ali če se ena oseba odloči zbrisati datoteko medtem, ko se jo druga odloči spremeniti, Git ne ve več kaj je pravilno. Git bo označil datoteko kot spor. Spor, ki ga moraš razrešiti preden lahko nadaljuješ z delom. + +# Kako razrešiti spor pri združevanje? + +Ko Git zazna spor pri združevanju, bo mesto problema v datoteku označil tako, da ga bo obdal z: +“<<<<<<<< HEAD” and “>>>>>>>>>>[other branch name]” + +Vsebina za prvo oznako bo izhajala iz tvoje trenutne veje. Nato sledi vrstica z "=======", tej pa sledi vsebina iz veje, ki je v nazkrižju s tvojo. Za tem pridejo znaki ">>>>>" in ime te druge veje. +Naša naloga je da uredimo te vrstice. Ko smo končali, naj bi datoteka izgledala točno tako, kot hočemo da izgleda. Lahko da se bo potrebno posvetovati s sodelavcem, ki je napisal vsebino, ki je v navzkrižju z našo, da se bomo lahko odločili katera koda je prava. Mogoče bo tvoja, mogoče bo njegova - ali pa mešanica obeh. + +Primer: +``` + <<<<<<< HEAD:mergetest + This is my third line + ======= + This is a fourth line I am adding + >>>>>>> 4e2b407f501b68f8588aa645acafffa0224b9b78:mergetest +``` + +`<<<<<<<`: Nakazuje začetek vrstic, kjer je spor. Te vrstice so iz tvoje datoteke, ki si jo poskusil združiti. +`=======`: Nakazuje prelomno točko za primerjavo. Razdeli spremembe iz tvojega commit-a (zgoraj) in spremembe nekoga drugega (spodaj) za lažjo predstavo. +`>>>>>>>`: Nakazuje konec vrstic, kjer je spor. + +Spor razrešiš z urejanjem datoteke in ročnim združevanjem delov datoteke, kjer je Git naletel na problem. To lahko pomeni da je potrebno zavreči tvoje spremembe, spremembe nekoga drugega ali pa ustvariti mešanico obeh. Prav tako je potrebno zbrisati '<<<<<<<', '=======', in '>>>>>>>'. + +Ko je bil spor razrešen, uporabi ukaz `git add`. Ne pozabi izvesti teste, s katerimi se prepričaš da je bil spor pravilno razrešen. + +Lahko si tudi namestiš različne plugine, ki so odvisni od tvojega IDE-ja, za lažje reševanje sporov. + +# Kako razveljaviti združitev ( merge )? +Če želiš razveljaviti združitev uporabi ukaz `git merge —abort`. diff --git a/additional-material/translations/Slovenian/reverting-a-commit.sl.md b/additional-material/translations/Slovenian/reverting-a-commit.sl.md new file mode 100644 index 00000000000..7264079505a --- /dev/null +++ b/additional-material/translations/Slovenian/reverting-a-commit.sl.md @@ -0,0 +1,38 @@ +# Povrnitev commit-a + +Povrnitev commit-a pomeni, da ustvarimo nov commit, ki odstrani vse spremembe, ki smo jih napravili v prejšnjem commit-u. Kot da bi naredili ```CTRL + Z ``` v Git-u. + +Povrnitev v Git-u je sorazmerno enostavna, ker je vsak commit, ki ga pošljemo v oddaljen repository, povezan s svojim unikatnim alfanumeričnim SHA (Secure Hash Algorithm) ključem. +To pomeni da lahko povrnemu vsak commit, če le imamo njegov SHA. +V vsakem primeru pa moramo biti previdni pri povračanju, ker si lahko poškodujemo repository. + +Da lahko izberemo SHA točno določenega commit-a, ki ga hočemo odstraniti, nam zelo prav pride seznam vseh commit-ov, ki smo jih napravili. +Ta seznam dobimo s tem ukazom: +```git log --oneline ``` +Ukaz ```git log``` bi nam prav tako vrnil SHA, vendar v daljši obliki izpisa. +Uporaba zastavice ```--oneline ``` Git-u pove da hočemo pregleden izpis v eni vrstici. + +Prvih 7 znakov v vsaki vrstici izpisa se imenuje skrajšani hash commit-a. + +Za primer, to je izpis ```git log --oneline ``` za ta repository: +``` +389004d added spacing in title +c1b9fc1 Merge branch 'master' into tutorials +77eaafd added tutorial for reverting a commit +``` + +To nam torej pokaže, da lahko z ```git log --oneline```, pridobimo seznam vseh commit-ov narejenih v repository-ju s prvimi 7 znaki njihovih SHA. + +No, sedaj lahko poskusimo zbrisati commit "added spacing in title" z naslednjimi koraki: + +* Kopiraj SHA commit-a, v tem primeru ```389004d``` +* Potem uporabi ukaz ```git revert 389004d``` + +Sedaj se zažene naš urejevalnik besedila in nas pozove naj uredimo komentar commit-a. +Lahko se odločiš, da pustiš privzeto sporočilo Git-a, ki se začne z besedo `Revert`, ali pa spremeniš komentar po svojih željah. + +* Nato shranimo in zapremo urejevalnik besedila. +* Vrnemo se v ukazno vrstico. +* Uporabimo ukaz ```git push origin ``` da pošljemo spremembe na GitHub. + +In to je to, spremembe bodo odstranjene. V tem primeru bi se moj repository povrnil na stanje v commit-u ```c1b9fc1```. \ No newline at end of file diff --git a/additional-material/translations/Slovenian/squashing-commits.sl.md b/additional-material/translations/Slovenian/squashing-commits.sl.md new file mode 100644 index 00000000000..2f6a40baafe --- /dev/null +++ b/additional-material/translations/Slovenian/squashing-commits.sl.md @@ -0,0 +1,94 @@ +# Kaj je stiskanje? + +V Git-u stiskanje ( squashing ) pomeni popravljanje zgodovine svojih commit-ov, tako da na koncu ostaneš samo z enim commit-om in enim komentarjem narejenih sprememb. +To je običajni postopek v odprto kodnih projektih, ker je velik del zgodovine vsake veje pomemben samo programerju, ki jo je ustvaril. Poleg tega na ta način poenostavimo sledenje izvedenih sprememb in jih tudi lažje povrnemo v prejšnje stanje, če je to potrebno. + +# Kako stisneš commit-e? + +Najprej uporabimo ukaz `git log` da lahko pregledamp commit-e v svoji veji, ki bi jih rad združili ( merge ). + +``` +git log +``` + +Videti bi morali serijo commit-ov, kot na primer: + +``` +commit blablabla +Author: omguhh +Date: 10/10/20 + Commit message 1 + +commit blablabla2 +Author: omguhh +Date: 10/10/20 + Commit message 2 +``` + +Sedaj, ko vidimo commit-e, ki jih želimo združiti v enega, lahko začnemo tako da uporabimo ukaz ```git rebase```. Predvidevam da že poznaš ukaz ```git rebase``` in lahko začnemo stiskanje commit-ov v interaktivnem načinu ukaza `git rebase`, ki ga aktiviramo tako: + +``` +git rebase -i +``` +V interaktivnem načinu ukaza rebase lahko določimo začetno in končno točko do katere nazaj želimo iti. HEAD je začetna točka, "~2" pa pomeni da gremo dva commita nazaj v zgodovino. Ukaz se uporabi takole: + +``` +git rebase -i HEAD~2 +``` + +Ko uporabimo ta ukaz, se nam bo prikazalo nekaj podobnega tem vrsticam: + +``` +pick blablabla Changing test01.txt file +pick blablabla2 Adding dummy01.txt file + +# +# Commands: +# p, pick = use commit +# r, reword = use commit, but edit the commit message +# e, edit = use commit, but stop for amending +# s, squash = use commit, but meld into previous commit +# f, fixup = like "squash", but discard this commit's log message +# x, exec = run command (the rest of the line) using shell +# +# These lines can be re-ordered; they are executed from top to bottom. +# +# If you remove a line here THAT COMMIT WILL BE LOST. +# +# However, if you remove everything, the rebase will be aborted. +# +# Note that empty commits are commented out +``` + +Ukazi navedeni v zgornjem sporočilu: +- p, pick = uporabi commit +- r, reword = uporabi commit, vendar uredi komentar +- e, edit = uporabi commit, vendar se ustavi za spremembo +- s, squash = uporabi commit, vendar ga stisni v prejšnji commit +- f, fixup = enak kot "squash", vendar zavrzi komentar tega commit-a +- x, exec = zaženi ukaz ( preostanek vrstice ) v shell-u + +To pomeni da, če želimo stisniti ```blablabla2``` v ```blablablabla```, bi zgornje sporočilo spremenili tako: + +``` +pick blablabla Changing test01.txt file +squash blablabla2 Adding dummy01.txt file + +``` + +Če gre vse po planu, dobimo rezultat, ki zgleda takole: + +``` +# This is a combination of 2 commits. +# The first commit's message is: +commit message 1 + +# This is the 2nd commit message: + +commit message 2 +``` + +To sporočilo lahko po želji spremenimo preden zapremo urejevalnik besedila, kar shrani spremembe. + +Če še enkrat uporabimo ukaz `git log`, bi morali dobiti komentar commit-a, ki smo ga vnesli preden smo zaprli urejevalnik besedila, in commit-i bi morali biti združeni v enega. + diff --git a/additional-material/translations/Slovenian/stashing-a-file.sl.md b/additional-material/translations/Slovenian/stashing-a-file.sl.md new file mode 100644 index 00000000000..00248203439 --- /dev/null +++ b/additional-material/translations/Slovenian/stashing-a-file.sl.md @@ -0,0 +1,136 @@ +# Shranjevanje za pozneje ( Stashing ) + +Kaj storiti, če delaš na velikem projektu, in moraš nenadoma zamenjati vejo, na kateri trenutno delaš, za neko drugo vejo? Koda, na kateri si delal, ni dokončana in dokler je ne preveriš dobro, ne želiš izvesti commit. Vendar se ne moreš premakniti na drugo vejo brez da bi izvedel commit, Git ti ne pusti prekiniti delovni tok ( workflow ). Kaj storiti? Kako preprečiti nepotreben commit in hkrati preskočiti na drugo vejo? Na to vprašanje odgovarja ta vodič. + +## Shranjevanje svojega dela + +Predpostavimo da delaš na veji projekta, kjer si naredil nekaj spremembe. Če uporabiš ukaz ```git status```, lahko vidiš kje so bile spremembe narejene. + +``` +$ git status +# On branch master +# Changes to be committed: +# (use "git reset HEAD ..." to unstage) +# +# modified: index.html +# +# Changes not staged for commit: +# (use "git add ..." to update what will be committed) +# +# modified: lib/simplegit.rb +# +``` +Sedaj se želiš prestaviti na drugo vejo, vendar še nočeš izvesti commit s temi spremembami. Zato bi shranil spremembe za pozneje ( stash ). +Spremembe lahko shraniš na svoj stack z uporabo ukaza ```git stash```: + +``` +$ git stash +Saved working directory and index state \ + "WIP on master: 049d078 added the index file" +HEAD is now at 049d078 added the index file +(To restore them type "git stash apply") +``` + +Sedaj je tvoje delovno okolje ( working directory ) čisto. To lahko preveriš z uporabo ukaza ```git status```: + +``` +$ git status +# On branch master +nothing to commit, working directory clean +``` + +Sedaj se lahko prestaviš na katerokoli vejo in delaš naprej; tvoje shranjene spremembe so shranjene na stack-u. Spremembe, ki so shranjene na stack-u, si lahko ogledaš z uporabo ukaza ```git stash list```: + +``` +$ git stash list +stash@{0}: WIP on master: 049d078 added the index file +stash@{1}: WIP on master: c264051 Revert "added file_size" +stash@{2}: WIP on master: 21d80a5 added number to log +``` + +V primeru da želiš uveljaviti (re-apply) spremembe, ki si jih ravnokar shranil, lahko uporabiš ukaz ```git stash apply```. S tem ukazom lahko uveljaviš zadnjo shranjeno spremembo. Če želiš uveljaviti katerokoli drugo spremembo, jo moraš točno določiti: ```git stash apply ```, kjer je `````` ime spremembe, ki jo želiš uveljaviti. + +``` +$ git stash apply +# On branch master +# Changes not staged for commit: +# (use "git add ..." to update what will be committed) +# +# modified: index.html +# modified: lib/simplegit.rb +# +``` + +Git je sedaj spremenil datoteko, ki smo jo povrnili v prvotno stanje, ko smo spremembe shranili v stack. V tem primeru smo imeli čisto delovno okolje, ko smo poskusili uveljaviti stash, in uveljavili smo jih na isti veji, s katere smo jih shranili. Nič od tega, čisto delovno okolje in ista veja, ni nujno da uveljavimo spremembe iz stasha. Spremembe lahko shranimo na eni veji, se prestavimo na drugo vejo in tam uveljavimo iste spremembe. Lahko bi tudi spremenili ali odstranili datoteke v svojem delovnem okolju, ko bi uveljavili stash. V primeru da pride do sporov pri združevanju shranjenih sprememb v obstoječe datoteke, bo Git te spore javil. + +Spremembe so bile uveljavljene, vendar datoteka, ki je bila pripravljena za commit, sedaj ni več pripravljena. Da dosežemo še to, moramo uporabiti ukaz ```git stash apply``` z ```--index```, da sporočimo ukazu da mora uveljaviti tudi to stanje. Ko uporabimo ta ukaz, se vrnemo v točno tako stanje, kot je bilo na začetku: + +``` +$ git stash apply --index +# On branch master +# Changes to be committed: +# (use "git reset HEAD ..." to unstage) +# +# modified: index.html +# +# Changes not staged for commit: +# (use "git add ..." to update what will be committed) +# +# modified: lib/simplegit.rb +# +``` + +Ukaz `apply` samo uveljavi spremembe, ki so bile shranjene, vendar te še vedno ostanejo na stack-u. Z ukazom ```git stash list``` si lahko prikažeš vsebino stack-a. Da nekaj z njega zbrišemo, uporabimo ukaz ```git stash drop```, ki mu dodamo ime stash-a. + +``` +$ git stash list +stash@{0}: WIP on master: 049d078 added the index file +stash@{1}: WIP on master: c264051 Revert "added file_size" +stash@{2}: WIP on master: 21d80a5 added number to log +$ git stash drop stash@{0} +Dropped stash@{0} (364e91f3f268f0900bc3ee613f9f733e82aaed43) +``` + +Z ukazom ```git stash pop``` lahko hkrati uveljavimo spremembe in jih odstranimo s stack-a. + +## Razveljavljanje Stash-a + +V nekaterih primerih hočeš uveljaviti shranjene spremembe, nekaj narediti, in razveljaviti spremembe, ki so prišle iz stash-a. Git nima ukaza ```git unapply```, vendar je možno doseči isti učinek z kombiniranjem ukazov. Najprej prikažemo željeni stash in ga nato vzratno uveljavimo: + +```$ git stash show -p stash@{0} | git apply -R``` + +Če ne določimo, kateri stash želimo, Git predvideva da želimo zadnjega: + +```$ git stash show -p | git apply -R``` + +Lahko ustvariš alias in v bistvu dodaš ukaz ```stash-unapply``` v svoj Git. Na primer: + +``` +$ git config --global alias.stash-unapply '!git stash show -p | git apply -R' +$ git stash apply +$ #... work work work +$ git stash-unapply +``` + +## Ustvari vejo iz Stash-a + +Če si shranil spremembe in jih nekaj časa pustil pri miru, vmes pa delal naprej na veji s katere si jih shranil, se ti lahko naredi da boš imel težave z uveljaljanjem sprememb. Če uveljavljaš spremembe na datoteki, ki si jo vmes spremenil, boš dobil spor pri združevanju in ga boš moral razrešiti. Obstaja lažji način povračanja sprememb iz stash-a z uporabo ukaza ```git stash branch```, ki ustvari novo vejo, pridobi commit na katerem si bil, ko si shranil spremembe, na njem uveljavi spremembe in potem zbriše stash, če je bil uspešno uveljavljen: + +``` +$ git stash branch testchanges +Switched to a new branch "testchanges" +# On branch testchanges +# Changes to be committed: +# (use "git reset HEAD ..." to unstage) +# +# modified: index.html +# +# Changes not staged for commit: +# (use "git add ..." to update what will be committed) +# +# modified: lib/simplegit.rb +# +Dropped refs/stash@{0} (f0dfc4d5dc332d1cee34a634182e168c4efc3359) +``` + +To je prikladna bližnjica s katero lahko enostavo pridobimo shranjene spremembe in jih uporabimo v novi veji. \ No newline at end of file diff --git a/additional-material/translations/Slovenian/undoing-a-commit.sl.md b/additional-material/translations/Slovenian/undoing-a-commit.sl.md new file mode 100644 index 00000000000..232f04c497b --- /dev/null +++ b/additional-material/translations/Slovenian/undoing-a-commit.sl.md @@ -0,0 +1,55 @@ +# Razveljavljanje lokalnega commit-a + +Vse kar rabiš storiti, da razveljaviš lokalni commit, je: +``` +git reset +``` +Ta ukaz bo resetiral stanje v čakalnici na tvoj zadnji commit, vendar bodo spremembe ostale v delovnem okolju. Če želiš, lahko ponovno ustvariš commit s temi spremembami. +Lahko pa tudi odstraniš samo eno datoteko s svojega prejšnjega commit-a. Uporabiš ukaz: +``` +git reset +``` +Ukaz bo odstranil samo določeno datoteko s čakalnice, vendar bodo spremembe narejene na datoteki ostale. + +Primer uporabe ```git reset```: +``` +# Make changes in index.php and tutorial.php +# Add files into the staging area +$ git add . +# Remembered both files need to be committed separately +# Unstage tutorial.php +$ git reset tutorial.php +# Commit index.php first +$ git commit -m "Changed index.php" +# Commit tutorial.php now +$ git add tutorial.php +$ git commit -m "Changed tutorial.php" +``` + +Predpostavimo da si pokvaril svoj lokalni repository in ga želiš resetirati na svoj zadnji commit. +Lahko uporabiš spodnji ukaz: +``` +git reset --hard +``` +Ukaz bo izpraznil čakalnico in tudi povrnil vse spremembe v datotekah na stanje v zadnjem commit-u. +Možnost ```--hard``` pove Git-u da mora odstraniti tudi vse spremembe v delovnem okolju. +Ta ukaz uporabi samo takrat, ko si prepričan da želiš odstraniti vse spremembe nastale od zadnjega commit-a! + +Primer uporabe ukaza ```git reset --hard```: +``` +# Decided to start a crazy experiment +# Create a new file 'crazy.php' and add some code to it +# Commit crazy.php +$ git add crazy.php +$ git commit -m "Started a crazy dev" +# Edit crazy.php file again and changed a lot other files +# Commit all tracked files +$ git add . +$ git commit -m "Continued dev" +# Tested and things went out of hand +# Decided to remove the whole thing +$ git reset --hard HEAD~2 +``` +Ukaz ```git reset --hard HEAD~2``` premakne trenutno vejo nazaj za 2 commit-a in hkrati povrne vse spremembe na to točko. Odstrani tudi 2 posnetka, ki smo ju ravnokar ustvarili iz zgodovine projekta. + +P.s: Nikoli ne izvedi ```git reset --hard``` , če si že poslal svoje commit-e v skupni repository, ker boš s tem ustvaril probleme vsem, ki uporabljajo ta repository! diff --git a/additional-material/translations/Ukrainian/removing-a-file.ua.md b/additional-material/translations/Ukrainian/removing-a-file.ua.md new file mode 100644 index 00000000000..3c8fb5f564a --- /dev/null +++ b/additional-material/translations/Ukrainian/removing-a-file.ua.md @@ -0,0 +1,23 @@ +# Видалення файлу з-під GIT контролю + +Іноді може виникнути необхідність видалити файл з-під GIT контролю, але зберегти його на комп'ютері. Це може бути досягнуто за допомогою наступної команди: + +`` Git rm <файл> --cached`` + +## Що ж сталося? + +GIT більш не контролює зміни у віддаленому файлі. З точки зору GIT'а, його немає, але якщо ви спробуєте локалізувати цей файл в файловій системі, то ви побачите, що він все ще на місці. + +Зауважте, що в наведеній вище комманде використовується ключ `--cached`. Якби ми не додали цей ключ, GIT знищив би файл не тільки зі сховищ, але також і з файлової системи. + +Якщо ви зробите Комміт за допомогою команди `git commit -m" Видалити file1.js "` і потім запущено його в віддалений репозиторій командою `git push origin master`, файл буде стертий також і з віддаленого сховища. + +## Додаткова інформація + +- Якщо ви хочете видалити більше одного файлу, це можна зробити, перерахувавши всі файли в одній команді: + +    `Git rm file1.js file2.js file3.js --cached` + +- Ви можете використовувати шаблон (*) для видалення файлів з близькими іменами, наприклад, якщо ви хочете видалити всі .txt файли з локального сховища, наберіть: + +    `Git rm * .txt --cached` diff --git a/additional-material/translations/Urdu/additional-material.ur.md b/additional-material/translations/Urdu/additional-material.ur.md new file mode 100644 index 00000000000..e6f4a8d557f --- /dev/null +++ b/additional-material/translations/Urdu/additional-material.ur.md @@ -0,0 +1,46 @@ +# اضافی معلومات + +ہم سمجھتے ہیں کہ آپ یہاں آنے سے پہلے بنیادی سبق کے ساتھ پہلے ہی ختم ہو چکے ہیں. اضافی معلومات آپ کو اعلی درجے کی گیٹ کی تکنیک کے بارے میں کچھ معلومات دے گی. + +### [ایک ارتکاب ترمیم] (amending-a-commit.md) +یہ دستاویز دور دراز ذخیرہ پر ایک عہد میں ترمیم کے بارے میں معلومات فراہم کرتا ہے. +> اس کا استعمال کریں جب آپ نے ایک عہد کو ایڈجسٹ کرنے کی ضرورت ہے. + +### [Git ترتیب دیں] (configuring-git.md) +یہ دستاویز صارف کی تفصیلات اور Git میں دیگر اختیارات کو ترتیب دینے کے بارے میں معلومات فراہم کرتا ہے. +> اپنی گیٹ ترتیب کو بہتر بنانے کے لئے اس کا استعمال کریں. + +### [آپ کانٹا مخزن کے ساتھ موافقت پذیر رکھنا] (keeping-your-fork-synced-with-this-repository.md) +یہ دستاویزی معلومات فراہم کرتی ہے کہ بیس ذخیرہ کے ساتھ اپ ڈیٹ شدہ ذخیرہ رکھنے کی تاریخ کیسے برقرار رکھے گی. یہ ضروری ہے، امید ہے کہ آپ اور بہت سے دوسرے منصوبے میں حصہ لیں گے. +> ان مرحلے پر عمل کریں اگر آپ کے والدین والدین کی ذخیرہ میں کوئی تبدیلی نہیں ہے. + +### [چلتی ایک مختلف برانچ کا ارتکاب] (moving-a-commit-to-a-different-branch.md) +یہ دستاویز کسی اور برانچ میں کمیٹی منتقل کرنے کے بارے میں معلومات فراہم کرتا ہے. +> دوسری شاخ کو انجام دینے کے لۓ ان اقدامات کریں. + +### [ایک فائل اتارنے] (removing-a-file.md) +یہ دستاویز آپ کے مقامی ذخیرہ سے ایک فائل کو ہٹانے کے بارے میں معلومات فراہم کرتا ہے. +> ایک وعدہ سے پہلے ایک فائل کو ہٹانے کے بارے میں سیکھنے کے لئے ان اقدامات پر عمل کریں + +### [آپ مخزن سے شاخ ہٹا رہا ہے] (removing-branch-from-your-repository.md) +یہ دستاویز آپ کے ذخیرہ سے ایک شاخ کو کیسے خارج کرنے کے بارے میں معلومات فراہم کرتا ہے. +> آپ کے پل کی درخواست مل گئی ہے کے بعد صرف ان اقدامات کریں. + +### [حل تنازعات کو ضم کریں] (resolving-merge-conflicts.md) +یہ دستاویز مرگ تنازعات کو حل کرنے کے بارے میں معلومات فراہم کرتا ہے. +> پریشانی مر تنازعات کو حل کرنے کے لئے ان اقدامات کریں. + +### [ایک ارتکاب لوٹا رہا ہے] (reverting-a-commit.md) +یہ دستاویز دور دراز ذخیرہ پر ایک عہد کو واپس کرنے کے بارے میں معلومات فراہم کرتا ہے. یہ کام میں آتا ہے اس صورت میں جب آپ کو کسی ایسے وعدے کو رد کرنے کی ضرورت ہوتی ہے جو پہلے ہی گیتوب کو منتقل کردی گئی ہے. +> اگر آپ کسی وعدے کو ریورس کرنا چاہتے ہیں تو ان اقدامات کریں. + +### [اسکواشنگ کمیٹیاں] (squashing-commits.md) +یہ دستاویز ایک انٹرایکٹو بغاوت کے ساتھ کام کرتا ہے کس طرح اسکواش کس طرح کے بارے میں معلومات فراہم کرتا ہے. +> اس کا استعمال کریں اگر آپ ایک کھلی منبع پراجیکٹ میں پی آر کھولنا چاہتے ہیں اور تجزیہ کار آپ کو ہر ایک کو ایک باضابطہ وعدہ پیغام کے ساتھ اسکواش کرنے سے پوچھتا ہے. + +### [کالعدم کنڈ ایک مقامی ارتکاب] (undoing-a-commit.md) +یہ دستاویز آپ کے مقامی ذخیرہ پر ایک وعدے کو کس طرح رد کرنے کے بارے میں معلومات فراہم کرتا ہے. جب آپ محسوس کرتے ہیں کہ آپ نے اپنے مقامی ذخیرہ کو مسلط کیا ہے اور مقامی ذخیرہ کو ری سیٹ کرنے کا ارادہ رکھتے ہیں تو یہ وہی ہے. +> اگر یہ ایرر برقرار رہے تو ہمارے ہیلپ ڈیسک سے رابطہ کریں. غلط استعمال کی اطلاع دیتے ہوئے ایرر آ گیا ہے. + +### [مفید روابط] (Useful-links-for-further-learning.md) +یہ دستاویز تمام بلاگز خطوط، مددگار سائٹس، تجاویز اور چالوں کی ویب سائٹوں کے لئے وقف ہے جو ہماری جانوں کو آسان بنا دیتا ہے. کہ ہم اپنی تمام ضروریات کے لئے حوالہ دیتے ہیں، یہ ایک ابتدائی یا ایک ماہر بنیں. یہ صفحہ ان تمام مفید لنکس کی ایک انڈیکس کے طور پر کام کرنا چاہیے جو ہر فرد کو کھلے منبع ڈومین میں یا کسی کو مزید جاننے کے لئے مدد کرے گا. \ No newline at end of file diff --git a/additional-material/translations/Urdu/amending-a-commit.ur.md b/additional-material/translations/Urdu/amending-a-commit.ur.md new file mode 100644 index 00000000000..168fe27551e --- /dev/null +++ b/additional-material/translations/Urdu/amending-a-commit.ur.md @@ -0,0 +1,51 @@ +کمانڈر ترمیم # + +اگر آپ اپنے دور دراز ذخیرہ میں تبدیلی کرتے ہیں تو صرف اس کے بعد احساس کرنے کے لۓ آپ کے پاس وعدہ کردہ پیغام میں ٹائپو ہے یا آپ کو اپنے حالیہ حاکموں میں ایک لائن شامل کرنا بھول گیا ہے. +تم اس میں کیسے ترمیم کرتے ہو؟ یہ وہی ہے جو سبق کا احاطہ کرتا ہے. + +## آپ Github کے لئے دھکیل دیا ہے کے بعد ایک حالیہ پیغام کا ارتکاب تبدیل کرنا. + +کسی فائل کو کھولنے کے بغیر ایسا کرنے کے لئے: +* میں ٹائپ کریں `` `git commit --amend -m "اپنا نیا ارتکاب کے بعد پیغام "` `` ارتکاب +* ذخیرہ کرنے کے لئے تبدیل کرنے کے لئے چلائیں `` `git push origin ` ``. + +نوٹ: اگر آپ صرف ``` git commit --amend ``` میں ٹائپ کریں تو، آپ کے ٹیکسٹ ایڈیٹر آپ کو وعدہ پیغام میں ترمیم کرنے کے لئے فوری طور پر کھولیں گے. +`` -m`` جھگڑے کو شامل کرنے سے روکتا ہے. + +## ایک واحد پر ترمیم کا ارتکاب + +لہذا، اگر ہم ایک ہی لفظ کو تبدیل کرنے کی طرح ایک فائل میں ایک معمولی تبدیلی کرنے کے لئے بھول گئے ہیں اور ہم نے پہلے سے ہی ہمارے دور دراز ذخیرہ کرنے کے لئے وعدے کو دھکا دیا ہے؟ + +یہاں وضاحت کرنے کے لئے میری اقلیت کی لاگت ہے: + +`` ` +g56123f create file bot file +a2235d updated contributor.md +a5da0d modified bot file +`` ` +آتے ہیں کہ میں بوٹ فائل میں ایک ہی لفظ شامل کرنے کے لئے بھول گیا + +اس کے بارے میں جانے کے لۓ 2 طریقے ہیں. سب سے پہلے ایک مکمل طور پر نیا وعدہ ہے جو اس طرح کی تبدیلی پر مشتمل ہے: + +`` ` +g56123f create file botfile +a2235d updated contributor.md +a5da0d modified botfile +b0ca8f added single word to botfile +`` ` +دوسرا طریقہ 5da0d وعدہ میں ترمیم کرنا ہے، اس نئے لفظ کو شامل کریں اور یہ ایک عہد کے طور پر جتھوٹ کو دھکا دیں. +دوسری آواز بہتر ہے کیونکہ یہ صرف ایک معمولی تبدیلی ہے. + +اس کو حاصل کرنے کے لئے، ہم مندرجہ ذیل کریں گے: +* فائل میں ترمیم کریں. اس صورت میں، میں نے پہلے ہی اتار دیا گیا لفظ شامل کرنے کے لئے میں botfile میں ترمیم کریں گے. +* اگلا، فیلڈ اسٹینج علاقے میں `` `git add ` `` + +عام طور پر اسٹینجنگ علاقے میں فائلوں کو شامل کرنے کے بعد، ہمارا اگلا کام ہمارا وعدہ ہے - ہمارا وعدہ پیغام "صحیح ہے؟ +لیکن چونکہ ہم یہاں حاصل کرنا چاہتے ہیں اس سے پچھلے وعدوں میں ترمیم کرنا ہے، ہم اس کے بجائے چلائیں گے: + +* `` `git commit --amend ` `` + اس کے بعد ٹیکسٹ ایڈیٹر کو لانے اور پیغام کو ترمیم کرنے کے لئے آپ کو فوری طور پر کریں گے. آپ پیغام کو چھوڑنے کا فیصلہ کر سکتے ہیں کیونکہ اس سے پہلے تھا یا اسے تبدیل کر دیا گیا تھا. +* ایڈیٹر سے باہر نکلیں +* اپنی تبدیلیوں کو دھکا دیں `` `git push origin ` `` + +اس طرح، دونوں تبدیلیاں ایک ہی انجام میں ہو گی. \ No newline at end of file diff --git a/additional-material/translations/Useful-links-for-further-learning.id.md b/additional-material/translations/Useful-links-for-further-learning.id.md new file mode 100644 index 00000000000..5cbbf0a4185 --- /dev/null +++ b/additional-material/translations/Useful-links-for-further-learning.id.md @@ -0,0 +1,45 @@ +# Tautan-tautan Bermanfaat + +Dokumen ini didedikasikan untuk semua situs web tips dan trik, postingan blog, dan situs bermanfaat yang membuat hidup kita lebih mudah. Ini adalah referensi yang bagus untuk memenuhi semua kebutuhan kita, baik itu pemula maupun ahli. Halaman ini berisi indeks dari semua tautan berguna yang akan membantu semua pemula dalam domain sumber terbuka atau seseorang yang ingin mempelajari lebih lanjut. + + +## Daftar Isi +1. [Tutorial git interaktif](https://try.github.io) +2. [Youtube: Git dan GitHub untuk pemula oleh freecodecamp](https://www.youtube.com/watch?v=RGOj5yH7evk) +3. [Git - panduan sederhana](http://rogerdudler.github.io/git-guide/) +4. [Tentang mengembalikan, menyesuaikan, atau menghapus commit pada git](http://sethrobertson.github.io/GitFixUm/fixup.html) +5. [Git and GitHub terjemahan tutorial untuk banyak bahasa](https://github.com/Roshanjossey/first-contributions) +6. [Konflik Merge](https://www.git-tower.com/learn/git/ebook/en/command-line/advanced-topics/merge-conflicts) +7. [Memperbaiki Konflik Merge](https://githowto.com/resolving_conflicts) +8. [Dasar - Dasar Git - Panduan cepat dan sederhana](https://blog.praveen.science/basics-of-git-the-quick-start-guide/) +9. [Standar - Standar Git menurut Agile Methodology Spotify](https://blog.praveen.science/git-standards-followed-in-our-way-of-spotify-agile-methodolgy/) +10. [Pintasan pada Git](https://blog.praveen.science/git-shortcuts/) +11. [Contekan Git resmi semua bahasa](https://services.github.com/on-demand/resources/cheatsheets) +12. [Contekan Git dari Tower](https://www.git-tower.com/learn/cheat-sheets/git) +13. [Permasalahan Umum Git](https://www.codementor.io/citizen428/git-tutorial-10-common-git-problems-and-how-to-fix-them-aajv0katd) +14. [Rebase pada Git](https://blog.gitprime.com/git-rebase-an-illustrated-guide/) +15. [Panduan Pemula untuk melakukan Rebase dan Squash](https://github.com/servo/servo/wiki/Beginner%27s-guide-to-rebasing-and-squashing) +16. [Contekan Git yang menunjukan korelasi antara perintah dan file](http://ndpsoftware.com/git-cheatsheet.html) +17. [Bagaimana Cara Berkontribusi](https://opensource.guide/how-to-contribute/) +18. [Memulai dengan Sumber Terbuka](https://github.com/OpenSourceHelpCommunity/Getting-Started-With-Contributing-to-Open-Sources) +19. [Bagaimana Cara Berkontribusi](https://github.com/freeCodeCamp/how-to-contribute-to-open-source) +20. [Tutorial Git Atlassians](https://www.atlassian.com/git) +21. [Tinjauan permintaan Pull](https://help.github.com/articles/about-pull-request-reviews/) +22. [Tutorial Interaktif lainnya untuk git](https://learngitbranching.js.org/) +23. [Contekan baris perintah pada Git](https://gist.github.com/davfre/8313299) +24. [Buku - Buku Pemrograman](https://github.com/EbookFoundation/free-programming-books) +25. [E-Book untuk profesional tip and rahasia](https://goalkicker.com/GitBook/GitProfessionalTipsSecrets.pdf) +26. [Tutorial tentang cara sederhana menjadi profesional git](https://medium.freecodecamp.org/follow-these-simple-rules-and-youll-become-a-git-and-github-master-e1045057468f) +27. [Sebuah catatan tentang Pesan Git Commit](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) +28. [5 Tip Berguna Untuk Pesan Commit yang baik](https://thoughtbot.com/blog/5-useful-tips-for-a-better-commit-message) +29. [Kontrol Versi menggunakan Git](https://ourcodingclub.github.io/2017/02/27/git.html) +30. [Kontrol Versi dengan Git](https://www.udacity.com/course/version-control-with-git--ud123) +31. [Memeriksa kursus Coursera dari Google](https://www.coursera.org/learn/introduction-git-github) +32. [Menggunakan Kontrol Versi pada VS Code](https://code.visualstudio.com/docs/editor/versioncontrol) +33. [Git vs Github: Apa Perbedaannya dan Bagaimana cara menggunakan keduanya](https://kinsta.com/knowledgebase/git-vs-github/) +34. [Panduan Hello World Github](https://guides.github.com/activities/hello-world/) +35. [Bagaimana cara menggunakan GitHub](https://www.edureka.co/blog/how-to-use-github/) +36. [10 Hari tentang Git and Github](https://github.com/Asabeneh/10-days-of-git-and-github) +37. [Pintasan Keyboard untuk Github](https://docs.github.com/en/get-started/using-github/keyboard-shortcuts) +38. [Tutorial Lengkap Git and GitHub oleh Kunal Kushwaha](https://www.youtube.com/watch?v=apGV9Kg7ics&ab_channel=KunalKushwaha) +Keep adding more links, that you find helpful. diff --git a/additional-material/translations/Vietnamese/resolving-merge-conflicts.vi.md b/additional-material/translations/Vietnamese/resolving-merge-conflicts.vi.md new file mode 100644 index 00000000000..b804171f36f --- /dev/null +++ b/additional-material/translations/Vietnamese/resolving-merge-conflicts.vi.md @@ -0,0 +1,33 @@ +# Mâu Thuẫn Khi Tích Hợp là gì? + +Khi bạn cố gắng tích hợp một nhánh khác vào nhánh làm việc hiện tại của bạn, bạn đang thực hiện các thay đổi từ bối cảnh khác và kết hợp chúng với các tệp tin hiện tại bạn đang làm việc. +Nếu hai người đã thay đổi cùng một dòng trong cùng một tệp hoặc nếu một người quyết định xóa nó trong khi người kia quyết định sửa đổi nó, Git không thể xác định đâu là phiên bản chính xác. Git sau đó sẽ đánh dấu tệp là có xung đột - điều mà bạn sẽ phải giải quyết trước khi bạn có thể tiếp tục công việc của mình. + +# Làm thế nào để giải quyết xung đột khi tích hợp? + +Khi đối mặt với việc xảy ra xung đột khi tích hợp, git sẽ đánh dấu khu vực có vấn đề trong tệp bằng cách đặt nó vào trong "<<<<<<<<< HEAD" và ">>>>>>>>>>[other branch name]" + +Các nội dung sau điểm đánh dấu đầu tiên bắt nguồn từ nhánh làm việc hiện tại của bạn. Sau dấu ngoặc nhọn, Git cho chúng ta biết những thay đổi đến từ đâu (từ nhánh nào). Dòng có "=======" phân tách hai thay đổi xung đột. Công việc của chúng tôi bây giờ là giải quyết những dòng này: khi chúng ta hoàn thành, tệp sẽ trông chính xác như chúng ta muốn. Nên tham khảo ý kiến của người đồng đội đã viết những thay đổi mâu thuẫn để quyết định phiên bản nào sẽ là bản cuối cùng. Nó có thể là của bạn - hoặc có thể là hỗn hợp giữa hai người. + +Ví dụ: +``` +<<<<<<< HEAD:mergetest + This is my third line + ======= + This is a fourth line I am adding + >>>>>>> 4e2b407f501b68f8588aa645acafffa0224b9b78:mergetest +``` + +`<<<<<<<`: Cho biết nơi bắt đầu của các dòng có xung đột khi tích hợp. Những dòng đầu tiên là các dòng từ tệp tin mà bạn đang thử tích hợp các thay đổi vào. +`=======`: Cho biết điểm phân chia được sử dụng để so sánh các thay đổi. Phân chia các thay đổi mà người dùng đã cam kết (ở trên) đối với các thay đổi đến từ nhánh tích hợp (bên dưới) để thấy rõ sự khác biệt. +`>>>>>>>`: Cho biết kết thúc của các dòng có xung đột khi tích hợp. + +Bạn giải quyết xung đột bằng cách chỉnh sửa tệp và sau đó tích hợp thủ công các phần của tệp mà git gặp sự cố khi tích hợp. Điều này có thể có nghĩa là loại bỏ các thay đổi của bạn hoặc của người khác hoặc đi tới việc kết hợp thay đổi của cả hai. Bạn cũng sẽ cần xóa '<<<<<<<', '=======' và '>>>>>>>' trong tệp. + +Một khi bạn đã giải quyết xung đột, chạy lệnh `git add`. Đừng quên chạy thử nghiệm, vì bạn phải chắc chắn rằng bạn đã giải quyết được xung đột. + +Bạn cũng có thể tải xuống các plugin khác nhau tùy thuộc vào IDE bạn đang sử dụng để có cách dễ dàng hơn để giải quyết xung đột hợp nhất. + +# Làm thế nào để hoàn tác lại tích hợp? + +Nếu bạn muốn hoàn tác lại tích hợp thì bạn có thể thực hiện `git merge —abort` diff --git a/additional-material/translations/additional-material.np.md b/additional-material/translations/additional-material.np.md new file mode 100644 index 00000000000..eb755c0ca44 --- /dev/null +++ b/additional-material/translations/additional-material.np.md @@ -0,0 +1,48 @@ +# थप जानकारी +हामी मान्दछौं कि तपाईंले यहाँ जानु अघि आधारभूत ट्यूटोरियल पढिसक्नुभएको छ। यो कागजातले तपाईंलाई Git प्रविधिहरूमा थप जानकारी दिनेछ उन्नत । + +### [प्रतिबद्धता सम्पादन गर्नुहोस्](amending-a-commit.np.md) +यो पृष्ठले तपाईंलाई रिमोट डाइरेक्टरीमा कमिट परिमार्जन गर्न आवश्यक जानकारी दिनेछ: +> तपाईंले गर्नुभएको प्रतिबद्धता ठीक गर्न यो प्रयोग गर्नुहोस्। + +### [git कन्फिगर गर्नुहोस्](configuring-git.np.md) +यो पृष्ठले तपाइँलाई तपाइँको प्रयोगकर्ता विवरणहरू र git मा अन्य विकल्पहरू कन्फिगर गर्न आवश्यक जानकारी दिनेछ: +> तपाईंको git कन्फिगरेसनको राम्रो नियन्त्रणको लागि प्रयोग गर्नुहोस्। + +### [डाइरेक्टरी संग सिंक मा आफ्नो फोर्क राख्नुहोस्](keeping-your-fork-synced-with-this-repository.np.md) +यो कागजातले तपाईंलाई स्रोत डाइरेक्टरीसँग "फोर्क" डाइरेक्टरीलाई अद्यावधिक राख्नको लागि जानकारी दिन्छ। यो महत्त्वपूर्ण छ र हामी आशा गर्छौं कि तपाईं र अरू धेरैले यस परियोजनामा ​​योगदान गर्नुहुनेछ। +> यदि तपाईंले अभिभावक डाइरेक्टरीमा आफ्नो शाखामा कुनै परिवर्तनहरू देख्नुभएन भने यी चरणहरू पालना गर्नुहोस्। + +### [एउटा कमिटलाई फरक शाखामा सार्नुहोस्](moving-a-commit-to-a-different-branch.np.md) +यो पृष्ठले तपाईंलाई फरक शाखामा प्रतिबद्धता सार्न आवश्यक जानकारी दिनेछ: +> कमिटलाई फरक खुट्टामा सार्न यी चरणहरू पालना गर्नुहोस्। + +### [फाइल मेटाउनुहोस्](removing-a-file.np.md) +यो पृष्ठले तपाईंलाई आफ्नो स्थानीय डाइरेक्टरीबाट फाइल मेटाउन आवश्यक जानकारी दिनेछ: +> कमिट गर्नु अघि फाइल कसरी मेटाउने भनेर सिक्नको लागि यी चरणहरू पालना गर्नुहोस्। + +### [तपाईंको डाइरेक्टरीमा एउटा शाखा मेटाउनुहोस्](removing-branch-from-your-repository.np.md) +यस पृष्ठले तपाइँलाई तपाइँको निर्देशिकाबाट शाखा मेटाउन आवश्यक जानकारी दिनेछ: +> तपाईंको पुल अनुरोध मर्ज भएपछि मात्र यी चरणहरू पालना गर्नुहोस्। + +### [मर्ज विवादहरू समाधान गर्नुहोस्](resolving-merge-conflicts.np.md) +यो पृष्ठले तपाईंलाई मर्ज मुद्दाहरूको समस्या निवारण गर्न आवश्यक जानकारी दिनेछ: +> यी (प्रायः कष्टप्रद) मिश्रण समस्याहरू समाधान गर्न यी चरणहरू पालना गर्नुहोस्। + +### [प्रतिबद्धतामा फर्कनुहोस्](reverting-a-commit.np.md) +यदि तपाइँ रिमोट डाइरेक्टरीमा अघिल्लो कमिटमा फर्कन आवश्यक छ भने यो पृष्ठले तपाइँलाई मद्दत गर्नेछ। तपाईले पहिले नै Github मा धकेल्नु भएको कमिटलाई अन्डू गर्न आवश्यक छ भने यो उपयोगी छ। +> यदि तपाइँ कमिट उल्टाउन चाहनुहुन्छ भने यी चरणहरू पालना गर्नुहोस्। + +### [सपाट कमिटहरू](squashing-commits.np.md) +यस पृष्ठले तपाइँलाई सिकाउनेछ कि कसरी एकमा धेरै कमिटहरू समतल गर्ने। +> यदि तपाइँ पुल अनुरोध खोल्न चाहनुहुन्छ भने प्रयोग गर्नुहोस् र समीक्षकले तपाइँलाई समग्र जानकारी सन्देश सहित सबै कमिटहरूलाई "फ्लैट" गर्न सोध्छन्। + +### [उपयोगी लिङ्कहरू](undoing-a-commit.np.md) +यो पृष्ठले तपाइँलाई तपाइँको स्थानीय डाइरेक्टरीमा कमिट अनडू गर्न आवश्यक जानकारी दिन्छ। यदि तपाईंले आफ्नो स्थानीय डाइरेक्टरीमा गल्ती गरेको महसुस गर्नुभयो र अघिल्लो अवस्थामा फर्कन चाहनुहुन्छ भने तपाईंले यो गर्न आवश्यक छ। +> यदि तपाइँ स्थानीय कमिटमा पूर्वस्थितिमा पूर्ववत/उल्टाउन चाहनुहुन्छ भने यी निर्देशनहरू पालना गर्नुहोस्। + +### [उपयोगी लिङ्कहरू](Useful-links-for-further-learning.np.md) +यो पृष्ठ सबै टिप्स र ट्रिक्स साइटहरू, ब्लगहरू, र सामान्य साइटहरूमा समर्पित छ जसले हामीलाई हाम्रो जीवन सजिलो बनाउन मद्दत गर्दछ। तिनीहरू तपाइँका सबै आवश्यकताहरू पूरा गर्न उत्कृष्ट सन्दर्भहरू हुन्, चाहे तपाइँ शुरुवात वा विशेषज्ञ हुनुहुन्छ। यो पृष्ठ ती सबै उपयोगी लिङ्कहरूको अनुक्रमणिका हुनुपर्छ जसले खुला स्रोतमा नयाँ भएका वा आफ्नो ज्ञानलाई अझ गहिरो बनाउन चाहने जो कोहीलाई मद्दत गर्नेछ। + +### [एउटा .gitignore फाइल सिर्जना गर्नुहोस्](creating-a-gitignore-file.np.md) +यो कागजातले .gitignore फाइल केका लागि हो, यसलाई किन प्रयोग गर्ने र कसरी सिर्जना गर्ने भनेर बताउँछ। यो फाइल लगभग सबै git परियोजनाहरूमा प्रयोग गरिन्छ। यसले कमिटहरूमा मात्र आवश्यक फाइलहरू विचार गर्न मद्दत गर्दछ। diff --git a/additional-material/translations/amending-a-commit.np.md b/additional-material/translations/amending-a-commit.np.md new file mode 100644 index 00000000000..d178f18a898 --- /dev/null +++ b/additional-material/translations/amending-a-commit.np.md @@ -0,0 +1,50 @@ +# प्रतिबद्धता सम्पादन गर्नुहोस् + +मानौं कि तपाईंले आफ्नो रिमोट डाइरेक्टरीमा प्रतिबद्धता गर्नुभयो र पछि यो महसुस गर्नुहोस् कमिट सन्देशमा टाइपो छ वा तपाईंले आफ्नो अन्तिम कमिटमा लाइन थप्न बिर्सनुभयो। यो त्रुटि कसरी सच्याउने? यो यस ट्यूटोरियल को विषय हो। + +## Github मा धक्का दिए पछि भर्खरको प्रतिबद्ध सन्देश परिवर्तन गर्नुहोस् +फाइल नखोली नै यो गर्नका लागि: +* आदेश टाइप गर्नुहोस् ```git कमिट --amend -m "तपाईँको नयाँ प्रतिबद्ध सन्देश पछि"``` +* निर्देशिकामा कमिट गर्न ```git push origin ``` आदेश चलाउनुहोस्। + +NB: यदि तपाइँ केवल ```git कमिट --amend``` टाइप गर्नुहुन्छ भने, पाठ सम्पादक खुल्छ र तपाइँलाई परिमार्जन गर्न सोध्छ। +सन्देश पठाउनुहोस्। पाठ सम्पादक प्रयोग गर्नबाट बच्न ``-m`` विकल्प थप्नुहोस्। + +## एक विशिष्ट प्रतिबद्धता परिमार्जन गर्नुहोस् + +त्यसोभए के हुन्छ यदि तपाईंले फाइलमा सानो परिवर्तन गर्न बिर्सनुभयो, जस्तै शब्द परिवर्तन गर्नुहोस् र +तपाईंले पहिले नै हाम्रो रिमोट डाइरेक्टरीमा यो प्रतिबद्धता पुश गरिसक्नुभएको छ? + +यस बिन्दुलाई चित्रण गर्न, यहाँ मेरो प्रतिबद्धताहरूको लग छ; +``` +g56123f बोट फाइल सिर्जना गर्दै +contributor.md बाट a2235d अपडेट +a5da0d बोट फाइल सम्पादन गर्नुहोस् +``` +कल्पना गरौं कि मैले बोट फाइलमा एउटा शब्द थप्न बिर्सें। + +यो समस्या समाधान गर्न दुई तरिकाहरू छन्। पहिलो भनेको नयाँ प्रतिबद्धता बनाउनु हो जसमा परिवर्तन समावेश छ: +``` +g56123f बोट फाइल सिर्जना गर्दै +contributor.md बाट a2235d अपडेट +a5da0d बोट फाइल सम्पादन गर्नुहोस् +b0ca8f बोट फाइलमा शब्द थप्नुहोस् +``` +दोस्रो तरिका भनेको a5da0d कमिट परिमार्जन गर्नु हो र यो नयाँ शब्द थप्नुहोस् र यसलाई Github मा सबै एक कमिटमा पुश गर्नुहोस्। +यो दोस्रो विकल्प बढी उपयुक्त देखिन्छ, यो एक सानो परिवर्तन हो। + +त्यसो गर्न, यी चरणहरू पालना गर्नुहोस्: +* फाइल सम्पादन गर्नुहोस्। हाम्रो अवस्थामा, हामी बिर्सिएको शब्द समावेश गर्न बोट फाइल परिमार्जन गर्छौं। +* त्यसपछि फाइललाई स्टेजिङ क्षेत्रमा ```git add ``` आदेशको साथ थप्नुहोस् + +सामान्यतया, स्टेजिङ क्षेत्रमा फाइलहरू थपेपछि, अर्को चरण आदेश चलाउन हो +git कमिट -एम "हाम्रो प्रतिबद्ध सन्देश", हैन? तर हामी यहाँ के चाहन्छौं भने प्रतिबद्धता परिमार्जन गर्नु हो +अघिल्लो, हामी यसको सट्टा आदेशहरू चलाउनेछौं: + +* ``git कमिट -- amend``` + यसले पाठ सम्पादक ल्याउनेछ जसले तपाईंलाई सन्देश सम्पादन गर्न सोध्छ। तपाईं छोड्ने निर्णय गर्न सक्नुहुन्छ + सन्देश जस्तो छ वा परिवर्तन गर्नुहोस्। +* सम्पादकबाट बाहिर निस्कनुहोस् +* आफ्ना परिवर्तनहरूलाई ```git push origin ``` सँग पुश गर्नुहोस् + +यसरी दुबै परिवर्तनहरू एउटै कमिटमा छन्। diff --git a/additional-material/translations/configuring-git.np.md b/additional-material/translations/configuring-git.np.md new file mode 100644 index 00000000000..1a55e88227d --- /dev/null +++ b/additional-material/translations/configuring-git.np.md @@ -0,0 +1,77 @@ +# Git वातावरण सेट अप गर्दै + +पहिलो पटक तपाईंले Git सँग कमिट गर्ने प्रयास गर्नुभयो, तपाईंले निम्न सन्देश देख्न सक्नुहुन्छ: + +```bash +$ git commit +*** Please tell me who you are. + +Run + +git config --global user.email "you@example.com" +git config --global user.name "Your Name" + +to set your account's default identity. +config --global to set the identity only in this repository. +``` + +Git लाई कमिट सिर्जना गर्न को लागी तपाई को हुनुहुन्छ भनेर जान्न आवश्यक छ। जब तपाइँ धेरै व्यक्तिहरूसँग समूहमा काम गर्नुहुन्छ, तपाइँलाई सधैं थाहा हुनुपर्छ कि कसले परियोजनामा ​​​​कुन परिवर्तन गर्यो र उनीहरूले यो कहिले गरे। यस अन्तको लागि, Git सिर्जना गरिएको थियो ताकि कमिटहरू नाम र ईमेलमा बाँधिएका छन्। + +त्यहाँ 'git कमिट' आदेशमा तपाईंको नाम र इमेल प्रदान गर्ने धेरै तरिकाहरू छन्, र हामी ती मध्ये केहीलाई निम्न लाइनहरूमा जानेछौं। + +### ग्लोबल कन्फिगरेसन + +जब हामीले ग्लोबल कन्फिगरेसन (ग्लोबल कन्फिगरेसन) मा केहि बचत गर्छौं, यो सेटिङ तपाईंले काम गर्ने सबै भण्डारहरूमा उपलब्ध हुन्छ। यो विधि सिफारिस गरिएको छ र अधिकतर अवस्थामा काम गर्दछ। + +ग्लोबल कन्फिगरेसनमा केहि बचत गर्न, 'config' आदेश प्रयोग गर्नुहोस्: + +`$ git config --global ` + +प्रयोगकर्ता डेटा को मामला मा: + +``` +$ git config --global user.email "you@example.com" +$ git config --global user.name "Your Name" +``` + +### भण्डार कन्फिगरेसन + +नामले नै हामीलाई बताउँछ, यी कन्फिगरेसनहरू केवल एउटा भण्डारमा सीमित छन्। यदि तपाइँ एक विशेष भण्डारमा प्रतिबद्ध गर्न चाहनुहुन्छ भने, तपाइँको कामको इ-मेलको साथ कार्य परियोजना भन्नुहोस्, त्यसपछि हामी यो विधि प्रयोग गर्दछौं। + +भण्डार कन्फिगरेसनमा केहि बचत गर्न, `config` आदेश प्रयोग गर्नुहोस् र `--global` झण्डा छोड्नुहोस्: + + +`$ git config ` + +प्रयोगकर्ता डेटा को मामला मा: + +``` +$ git config user.email "you@alternate.com" +$ git config user.name "Your Name" +``` + +### कमाण्ड लाइन कन्फिगरेसन + +यी कन्फिगरेसनहरू हालको आदेश रेखामा मात्र सीमित छन्। सबै Git आदेशहरूले आदेश क्रियाको अगाडि `-c` उपसर्ग स्वीकार गर्दछ। यसले अस्थायी कन्फिगरेसन सिर्जना गर्दछ। + +आदेश रेखा कन्फिगरेसनमा केहि बचत गर्न: + +`$ git -c = -c = ` + +हाम्रो उदाहरणमा, हामी कमिट आदेशलाई यसरी प्रयोग गर्नेछौं: + +`git -c user.name='Your Name' -c user.email='you@example.com' commit -m "Your commit message"` + +### फाइदाको बारेमा + +माथि उल्लिखित विधिहरू बीच प्रयोगको क्रम निम्नानुसार छ `command-line > repository > global`. यसको मतलब यदि चर कमाण्ड लाइन र ग्लोबलमा भण्डार गरिएको छ भने, कमाण्ड लाइन कन्फिगरेसनमा मान प्रयोग गरिनेछ। + +## साथै + +अहिलेसम्म हामीले प्रयोगकर्ता सेटिङहरूमा मात्र काम गरेका छौं, तर त्यहाँ केही अन्य कन्फिगरेसनहरू छन्। ती मध्ये केही हुन्: + +1. `core.editor` - टिप्पणी लेख्न प्रयोग गर्न पाठ सम्पादक निर्दिष्ट गर्न, आदि। +2. `commit.template` - प्रारम्भिक कमिट टेम्प्लेटको रूपमा प्रयोग गर्न प्रणालीमा फाइल निर्दिष्ट गर्न +3. `color.ui` - Git को आउटपुटमा रङहरू प्रयोग गर्न बुलियन मान निर्दिष्ट गर्न। + +हामीले सजिलै बुझ्नको लागि केही विवरणहरू सरलीकृत गरेका छौं। तपाईं मा थप पढ्न सक्नुहुन्छ [git-scm.com](https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration). diff --git a/additional-material/translations/delete-branch-locally.fa.md b/additional-material/translations/delete-branch-locally.fa.md new file mode 100644 index 00000000000..a0a5e719f08 --- /dev/null +++ b/additional-material/translations/delete-branch-locally.fa.md @@ -0,0 +1,19 @@ +# حذف کردن شاخه که به صورت محلی ایجاد شده است + +این در زمانی سودمند خواهد بود که شما نام یک شاخه (برنچ) را اشتباه نوشته اید. + +این کار به *3* روش قابل انجام است + +``` +git branch -D +``` + +``` +git branch --delete --force # Same as -D +``` + +``` +git branch --delete # Error on unmerge +``` + +پرچم `D-` مخفف `delete --force--` است که شاخه را حتی اگر مرج نشده باشد حذف میکند. (حذف اجباری)، ولی شما میتوانید از پرچم `d-` استفاده کنید که مخفف `delete--` است که با توجه با وضعیت مرج شاخه ارور خواهد داد. \ No newline at end of file diff --git a/cli-tool-tutorials/git-bash-windows-tutorial.md b/cli-tool-tutorials/git-bash-windows-tutorial.md new file mode 100644 index 00000000000..f1a1e511fa3 --- /dev/null +++ b/cli-tool-tutorials/git-bash-windows-tutorial.md @@ -0,0 +1,129 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# First Contributions + +| Git Bash | Git Bash Edition | +| ---------------------------------------------------------------------------------------------------------------------- | ---------------- | + +It's hard. It's always hard the first time you do something. Especially when you are collaborating, making mistakes isn't a comfortable thing. But open source is all about collaboration & working together. We wanted to simplify the way new open-source contributors learn & contribute for the first time. + +Reading articles & watching tutorials can help, but what comes better than actually doing the stuff without messing up anything. This project aims at providing guidance & simplifying the way rookies make their first contribution. Remember the more relaxed you are the better you learn. If you are looking for making your first contribution just follow the simple steps below. We promise you, it will be fun. + +If you don't have Git Bash on your windows machine, [install it](https://git-scm.com/download/win). + +fork this repository + +## Fork this repository + +Fork this repo by clicking on the fork button on the top right of this page. +This will create a copy of this repository in your account. + +## Clone the repository + +Now clone this repo to your machine. + +IMPORTANT: DO NOT CLONE THE ORIGINAL REPO. Go to your fork and clone it. + +To clone the repo, click on "Code" and then copy the string down below. + +`copy string` + +Open the git bash application you just downloaded. It should look like the image down below if its on a windows machine. + +`open git bash terminal` + +Go to the folder that you want to save this project on by uisng this command + +`cd ` + +`cd into a folder` + +Use the string you copied in the step above to clone the repository using this command + +`git clone ` + +`clone the repository` + +Go to the directory where the repo is and open it up on vs code to make your changes. + +`cd into the newly cloned repo` + +## Create a branch + +Now create a branch by uing this simple command. This command not only creates a branch for you but also lets you switch to that branch. + +``` +git checkout -b +``` + +Name your branch ``. For example, "add-james-smith" + +`create a branch` + +## Make necessary changes and commit those changes + +Now open `Contributors.md` file in a text editor, scroll to the bottom of the page and add your name to it, then save the file. + +Example: If your name is James Smith, It should look like this. + +\[James Smith](https://github.com/jamessmith) + +You can see that there are changes to Contributors.md by simply running this command + +`git status` + +`check the status` + +Now commit those changes: + +First add the change you made to the staging area by using + +`git add file-name` + +Then write a commit message by sing this command + +`git commit -m "Add your-name to Contributors list"` + +Replace `` with your name. + +`commit changes` + +To see if your commit has been made you can run a simple `git log --oneline` command. + +## Push changes to github + +Once you are done with the above steps you can push your changes by using this command + +`git push origin ` + +`push changes` + +## Submit your changes for review + +If you go to your repository on github, you'll see `Compare & pull request` button. click on that button. + +create a pull request + +Now submit the pull request. + +submit pull request + +Soon I'll be merging all your changes into the master branch of this project. You will get a notification email once the changes have been merged. + +## Where to go from here? + +Congrats! You just completed the standard _fork -> clone -> edit -> PR_ workflow that you'll encounter often as a contributor! + +Celebrate your contribution and share it with your friends and followers by going to [web app](https://firstcontributions.github.io#social-share). + +You can join our slack team in case you need any help or have any questions. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +### [Additional material](../additional-material/git_workflow_scenarios/additional-material.md) + +## Tutorials Using Other Tools + +[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools) diff --git a/cli-tool-tutorials/github-cli-tutorial.md b/cli-tool-tutorials/github-cli-tutorial.md new file mode 100644 index 00000000000..a4da2e43605 --- /dev/null +++ b/cli-tool-tutorials/github-cli-tutorial.md @@ -0,0 +1,101 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# First Contributions + +| GitHub Desktop | GitHub Command Line Interface (CLI) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| + +This is a guide for us the terminal nerds who wants to do everything in the terminal, and thanks to the [Github-CLI](https://cli.github.com/) we can achieve it, remember your first contribution should be fun, rewarding and a motivator just to keep going! + +This guide is a bit more challenging since we are not using any graphical interface at all, but still it's really fun and you can totally follow it! + +The first requisite is to have: +- Git installed (how to install [git](https://git-scm.com/downloads)) +- Github account + +Now we need to install the github-cli tool in our system by following the [official documentation](https://github.com/cli/cli#installation) + +After that, we need to login in the CLI so enter this command: +```bash +gh auth login +``` + +Follow the instructions and we are ready! + +# Fork this repository +It's just as easy as running this command: + +```bash +gh repo fork firstcontributions/first-contributions +``` +**Important: It will prompt you if you want to clone it as well, select the "yes" option** + +# Create your branch +We will do this step with git, so we enter this command replacing the name with your name, for example: +```bash +git switch -c add-john-doe +``` + +# Make necessary changes and commit those changes +Now you can open `Contributors.md` file in a text editor, add your name to it. Put your name anywhere between the beginning and the end, now save the file. + +In the project directory execute `git status` and you will see the changes. +![image-git](https://camo.githubusercontent.com/a35c4722d7aab337eefc655d1488f7b4dc038508e6adaf5e88e2e052a976f010/68747470733a2f2f6669727374636f6e747269627574696f6e732e6769746875622e696f2f6173736574732f526561646d652f6769742d7374617475732e706e67) + +Add those changes to the branch you just created using the `git add` command: +`git add Contributors.md` + +Now commit those changes using the `git commit` command: +`git commit -m "Add your-name to Contributors list` +replacing `your-name` with your name. + +# Push changes to github +Push your changes using the command `git push`: + +``` +git push origin -u your-branch-name +``` + +replacing `your-branch-name` with the name of the branch you created earlier. + +
+ If you get any errors while pushing, click here: + +- ### Authentication Error + 
remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead.
+  remote: Please see https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ for more information.
+  fatal: Authentication failed for 'https://github.com//first-contributions.git/'
+ Go to [GitHub's tutorial](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account) on generating and configuring an SSH key to your account. + +
+ +# Submit your changes for review +Now running this command in our repo's directory will let us create a pull request for review: + +```bash +gh pr create --repo firstcontributions/first-contributions +``` + +After that submit the pull request. + +You can use the command `gh status` to see your mentioned pull request in action. + +## Where to go from here? + +Congrats! You just completed the standard _fork -> clone -> edit -> pull request_ workflow that you'll often encounter as a contributor! + +Celebrate your contribution and share it with your friends and followers by going to [web app](https://firstcontributions.github.io/#social-share). + +You could join our slack team if you need any help or have any questions. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-vchl8cde-S0KstI_jyCcGEEj7rSTQiA). + +Now let's get you started with contributing to other projects. We've compiled a list of projects with easy issues you can get started on. Check out [the list of projects in the web app](https://firstcontributions.github.io/#project-list). + +### [Additional material](additional-material/git_workflow_scenarios/additional-material.md) + +## Tutorials Using Other Tools + +[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools) diff --git a/gui-tool-tutorials/github-desktop-old-version-tutorial.md b/gui-tool-tutorials/github-desktop-old-version-tutorial.md new file mode 100644 index 00000000000..19bec585225 --- /dev/null +++ b/gui-tool-tutorials/github-desktop-old-version-tutorial.md @@ -0,0 +1,108 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# First Contributions + +|GitHub Desktop|GitHub Desktop Edition| +|---|---| + +It's hard. It's always hard the first time you do something. Especially when you are collaborating, making mistakes isn't a comfortable thing. But open source is all about collaboration & working together. We wanted to simplify the way new open-source contributors learn & contribute for the first time. + +Reading articles & watching tutorials can help, but what comes better than actually doing the stuff without messing up anything. This project aims at providing guidance & simplifying the way rookies make their first contribution. Remember the more relaxed you are, the better you learn. If you are looking for making your first contribution just follow the simple steps below. We promise you, it will be fun. + +fork this repository + +If you don't have GitHub Desktop on your machine, [install it](https://desktop.github.com/). + +## Fork this repository + +Fork this repo by clicking on the fork button on the top of this page. +This will create of copy of this repository in your account. + +## Clone the repository + +Now clone this repo to your machine. + +Open the GitHub Desktop app and click on the `+` on the top left. + +clone this repository + +If it is not already selected, click on `Clone`. Then choose first-contributions and then click on `Clone first-contributions` + +clone this repository + +Choose the directory on your machine you would like to clone first-contributions into + +clone this repository + +Now you have copied the contents of the first-contributions repository in github to your computer. + +## Create a branch + +Now create a branch by clicking on the branch icon at the top left: + +make a branch + +Name your branch add-your-name. For example, add-crawleya + +Click on `Create new branch` + +name your branch + +## Make necessary changes and commit those changes + +Now open `Contributors.md` file in a text editor and add your name to it, then save the file. + +You can see that there are changes to Contributors.md and they have been added. + +check status + +Now commit those changes: + +Write the message "Add `` to Contributors list" in the *summary* field + +Replace `` with your name + +Click on the button that says `Commit to add-your-name` + +commit your changes + +At the bottom, you can see that the commit has been created. + +commit your changes + +## Push changes to github + +Click the `Publish` button on the top right. + +push your changes + +## Submit your changes for review + +If you go to your repository on github, you'll see `Compare & pull request` button. click on that button. + +create a pull request + +Now submit the pull request. + +submit pull request + +Soon I'll be merging all your changes into the master branch of this project. You will get a notification email once the changes have been merged. + +## Where to go from here? + +Congrats! You just completed the standard _fork -> clone -> edit -> PR_ workflow that you'll encounter often as a contributor! + +Celebrate your contribution and share it with your friends and followers by going to [web app](https://firstcontributions.github.io#social-share). + +You could join our slack team in case you need any help or have any questions. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + + +### [Additional material](../additional-material/git_workflow_senarios/additional-material.md) + + +## Tutorials Using Other Tools +[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools) diff --git a/gui-tool-tutorials/github-desktop-tutorial.md b/gui-tool-tutorials/github-desktop-tutorial.md new file mode 100644 index 00000000000..0d5d7693029 --- /dev/null +++ b/gui-tool-tutorials/github-desktop-tutorial.md @@ -0,0 +1,119 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# First Contributions + +|GitHub Desktop|GitHub Desktop Edition| +|---|---| + +It's hard. It's always hard the first time you do something. Especially when you are collaborating, making mistakes isn't a comfortable thing. But open source is all about collaboration & working together. We wanted to simplify the way new open-source contributors learn & contribute for the first time. + +Reading articles & watching tutorials can help, but what comes better than actually doing the stuff without messing up anything. This project aims at providing guidance & simplifying the way rookies make their first contribution. Remember the more relaxed you are the better you learn. If you are looking for making your first contribution just follow the simple steps below. We promise you, it will be fun. + +If you don't have GitHub Desktop on your machine, [install it](https://desktop.github.com/). + +If you're using a version of GitHub desktop before 1.0, [refer this tutorial](github-desktop-old-version-tutorial.md). + +fork this repository + +## Fork this repository + +Fork this repo by clicking on the fork button on the top right of this page. +This will create a copy of this repository in your account. + +## Clone the repository + +Now clone this repo to your machine. + +IMPORTANT: DO NOT CLONE THE ORIGINAL REPO. Go to your fork and clone it. + +To clone the repo, click on "Clone or Download" and then click on "Open in Desktop". + +clone this repository + +A pop up window will open. Click on "Open GitHubDesktop.exe". + +clone this repository + +After you click on "Open GitHubDesktop.exe" the contents will be downloaded to your computer. + +clone this repository + +Now you have copied the contents of the first-contributions repository in github to your computer. + +## Create a branch + +Now create a branch by clicking on the "Current branch" icon at the top and then click on "New branch": + +make a branch + +Name your branch . For example, "add-james-smith" + +name your branch + +Click on `Create branch` + +## Make necessary changes and commit those changes + +Now, go to history tab and open `Contributors.md` file in a text editor by right clicking and open in text editor. Scroll to the bottom of the page and add your name to it, then save the file. + +Example: If your name is James Smith, It should look like this. + +\[James Smith](https://github.com/jamessmith) + +You can see that there are changes to Contributors.md and they have been added to the Github Desktop. + +check status + +Now commit those changes: + +Write the message "Add `` to Contributors list" in the *summary* field. + +Replace `` with your name. + +Click on the button that says `Commit to add-your-name`. + +commit your changes + +At the bottom, you can see that the commit has been created. + +commit your changes + +## Push changes to github + +Click on File->Options and sign-in to Github.com. Type in your Github username and password. + +log-in to Github + +Click the `Publish` button on the top right. + +push your changes + +## Submit your changes for review + +If you go to your repository on github, you'll see `Compare & pull request` button. click on that button. + +create a pull request + +Now submit the pull request. + +submit pull request + +Soon I'll be merging all your changes into the master branch of this project. You will get a notification email once the changes have been merged. + +## Where to go from here? + +Congrats! You just completed the standard _fork -> clone -> edit -> PR_ workflow that you'll encounter often as a contributor! + +Celebrate your contribution and share it with your friends and followers by going to [web app](https://firstcontributions.github.io#social-share). + +You can join our slack team in case you need any help or have any questions. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + + +### [Additional material](../additional-material/git_workflow_scenarios/additional-material.md) + +## Tutorials Using Other Tools +[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools) diff --git a/gui-tool-tutorials/github-windows-intellij-tutorial.md b/gui-tool-tutorials/github-windows-intellij-tutorial.md new file mode 100644 index 00000000000..fafe63df4f0 --- /dev/null +++ b/gui-tool-tutorials/github-windows-intellij-tutorial.md @@ -0,0 +1,112 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# First Contributions + +| IntelliJ IDEA | IntelliJ IDEA | +| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ | + + +It's hard. It's always hard the first time you do something. Especially when you are collaborating, making mistakes isn't a comfortable thing. But open source is all about collaboration & working together. We wanted to simplify the way new open-source contributors learn & contribute for the first time. + +Reading articles & watching tutorials can help, but what comes better than actually doing the stuff without messing up anything. This project aims at providing guidance & simplifying the way rookies make their first contribution. Remember the more relaxed you are, the better you learn. If you are looking for making your first contribution, just follow the simple steps below. We promise you, it will be fun. + +If you don't have IntelliJ IDEA on your machine, [install it](https://www.jetbrains.com/idea/download/#section=windows). + +**Notice:** This tutorial was made using IntelliJ IDEA (Version 2019.3.2) on a Windows 10 machine. Later in this tutorial we will make use of some keyboard shortcuts. These may differ on other operating systems (macOS/Linux). + +## Fork this repository + +fork this repository + +Fork this repo by clicking on the fork button on the top right of this page. This will create a copy of this repository in your GitHub account. + +GitHub keeps track of the relationship between your repo and the one you have forked it from. You can think of your repo as a working copy. + +Most top-level GitHub Repos (i.e. ones not forked from any other repo) have a small core team of people who can directly commit changes. All other contributors must fork the repo and make changes in the fork, then create a Pull Request to request to merge back their changes into the top-level repo. If the top-level repo administrator approves the changes they will be merged, and you will gain instant fame and fortune! More on how to do that later. + +## Clone your repository + +clone this repository + +The next step is to clone your repo down to your machine so you can begin making changes. IntelliJ IDEA needs the URL of your repo, so click the "clone" button and then click the "copy to clipboard" icon. + +**CAREFUL:** One mistake that new contributors often make is to clone the repo you forked _from_ rather than cloning your repo. Check your browser's address bar and make sure you are cloning your repo. + +Now open up IntelliJ IDEA. + +IntelliJ IDEA allows you to check out (in Git terms clone) an existing repository and create a new project based on the data you've downloaded. + +From the main menu, choose VCS | Get from Version Control, or, if no project is currently opened, click Get from Version Control on the Welcome screen. + +In the Get from Version Control dialog, specify the URL of the remote repository you want to clone (you can click Test to make sure that connection to the remote can be established) or select one of the VCS hosting services on the left. If you are already logged in to the selected hosting service, completion will suggest the list of available repositories that you can clone. + +Click Clone. If you want to create an IntelliJ IDEA project based on the sources you have cloned, click Yes in the confirmation dialog. Git root mapping will be automatically set to the project root directory. + +If your project contains submodules, they will also be cloned and automatically registered as project roots. + +**Important**: Make sure it is the forked repository and not the original one, otherwise it won't work. + +## Create a branch + +In Git, branching is a powerful mechanism that allows you to diverge from the main development line, for example, when you need to work on a feature or freeze a certain state of a codebase for a release, and so on. + +In IntelliJ IDEA, all operations with branches are performed in the Git Branches popup. To invoke it, click the Git widget in the Status bar or press Ctrl+Shift+`. + +The name of the branch that is currently checked out is displayed in the Git widget in the Status bar. + +In the Branches popup, choose New Branch. + +In the dialog that opens, specify the branch name, and make sure the Checkout branch option is selected if you want to switch to that branch. + +The new branch will start from the current HEAD. If you want to start a branch from a previous commit instead of the current branch HEAD, select this commit in the Log tab of the Version Control tool window Alt+9 and choose New Branch from the context menu. + +## Make necessary changes + +Open `Contributors.md` and add your name anywhere in the file. This file contains GFM (GitHub Flavored Markdown) which is a proprietary flavor of the markdown syntax. + +Copy one of the other contributors' lines and modify it with your name to make sure you get the syntax right - it can be picky. + +## Commit & Push changes to GitHub + +Select the files you want to commit or an entire changelist in the Local Changes tab of the Version Control tool window Alt+9 and press Ctrl+K or click Commit Commit button on the toolbar. + +The Commit Changes dialog that opens lists all files that have been modified since the last commit, as well as all newly added unversioned files. + +Enter a meaningful commit message. + +You can click Commit Message history Commit Message history Ctrl+M to choose from the list of recent commit messages. + +You can also edit the commit message later before you've pushed the commit. + +Press Ctrl+Shift+K or choose VCS | Git | Push from the main menu. The Push Commits dialog opens showing all Git repositories (for multi-repository projects) and listing all commits made in the current branch in each repository since the last push. + +## Submit your changes for review + +At this point you have completed your change but it still only resides in your repo. This step will show you how to submit a request to the administrator of the top-level repo to merge your change. + +In your repo on GitHub you'll see the `Compare & pull request` button next to the new branch notification. Click on that button. + +create a pull request + +Now submit the pull request. + +submit pull request + +Soon I'll be merging all your changes into the master branch of this project. You will get a notification email once the changes have been merged. + +## Where to go from here? + +Congrats! You have just completed the standard _fork -> clone -> edit -> PR_ workflow that you'll encounter often as a contributor! + +Celebrate your contribution and share it with your friends and followers by going to [web app](https://firstcontributions.github.io#social-share). + +You can join our slack team in case you need any help or have any questions. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + + +### [Additional material](../additional-material/git_workflow_scenarios/additional-material.md) + +## Tutorials Using Other Tools +[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools) diff --git a/gui-tool-tutorials/github-windows-vs-code-tutorial.md b/gui-tool-tutorials/github-windows-vs-code-tutorial.md new file mode 100644 index 00000000000..aabf88be545 --- /dev/null +++ b/gui-tool-tutorials/github-windows-vs-code-tutorial.md @@ -0,0 +1,118 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# First Contributions + +| Visual Studio Code | Visual Studio Code | +| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ | + + +It's hard. It's always hard the first time you do something. Especially when you are collaborating, making mistakes isn't a comfortable thing. But open source is all about collaboration & working together. We wanted to simplify the way new open-source contributors learn & contribute for the first time. + +Reading articles & watching tutorials can help, but what comes better than actually doing the stuff without messing up anything. This project aims at providing guidance & simplifying the way rookies make their first contribution. Remember the more relaxed you are, the better you learn. If you are looking for making your first contribution, just follow the simple steps below. We promise you, it will be fun. + +If you don't have Visual Studio Code on your machine, [install it](https://code.visualstudio.com/download). + +**Notice:** This tutorial was made using Visual Studio Code (Version 1.27.2) on a Windows 10 machine. Later in this tutorial we will make use of some keyboard shortcuts. These may differ on other operating systems (macOS/Linux) as well as keyboard language (UK, DE, etc). You can go through your list of shortcuts by searching "shortcut" in the Command Palette. + +## Fork this repository + +fork this repository + +Fork this repo by clicking on the fork button on the top right of this page. This will create a copy of this repository in your GitHub account. + +GitHub keeps track of the relationship between your repo and the one you have forked it from. You can think of your repo as a working copy. + +Most top-level GitHub repos (i.e. ones not forked from any other repo) have a small core team of people who can directly commit changes. All other contributors must fork the repo and make changes in the fork, then create a Pull Request to ask for their changes to be merged back into the top-level repo. If the top-level repo administrator likes the changes they will be merged and you will gain instant fame and fortune! More on how to do that later. + +## Clone your repository + +clone this repository + +The next step is to clone your repo down to your machine so you can begin making changes. VS Code needs the URL of your repo, so click the code button and then click the "copy to clipboard" icon. + +**CAREFUL:** One mistake that new contributors often make is to clone the repo you forked _from_ rather than cloning your repo. Check your browser's address bar and make sure you are cloning your repo. + +Now open up Visual Studio Code. The welcome page of VS Code will pop up. From there press `F1` to open up the bar shown below. Notice that there is already a `>` (greater than) sign in the text field. You can also get to the input prompt by pressing `CTRL-P` and then type the `>` character. + +Clone Popup (Command Popup) + +You may notice that there are already some obscure commands listed below. Those are my recently used commands. So just don't care about them. + +Clone repo + +Now type in `git clone`, only `git` or `clone` (it works like a search). +Select the Entry `Git: Clone` and press `Enter` + +Paste Repository URL in + +Paste the URL of your repository and press `Enter`. This will open up a File Explorer where you can then choose where the Git repository should be stored. + +**Important**: Make sure it is the forked repository and not the original one, otherwise it won't work. + +Status popup + +You should see a status popup on the bottom right of Visual Studio Code. After it has finished, you can open up the cloned repository (now a folder on your machine) using the buttons in the dialog. + +## Create a branch + +Open up the command palette again by pressing `F1`. Type in `branch` and select the `create branch` command from there. In the next step type in the name of your new branch, for example `add-david-kroell`. Press enter and the branch will be created. The branch is also already checked out. [What does checkout mean?](https://www.git-scm.com/docs/git-checkout) + +Branches Command Palette + +## Make necessary changes + +Open `Contributors.md` and add your name anywhere in the file. This file contains GFM (GitHub Flavored Markdown) which is a proprietary flavor of the markdown syntax. + +Copy one of the other contributors' lines and modify it with your name to make sure you get the syntax right - it can be picky. + +Add your name + +## Commit & Push changes to GitHub + +On the left side of VS Code is a menu with 5 icons displayed. Select the version control/Source Control icon. +(Shortcut : Ctrl + Shift + G) + +Commit changes + +The file explorer displays all files which were changed after the last commit. By hovering the files and clicking the `+` (plus) the files are staged. + +Stashed Files + +Type something in the line on top of the explorer and press the checkmark. The changes are now committed to your local copy. Now the changes have to be pushed back to GitHub. + +Stashed Files + +Use the three-dot icon to open up the menu where you select the `Publish Branch` option. This should open up a dialog to put your GitHub credentials in. + +Stashed Files + +## Submit your changes for review + +At this point you have completed your change but it still only resides in your repo. This step will show you how to submit a request to the administrator of the top-level repo to merge your change. + +In your repo on GitHub you'll see the `Compare & pull request` button next to the new branch notification. Click on that button. + +create a pull request + +Now submit the pull request. + +submit pull request + +Soon I'll be merging all your changes into the master branch of this project. You will get a notification email once the changes have been merged. + +## Where to go from here? + +Congrats! You have just completed the standard _fork -> clone -> edit -> PR_ workflow that you'll encounter often as a contributor! + +Celebrate your contribution and share it with your friends and followers by going to [web app](https://firstcontributions.github.io#social-share). + +You can join our slack team in case you need any help or have any questions. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + + +### [Additional material](../additional-material/git_workflow_scenarios/additional-material.md) + +## Tutorials Using Other Tools +[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools) diff --git a/gui-tool-tutorials/github-windows-vs2017-tutorial.md b/gui-tool-tutorials/github-windows-vs2017-tutorial.md new file mode 100644 index 00000000000..2c6c9104f23 --- /dev/null +++ b/gui-tool-tutorials/github-windows-vs2017-tutorial.md @@ -0,0 +1,140 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# First Contributions + +|Visual Studio 2017|Visual Studio 2017 Edition| +|---|---| + +It's hard. It's always hard the first time you do something. Especially when you are collaborating, making mistakes isn't a comfortable thing. But open source is all about collaboration & working together. We wanted to simplify the way new open-source contributors learn & contribute for the first time. + +Reading articles & watching tutorials can help, but what comes better than actually doing the stuff without messing up anything. This project aims at providing guidance & simplifying the way rookies make their first contribution. Remember the more relaxed you are the better you learn. If you are looking for making your first contribution just follow the simple steps below. We promise you, it will be fun. + +If you don't have Visual Studio 2017 on your machine, [install it](https://www.visualstudio.com/downloads/). + +## Fork this repository + +fork this repository + +Fork this repository by clicking on the fork button on the top of this page. This will create of copy of this repository in your GitHub account. + +GitHub keeps track of the relationship between your repo and the one you forked it from. You can think of your repo as a working copy. + +Most top-level GitHub repos (i.e. ones not forked from any other repo) have a small core team of people who can directly commit changes. All other contributors must fork the repo and make changes in the fork, then create a Pull Request to ask for their changes to be merged back into the top-level repo. If the top-level repo administrator likes the changes they will be merged and you will gain instant fame and fortune! More on how to do that later. + +## Clone your repository + +clone this repository + +The next step is to clone your repo down to your machine so you can begin making changes. Visual Studio needs the URL of your repo, so click the "clone" button and then click the "copy to clipboard" icon. + +**CAREFUL:** One mistake that new contributors often make is to clone the repo you forked *from* rather than cloning your repo. Check your browser's address bar and make sure you are cloning your repo. + +It is now time to jump in to Visual Studio 2017! You will be working in the Team Explorer tab for most of this tutorial. If it is not open by default, click `View > Team Explorer` to open it. + +Team Explorer + +Team Explorer has many views and there are navigation buttons located at the top to help you find the different areas. To clone a repo, you need to be on the Connect view, which should be the default. If you do not see the 'clone' button, click the green plug at the top. + +Click the `Clone` option under **Local Git Repositories** and paste the URL to your repo in the text box. This should be the URL you copied to your clipboard from GitHub previously. + +Click the `Clone` button to initiate the process. + +Clone repo + +When the process is complete you will be moved over to the Solution Explorer tab where you can see the contents of your repo. Yours will look different than the screenshot below because things change! + +Solution Explorer + +## Create a branch + +Click back to the Team Explorer tab and use the main navigation dropdown to open the Branches view. + +Branches view + +You should see the **first-contributions** repo and the default branch, which is called `master`. Right-click on `master` and choose `New Local Branch From...`. + +New branch + +Give your branch a name like `add-`, for example: `add-alonzo-church`. + +Leave the `Checkout branch` box checked and click the `Create Branch` button. + +Create branch + +You should see your new branch in the list. + +See new branch + +## Make necessary changes + +Open `Contributors.md` and add your name to the end of the list. This file contains GFM (GitHub Flavored Markdown) which is a proprietary flavor of the markdown syntax. + +Copy one of the other contributors' lines and modify it with your name to make sure you get the syntax right - it can be picky. + +Add your name + +## Commit & Push changes to GitHub + +Switch back to Team Explorer and navigate to the Changes view. + +Changes + +Enter the information you want to post with your commit and click `Save`. Visual Studio will remember it for future commits. + +Git user information + +**NOTE:** Visual Studio uses a hidden folder called `.vs` to store your personal settings and preferences. The contents of this folder **should not be saved in Git**. +If it has not been ignored already, you may need to tell Git to ignore this folder so it does not send it up to the repo. + +This folder has already been ignored in this repo, so you should not have to perform this step...it is just here for your reference for future projects. + +Ignore vs folder + +Now you should see a list of changed files and a textbox to type a commit comment. Comments should be in brief but thorough. There is nothing worse than reading through commit comments and seeing this: `"I updated some stuff"`. Take a few seconds to outline your commit. Your team will thank you later, and you might even thank yourself! + +Click `Commit All and Push` to perform a local commit and push your changes back up to your repo, all in one step. + +**NOTE:** Commit can be performed separately from Push. We do both here for convenience. Commit logs your changes locally but they will not be reflected in your GitHub repo until you Push. + +Commit and Push + +The first time you Push to GitHub, Visual Studio will ask for your GitHub credentials. They will be cached so you should not see this very often. + +Login + +After the Push operation completes, open your repo in GitHub and you should see a message indicating a recently pushed branch. + +You can view your changes by opening the `Branch: master` dropdown and selecting your new branch. Congratulations, you can share the branch URL with the world to show your progress! + +View pushed branch on GitHub + +## Submit your changes for review + +At this point you have completed your change but it still only resides in your repo. This step will show you how to submit a request to the administrator of the top-level repo to merge your change. + +In your repo on GitHub you'll see the `Compare & pull request` button next to the new branch notification. Click on that button. + +create a pull request + +Now submit the pull request. + +submit pull request + +Soon I'll be merging all your changes into the master branch of this project. You will get a notification email once the changes have been merged. + +## Where to go from here? + +Congrats! You have just completed the standard _fork -> clone -> edit -> PR_ workflow that you'll encounter often as a contributor! + +Celebrate your contribution and share it with your friends and followers by going to [web app](https://firstcontributions.github.io#social-share). + +You can join our slack team in case you need any help or have any questions. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + + +### [Additional material](../additional-material/git_workflow_scenarios/additional-material.md) + +## Tutorials Using Other Tools +[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools) diff --git a/gui-tool-tutorials/gitkraken-tutorial.md b/gui-tool-tutorials/gitkraken-tutorial.md new file mode 100644 index 00000000000..fe362377e1c --- /dev/null +++ b/gui-tool-tutorials/gitkraken-tutorial.md @@ -0,0 +1,123 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# First Contributions + +|GitKraken|GitKraken Edition| +|---|---| + +It's hard. It's always hard, when you do something for the first time. Especially when you are collaborating, making mistakes isn't a comfortable thing. But open source is all about collaboration & working together. We wanted to simplify the way new open-source contributors learn & contribute for the first time. + +Reading articles & watching tutorials can help, but what comes better than actually doing the stuff without messing up anything. This project aims at providing guidance & simplifying the way rookies make their first contribution. Remember the more relaxed you are, the better you learn. If you are looking for making your first contribution just follow the simple steps below. We promise you, it will be fun. + + +## Git Kraken + +Download [GitKraken](https://www.gitkraken.com), Install and open it. + + +You should see the "Welcome to GitKraken" modal dialog - Sign in with GitHub and allow GitKraken access to your GitHub account. + + +login to GitHub + +(optional) Go to File -> Preferences and set your project directory to the root of your local repositories. + + +## Fork this repository + +Fork this repo by clicking on the fork button on the top of this page. +fork this repository +This will create of copy of this repository in your account. + + +## Clone the repository + +In GitKraken, go to File -> Clone Repo. + + +clone this repository + + +Select GitHub.com in the right pane. Under your username, you should see first-contributions. Click that repository and check the full path shown at the bottom of this pane. + +Once you're satisfied with the path, click "Clone the repo!". + + +## Create a branch + +Click the branch button on the toolbar. + +Name your branch "add-your-name", for example: "add-william-sutton" + +name your branch + + +## Make necessary changes and commit those changes + +Now open `Contributors.md` file in a text editor and add your name to it, then save the file. + +If you have the repo open in GitKraken you'll see there are changes. Review and stage those changes by selecting the newest commit marked with "// WIP" and the number of files changed and the type of change. + +edit some file(s) + +Review the files that have been changed and decide what you would like to stage. Staging is important to tell git exactly what file changes you want associated with this commit. + + +stage your changes + + +Once you have a good commit message ("Add to Contributors list" sounds nice and descriptive) and are happy with your changes, you can hit "Stage all changes" to stage everything that is modified or "Stage File" to stage an individual file. + + +clone this repository + + +If you change your mind, you can unstage those changes, or you can discard them all together. +WARNING: As the word discard implies, this is a destructive operation. Do this only if you don't want any change(s) from whatever repository you're in. + +Hit commit. + +Congratulations, you've committed all the changes to your local copy of your branch of your fork of first-contributions. Onward! + + +## Push changes to GitHub + +push your changes + +Click the Push button on the toolbar. + +origin or branch + +Submit changes on the origin branch if you want the changes to reflect in the master branch directly, else select the appropriate branch you want to push. + + +## Submit your changes for review + +If you go to your repository on github, you'll see `Compare & pull request` button. Click on that button. + +create a pull request + +Now submit the pull request. + +submit pull request + +Soon I'll be merging all your changes into the master branch of this project. You will get a notification email once the changes have been merged. + +## Where to go from here? + +Congrats! You have just completed the standard _fork -> clone -> edit -> PR_ workflow that you'll encounter often as a contributor! + +Celebrate your contribution and share it with your friends and followers by going to [web app](https://firstcontributions.github.io/#social-share). + +You could join our slack team in case you need any help or have any questions. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + + +### [Additional material](../additional-material/git_workflow_scenarios/additional-material.md) + + +## Tutorials Using Other Tools +[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools) diff --git a/gui-tool-tutorials/sourcetree-macos-tutorial.md b/gui-tool-tutorials/sourcetree-macos-tutorial.md new file mode 100644 index 00000000000..62b1dd6dd45 --- /dev/null +++ b/gui-tool-tutorials/sourcetree-macos-tutorial.md @@ -0,0 +1,139 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# First Contributions + +|SourceTree|Atlassian Sourcetree| +|---|---| + +It's hard. It's always hard, when you do something for the first time. Especially when you are collaborating, making mistakes isn't a comfortable thing. But open source is all about collaboration & working together. We wanted to simplify the way new open-source contributors learn & contribute for the first time. + +Reading articles & watching tutorials can help, but what comes better than actually doing the stuff without messing up anything. This project aims at providing guidance & simplifying the way rookies make their first contribution. Remember the more relaxed you are, the better you learn. If you are looking for making your first contribution just follow the simple steps below. We promise you, it will be fun. + + +## Sourcetree + +Please note, this tutorial is for MacOS. It is similar with Sourcetree on Windows but some things may look different. + + +Download [Sourcetree](https://www.sourcetreeapp.com), Install and open it. + +You should see the "Sourcetree" modal dialog. + +SourceTree Main + +From here, you want to click on Remote. If this is the first installation, then you likely haven't connected your GitHub account yet. Do so by clicking the "Connect Button". + +SourceTree Connect + +The *Accounts* dialog will appear. Click "Add" in the lower left hand corner. Then select the appropriate settings to add GitHub (or any other account you want) to the client. After you selected your settings for GitHub, click "Connect Account." + +SourceTree Connect Add + +This will open a page in your web browser. Follow the steps given to authorize your account. + +## Fork this repository + +Fork this repo by clicking on the fork button on the top of this page. +fork this repository +This will create of copy of this repository in your account. + + +## Clone the repository + +In Sourcetree, Click on the "Remote" button. This should load all of your GitHub repos which are listed on GitHub. + +clone this repository + +Once you click the "Clone" button, you will be presented with another view to define several different things. + +clone this repository + +1) **Source URL:** This is automatically filled and you don't need to change it. It is the URL from where your GitHub project resides. + +2) **Destination Path:** This is the physical location on your computer where this project will be saved + +3) **Name:** This is a "Bookmark" to how Sourcetree will reference your project. Think of it like a shortcut. + +*Note: Normally the defaults in these fields are fine.* + +**Once you are satisfied, click "Clone"** + +This will bring up the main repo browser for your repository! + +## Create a branch + +Click the branch button on the toolbar. + +Name your branch "add-your-name-to-contribution", for example: "add-sally-to-contribution". + +To do this, click **Branch (1)** which launches the naming dialog. Then **Add your name (2)** as just described. Finally click **Create Branch**. This will create the branch for what you just named. + +name your branch + + +## Make necessary changes and commit those changes + +Now open `Contributors.md` file in a text editor and add your name to it, with your Github URL link, then save the file. + +You should be able to see and review the file that have been changed and decide what you would like to stage. Staging is important to tell git exactly what file changes you want associated with this commit. + +*Note: If you do not see the file's diff, click **Uncommitted Files** at the top of your dialog* + +edit some file(s) + +Next click the **Commit** button on the top left of the dialog. This will show you your staging area. + +Click the *Checkbox* to **add** the file to the staging area. Then enter a commit message. + +*Note: You can also select files (both in the staging and unstaged areas) and add/remove files from the respective areas by using the spacebar* + +stage your changes + + +Once you have added your changes and added a commit message, you can press the **Commit** button to finally make the commit. + +Congratulations, you've committed all the changes to your local copy of your branch of your fork of first-contributions. Onward! + + +## Push changes to GitHub + +Now you are ready to push your changes to github. This will be pushing it to your own, forked, copy of the project. Follow the steps to push your branch up. First, click **Push (1)**, this will show the remote/push dialog. **Click (2)** the checkbox of your branch you want to push. Select **OK (3)** and this will push your commit up to Github. + +origin or branch + +## Submit your changes for review + +If you go to your repository on github, you'll see `Compare & pull request` button. Click on that button. + +create a pull request + +Now submit the pull request. + +submit pull request + +Soon I'll be merging all your changes into the master branch of this project. You will get a notification email once the changes have been merged. + +## Where to go from here? + +Congrats! You have just completed the standard _fork -> clone -> edit -> PR_ workflow that you'll encounter often as a contributor! + +Celebrate your contribution and share it with your friends and followers by going to [web app](https://firstcontributions.github.io/#social-share). + +You could join our slack team in case you need any help or have any questions. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + + +### [Additional material](../additional-material/git_workflow_scenarios/additional-material.md) + + +## Tutorials Using Other Tools +[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools) diff --git a/gui-tool-tutorials/sublime-merge-tutorial.md b/gui-tool-tutorials/sublime-merge-tutorial.md new file mode 100644 index 00000000000..38949b2fce3 --- /dev/null +++ b/gui-tool-tutorials/sublime-merge-tutorial.md @@ -0,0 +1,121 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# First Contributions + +|Sublime Merge|Sublime Merge Git Client| +|---|---| + +It's hard. It's always hard, when you do something for the first time. Especially when you are collaborating or trying out something new, making mistakes isn't a comfortable thing. But open source is all about collaboration & working together. We wanted to simplify the way new open-source contributors learn & contribute for the first time. + +Reading articles & watching tutorials can help, but what comes better than actually doing the stuff without messing up anything. This project aims at providing guidance & simplifying the way rookies make their first contribution. Remember the more relaxed you are, the better you learn. If you are looking for making your first contribution just follow the simple steps below. We promise you, it will be fun. + + +## Sublime Merge + +Download [Sublime Merge](https://www.sublimemerge.com/), Install and open it. + +## Fork this repository + +Fork this repo by clicking on the fork button on the top of this page. +fork this repository +This will create of copy of this repository in your account. + +
+
+
+
+ +## Clone the repository + +clone this repository + +In Sublime Merge, go to File -> Clone Repository. + + +clone this repository + +The next step is to clone your repo down to your machine so you can begin making changes. Sublime Merge needs the URL of your repo, so click the "clone" button and then click the "copy to clipboard" icon. + +**CAREFUL:** One mistake that new contributors often make is to clone the repo you forked _from_ rather than cloning your repo. Check your browser's address bar and make sure you are cloning your repo. + + +Enter the URL of the repo in Sublime Merge, give it a repository name (or leave it blank) and set your directory where to save the repository. + +Once you're satisfied with the path, click "Clone". + + +## Create a branch + +Right click Branches -> Create Branch +or +Navigate to Repository -> Create Branch + +Name your branch "add-your-name", for example: "add-william-sutton" + +name your branch + + +## Make necessary changes and commit those changes + +Now open `Contributors.md` file in a text editor and add your name to it, then save the file. + +If you have the repo open in Sublime Merge you'll see there are changes. +Select the newest commit at the top, named "x unstaged files" +Review the files that have been changed and decide what you would like to stage. +Give the commit a commit message ("Add to Contributors list" sounds nice and descriptive). +When you are happy with your changes stage those changes by staging them file by file or selecting "stage all". Staging is important to tell git exactly what file changes you want associated with this commit. + +stage your changes + +If you change your mind, you can unstage those changes, or you can discard them all together. +WARNING: As the word discard implies, this is a destructive operation. Do this only if you don't want any change(s) from whatever repository you're in. + +Hit commit and enter your username and email address and press Update. + +Hit commit again. + +Congratulations, you've committed all the changes to your local copy of your branch of your fork of first-contributions. Onward! + + +## Push changes to GitHub + +Navigate to Repository -> Push +or hit the small arrow in upward direction in the right hand corner. + +login + +Login to your Github Account with your username and password + +Submit changes on the origin branch if you want the changes to reflect in the master branch directly, else select the appropriate branch you want to push. + + +## Submit your changes for review + +If you go to your repository on github, you'll see `Compare & pull request` button. Click on that button. + +create a pull request + +Now submit the pull request. + +submit pull request + +Soon I'll be merging all your changes into the master branch of this project. You will get a notification email once the changes have been merged. + +## Where to go from here? + +Congrats! You have just completed the standard _fork -> clone -> edit -> PR_ workflow that you'll encounter often as a contributor! + +Celebrate your contribution and share it with your friends and followers by going to [web app](https://firstcontributions.github.io#social-share). + +You could join our slack team in case you need any help or have any questions. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + + +### [Additional material](../additional-material/git_workflow_senarios/additional-material.md) + + +## Tutorials Using Other Tools +[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools) diff --git a/gui-tool-tutorials/translations/github-desktop-tutorial.ng_yr.md b/gui-tool-tutorials/translations/github-desktop-tutorial.ng_yr.md new file mode 100644 index 00000000000..6c50777c803 --- /dev/null +++ b/gui-tool-tutorials/translations/github-desktop-tutorial.ng_yr.md @@ -0,0 +1,106 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Awọn ẹbun akọkọ + +|GitHub Desktop|GitHub Ojú-iṣẹ Edition| +|---|---| + +O le. O jẹ lile nigbagbogbo ni igba akọkọ ti o ṣe nkan. Paapa nigbati o ba n ṣe ifowosowopo, ṣiṣe awọn aṣiṣe kii ṣe nkan ti o ni itunu. Ṣugbọn orisun ṣiṣi jẹ gbogbo nipa ifowosowopo & ṣiṣẹ papọ. A fẹ lati jẹ ki o rọrun ni ọna ti awọn oluranlọwọ orisun-ìmọ tuntun kọ ẹkọ & ṣe alabapin fun igba akọkọ. + +Awọn nkan kika & wiwo awọn olukọni le ṣe iranlọwọ, ṣugbọn kini o dara julọ ju ṣiṣe nkan naa ni gangan laisi dabaru ohunkohun. Ise agbese yii ni ero lati pese itọnisọna & simplifying ọna ti awọn rookies ṣe ṣe ilowosi akọkọ wọn. Ranti diẹ sii ni ihuwasi ti o dara julọ ti o kọ ẹkọ. Ti o ba n wa ṣiṣe ilowosi akọkọ rẹ kan tẹle awọn igbesẹ ti o rọrun ni isalẹ. A ṣe ileri fun ọ, yoo jẹ igbadun. + +Ti o ko ba ni Ojú-iṣẹ GitHub lori ẹrọ rẹ, [fi sii] (https://desktop.github.com/). + +Ti o ba n lo ẹya ti tabili GitHub ṣaaju 1.0, [tọkasi ikẹkọ yii](github-desktop-old-version-tutorial.md). orita ibi ipamọ yii + +## Orita ibi ipamọ yii + +Fork repo yii nipa tite lori bọtini orita ni apa ọtun oke ti oju-iwe yii. Eyi yoo ṣẹda ẹda ibi ipamọ yii sinu akọọlẹ rẹ. + +## Ti ẹda ibi ipamọ naa + +Bayi clone repo yii si ẹrọ rẹ. PATAKI: MAA ṢE TI AWỌN REPO ORIGINAL. Lọ si orita rẹ ki o ṣe oniye rẹ. Lati ṣe oniye repo, tẹ lori "Clone tabi Download" ati lẹhinna tẹ "Ṣii ni Ojú-iṣẹ". + +clone this repository + +Ferese agbejade yoo ṣii. Tẹ "Ṣii GitHubDesktop.exe". + +clone this repository + +Lẹhin ti o tẹ “Ṣii GitHubDesktop.exe” awọn akoonu naa yoo ṣe igbasilẹ si kọnputa rẹ. + +clone this repository + +Bayi o ti daakọ awọn akoonu ti ibi ipamọ awọn ifunni akọkọ ni github si kọnputa rẹ. + +## Ṣẹda ẹka kan + +Bayi ṣẹda ẹka kan nipa tite lori aami “Ẹka lọwọlọwọ” ni oke ati lẹhinna tẹ “Ẹka Tuntun”: + +name your branch + +Tẹ 'Ṣẹda ẹka' + +## Ṣe awọn ayipada to ṣe pataki ki o ṣe awọn ayipada yẹn + +Bayi ṣii faili `Contributors.md` ni olootu ọrọ, yi lọ si isalẹ ti oju-iwe naa ki o fi orukọ rẹ kun, lẹhinna fi faili naa pamọ. + +Apeere: Ti orukọ rẹ ba jẹ James Smith, O yẹ ki o dabi eleyi. \[James Smith](https://github.com/jamessmith) O le rii pe awọn ayipada wa si Contributors.md ati pe wọn ti ṣafikun si Ojú-iṣẹ Github. + +check status + +Bayi ṣe awọn ayipada wọnyi: + +Kọ ifiranṣẹ naa "Ṣafikun `` si atokọ Awọn oluranlọwọ” ni aaye * akopọ *. + +Ropo `` pẹlu orukọ rẹ. + +Tẹ bọtini ti o sọ 'Ṣe lati fi-orukọ-rẹ'. + +commit your changes + +Ni isalẹ, o le rii pe a ti ṣẹda ifaramọ naa. + + ṣe awọn ayipada rẹ + +## Titari awọn ayipada si github + + Tẹ Faili-> Awọn aṣayan ati wọle si Github.com. Tẹ orukọ olumulo Github ati ọrọ igbaniwọle sii. + + +wọle si Github + +Tẹ bọtini 'Tẹjade' ni apa ọtun oke. + +Titari awọn ayipada rẹ + +## Firanṣẹ awọn ayipada rẹ fun atunyẹwo + +Ti o ba lọ si ibi ipamọ rẹ lori github, iwọ yoo rii bọtini 'Afiwe & fa ìbéèrè'. tẹ lori wipe bọtini. + +ṣẹda ibeere fifa + +Bayi fi ibeere fa silẹ. + +fi ìbéèrè fa + +Laipẹ Emi yoo dapọ gbogbo awọn ayipada rẹ si ẹka ọga ti iṣẹ akanṣe yii. Iwọ yoo gba imeeli iwifunni ni kete ti awọn ayipada ba ti dapọ. + +## Nibo ni lati lọ lati ibi? + +Oriire! O kan pari boṣewa _fork -> oniye -> edit -> PR_ iṣan-iṣẹ ti iwọ yoo ba pade nigbagbogbo bi oluranlọwọ! + +Ṣe ayẹyẹ ilowosi rẹ ki o pin pẹlu awọn ọrẹ ati awọn ọmọlẹyin rẹ nipa lilọ si [ohun elo wẹẹbu](https://firstcontributions.github.io#social-share). + +O le darapọ mọ ẹgbẹ alailẹṣẹ wa ni ọran ti o nilo iranlọwọ eyikeyi tabi ni awọn ibeere eyikeyi. + [Darapọ mọ ẹgbẹ alailẹṣẹ](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYVk) + + +### [Awọn ohun elo afikun](../additional-material/git_workflow_scenarios/additional-material.md) + +## Awọn olukọni Lilo Awọn irinṣẹ miiran +[Pada si oju-iwe akọkọ](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools) diff --git a/gui-tool-tutorials/translations/github-desktop-tutorial.pt_br.md b/gui-tool-tutorials/translations/github-desktop-tutorial.pt_br.md new file mode 100644 index 00000000000..2aa68ecfa7d --- /dev/null +++ b/gui-tool-tutorials/translations/github-desktop-tutorial.pt_br.md @@ -0,0 +1,119 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# First Contributions + +|GitHub Desktop|GitHub Desktop Edition| +|---|---| + +É difícil. É sempre difícil fazer algo pela primeira vez. Especialmente quando se está colaborando, cometer erros não é algo agradável. Mas *open source* (código aberto) se trata de colaboração e de trabalharmos juntos. Queremos simplificar a forma com que novos colaboradores *open source* aprendem e contribuem pela primeira vez. + +Ler artigos e ver tutoriais pode ajudar, mas o que é melhor do que realmente pôr a mão na massa em um ambiente prático? Este projeto visa guiar e simplificar a forma com que os novatos fazem a sua primeira contribuição. Se quiser fazer a sua primeira contribuição, siga os passos abaixo. + +Se você nao tem o Github desktop na sua máquina, [instale aqui](https://desktop.github.com/). + +Se você está usando uma versão do Github desktop antes da 1.0, [consulte este tutorial](github-desktop-old-version-tutorial.md). + +fork este repositório + +## Fork este repositório + +Fork este repositório clicando no botão fork na parte superior direita dessa página. +Isso vai criar uma cópia desse repositório na sua conta. + +## Clone este repositório + +Agora clone esse repositório na sua máquina. + +IMPORTANTE: NÃO CLONE O REPOSITÓRIO ORIGINAL. Vá para o seu fork e clone. + +Para clonar esse repositório, clique em "Clone or Download" e então clique em "Open in Desktop". + +clone este repositório + +Uma janela pop up vai aparecer. Clique em "Open GitHubDesktop.exe". + +clone este repositório + +Depois de clicar em "Open GitHubDesktop.exe" os arquivos serão baixados para o seu computador. + +clone este repositório + +Agora você copiou os arquivos do repositório first-contributions no github para o seu computador. + +## Criando uma branch (ramo) + +Agora crie uma branch clicando na aba "Current branch" que fica no topo, depois clique em "New branch": + +criar uma branch + +Nomeie sua branch como . Por exemplo, "add-james-smith" + +nomeie sua branch + +Clique em `Create branch` + +## Faça as mudanças necessárias e commit essas mudanças + +Agora abra o arquivo `Contributors.md` em um editor de texto, vá para o final do arquivo e adicione seu nome, depois salve o arquivo. + +Exemplo: Se o seu nome for James Smith, Deve ficar parecido com isso. + +\[James Smith](https://github.com/jamessmith) + +Você pode ver as alterações feitas em Contributors.md no Github Desktop. + +checar mudanças + +Agora faça commit dessas alterações: + +Escreva a mensagem "Add `` to Contributors list" no campo *sumary* + +Substitua `` pelo seu nome. + +Clique no botão que diz `Commit to add-your-name`. + +commit suas alterações + +Na parte inferior, você pode ver que o commit foi criado com sucesso. + +commit suas alterações + +## Faça o push das mudanças no github + +Clique em File -> Options e depois em sign-in to Github.com. Digite seu username e senha do Github. + +log-in no Github + +Clique no botão `Publish` na parte superior direita. + +push suas alterações + +## Envie suas alterações para review + +Se você for até seu repositório no github, verá o botão `Compare & pull request`. Clique nesse botão + +criando um pull request + +Agora envie o pull request. + +enviando o pull request + +Em breve estarei mesclando todas as suas alterações na branch Master do projeto. Você vai receber um email de notificação assim que as alterações forem integradas. + +## Qual o próximo passo? + +Parabéns! Você acabou de completar o fluxo _fork -> clone -> edit -> PR_ que encontrará diversas vezes como contribuidor! + +Comemore sua contribuição e compartilhe com seus amigos e seguidores acessando o [web app](https://firstcontributions.github.io#social-share). + +Você pode entrar na nossa equipe no Slack caso precise de alguma ajuda ou tenha alguma dúvida. [Entre no Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + + +### [Material adicional](../additional-material/git_workflow_senarios/additional-material.md) + +## Tutoriais usando outras ferramentas +[Voltar a página principal](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools) diff --git a/gui-tool-tutorials/translations/github-windows-intellij-tutorial.pt_br.md b/gui-tool-tutorials/translations/github-windows-intellij-tutorial.pt_br.md new file mode 100644 index 00000000000..1d7c61d1e59 --- /dev/null +++ b/gui-tool-tutorials/translations/github-windows-intellij-tutorial.pt_br.md @@ -0,0 +1,126 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Primeiras Contribuições + +| IntelliJ IDEA | IntelliJ IDEA | +| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ | + + +É difícil, sempre é difícil quando fazemos alguma coisa pela primeira vez. Especialmente quando você está colaborando, cometendo erros, não é nada confortável. No entanto, o open source é totalmente sobre colaboração & trabalho em equipe. Por isso, nós queremos simplificar a maneira como os novos colaboradores de código aberto aprendem & contribuem pela primeira vez. + +Ler artigos & assistir a tutoriais até podem ajudar, mas o que é melhor do que fazer as coisas sem bagunçar nada. Este projeto tem como objetivo orientar & simplificar a forma como os iniciantes fazem a sua primeira contribuição. Lembre-se que você aprende melhor quando está relaxado. Se você deseja fazer sua primeira contribuição, basta seguir os passos abaixo. Nós prometemos a você que será divertido! + +Se você ainda não tem o IntelliJ IDEA no seu computador, [instale-o](https://www.jetbrains.com/idea/download/#section=windows) + +**Observação:** Este tutorial foi feito usando o IntelliJ IDEA (versão 2019.3.2) em um computador rodando Windows 10. Posteriormente neste tutorial, faremos uso de algumas teclas de atalho, que podem ser diferentes em outros sistemas operacionais (macOS / Linux). + + +## Faça o Fork deste repositório + +fork this repository + +Faça um *fork* deste repositório clicando no botão *fork* (bifurcar) no canto superior direito desta página. Isso criará uma cópia deste repositório em sua conta do GitHub. + +O GitHub rastreia a relação entre seu repositório e o original, o qual você fez o *fork*. Você pode pensar em seu repositório como uma cópia de trabalho. + +Muitos dos repositórios matrizes do GitHub (ou seja, aqueles que não são *Fork* de nenhum outro repositório) tem um pequeno grupo de pessoas que podem fazer commits de modificações diretamente. Todos os outros contribuidores devem fazer um *for* do repositório e fazer alterações no *fork*, em seguida, devem criar um Pull Request para solicitar um *Merge* (mesclagem) das modificações feitas no repositório original. + + +## Clone seu Repositório + +clone this repository + +O próximo passo será clonar seu repositório em sua máquina para que você possa modificá-lo. Visual Studio precisa da URL do seu repositório, portanto clique no botão "clone" e então clique no ícone "copy to clipboard". + +**CUIDADO**: Um erro que os novatos costumam cometer é clonar o repo do qual você fez o fork, em vez de clonar seu repo. Verifique a barra de endereços do seu navegador e certifique-se de que você está clonando o seu repositório. + +Agora abra o IntelliJ IDEA. + +O IntelliJ IDEA permite que você fassa um check out (em termos do Git clone) de um repositório existente e crie um novo projeto com base nos dados que você baixou. + +No menu principal, escolha VCS | Get from Version Control ou, se nenhum projeto estiver aberto no momento, clique em Get from Version Control na tela inicial. + +Na caixa de diálogo Get from Version Control dialog, especifique a URL do repositório remoto que deseja clonar (você pode clicar em Test para certificar-se de que a conexão com o repositório remoto pode ser estabelecida) ou selecione um dos serviços de hospedagem VCS à esquerda. Se você já estiver conectado ao serviço de hospedagem selecionado, a completion irá sugerir a lista de repositórios disponíveis que você pode clonar. + +Clique em Clone. Se quiser criar um projeto IntelliJ IDEA com base nas fontes que você clonou, clique em Sim na caixa de diálogo de confirmação. O mapeamento de raiz do Git será automaticamente definido para o diretório raiz do projeto. + +Se o seu projeto tiver submodelos, eles também serão clonados e automaticamente registrados como raízes do projeto. + +**Importante**: certifique-se de que é o repositório é o fork e não o original, caso contrário, o procedimento não funcionará. + + +## Crie um branch + +No Git, o processo de branching (ramificação) é um mecanismo poderoso que permite divergir da linha principal de desenvolvimento, por exemplo, quando você precisa trabalhar em um recurso ou congelar um determinado estado de uma base de código para um release e assim por diante. + +No IntelliJ IDEA, todas as operações com branches são realizadas no pop-up Git Branches. Para ativá-lo, clique no widget Git na barra de status ou pressione Ctrl + Shift + `. + +O nome do branch atual é exibido no widget do Git na barra de status. + +No pop-up branch, escolha Novo branch. + +Na caixa de diálogo que é aberta, especifique o nome do branch e certifique-se de que a opção Checkout branch esteja selecionada se você quiser alternar para esse branch. + +A nova ramificação começará a partir do HEAD atual. Se você deseja iniciar um branch de um commit anterior ao invés do branch atual HEAD, selecione este commit na aba Log da janela da ferramenta de Controle de Versão Alt + 9 e escolha New Branch no menu de contexto. + + +## Faça as alterações necessárias +Abra ``Contributors.md`` e adicione seu nome em qualquer lugar do arquivo. Este arquivo contém GFM (GitHub Flavored Markdown), que é um tipo proprietário da sintaxe de [markdown](https://pt.wikipedia.org/wiki/Markdown). + +Copie uma das linhas de outros contribuidores e modifique-a com seu nome para ter certeza que você obteve a sintaxe correta. + + +## Commit & Push modificações para o GitHub + +Selecione os arquivos que deseja commitar ou uma lista de alterações inteira na guia Local Changes da janela da ferramenta de controle de versão Alt + 9 e pressione Ctrl + K ou clique no botão Commit na barra de ferramentas. + +A caixa de diálogo Commit Changes abrira e listara todos os arquivos que foram modificados desde o último commit, bem como todos os arquivos não versionados recém-adicionados. + +Insira uma mensagem de commit que faça sentido. + +Você pode clicar em Commit Message history (Confirmar histórico de mensagens) Ctrl + M para escolher na lista de mensagens de commits recentes. + +Você também pode editar a mensagem de commit mais tarde, antes de enviar o commit. + +Pressione Ctrl + Shift + K ou escolha VCS | Git | Push from the main menu. A caixa de diálogo Push Commits é aberta, mostrando todos os repositórios Git (para projetos de vários repositórios) e listando todos os commits feitos no branch atual em cada repositório desde o último push. + + +## Envie suas alterações para revisão + +Neste ponto, você concluiu a alteração, mas ela ainda está apenas no seu repo. Esta etapa mostrará como enviar uma solicitação ao administrador do repo matriz para mesclar sua alteração. + +Em seu repo no GitHub, você verá o botão `Compare & pull request` ao lado da notificação do novo branch, clique nesse botão. + + +create a pull request + +Agora submeta o pull request. + +submit pull request + +Em breve estarei mesclando todas as suas alterações no branch master deste projeto. Você receberá um e-mail de notificação assim que as alterações forem integradas. + +## Para onde ir agora? + +Parabéns! Você acabou de completar o padrão _fork -> clone -> edit -> PR_ workflow que você encontrará frequentemente como um contribuidor! + +Comemore sua contribuição e compartilhe-a com seus amigos e seguidores acessando o [web app](https://roshanjossey.github.io/first-contributions/#social-share). + +Você pode se juntar a nossa equipe slack caso precise de alguma ajuda ou tenha alguma dúvida. [Junte-se ao time slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Agora vamos começar a contribuir para outros projetos, compilamos uma lista de projetos com questões fáceis para você começar. [Confira a lista de projetos no web app](https://roshanjossey.github.io/first-contributions/#project-list). + + + + +### [Material Adicional](../../additional-material/translations/Portuguese/additional-material.pt_br.md). + +## Tutoriais usando outras ferramentas +[Voltar a página principal](https://github.com/firstcontributions/first-contributions/blob/master/translations/README.pt_br.md) + +## Autopromoção + +Se você gostou deste projeto, de star no GitHub. Se você gostou dessa tradução me siga no GitHub [Vitor Matias](https://github.com/VitorCMatias). diff --git a/gui-tool-tutorials/translations/github-windows-vs-code-tutorial-hi.md b/gui-tool-tutorials/translations/github-windows-vs-code-tutorial-hi.md new file mode 100644 index 00000000000..ea1241d7bc8 --- /dev/null +++ b/gui-tool-tutorials/translations/github-windows-vs-code-tutorial-hi.md @@ -0,0 +1,116 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/CodeWithAjaySaini) + + +# First Contributions + +| Visual Studio Code | Visual Studio Code | +| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ | + + +यह मुश्किल है। पहली बार जब आप कुछ करते हैं तो यह हमेशा कठिन होता है। खासकर जब आप सहयोग कर रहे हों, तो गलतियाँ करना सहज बात नहीं है। लेकिन ओपन सोर्स सहयोग और एक साथ काम करने के बारे में है। हम नए ओपन-सोर्स योगदानकर्ताओं के पहली बार सीखने और योगदान करने के तरीके को सरल बनाना चाहते थे। + +लेख पढ़ना और ट्यूटोरियल देखना मदद कर सकता है, लेकिन वास्तव में कुछ भी गड़बड़ किए बिना सामान करने से बेहतर क्या हो सकता है। इस परियोजना का उद्देश्य मार्गदर्शन प्रदान करना और धोखेबाज़ों द्वारा अपना पहला योगदान देने के तरीके को सरल बनाना है। याद रखें कि आप जितने अधिक आराम से होंगे, आप उतना ही बेहतर सीखेंगे। यदि आप अपना पहला योगदान करना चाहते हैं, तो बस नीचे दिए गए सरल चरणों का पालन करें। हम आपसे वादा करते हैं, यह मजेदार होगा। + +यदि आपकी मशीन पर विजुअल स्टूडियो कोड नहीं है, [install it](https://code.visualstudio.com/download). + +**सूचना:** यह ट्यूटोरियल विंडोज 10 मशीन पर विजुअल स्टूडियो कोड (संस्करण 1.27.2) का उपयोग करके बनाया गया था। बाद में इस ट्यूटोरियल में हम कुछ कीबोर्ड शॉर्टकट का उपयोग करेंगे। ये अन्य ऑपरेटिंग सिस्टम (मैकोज़/लिनक्स) के साथ-साथ कीबोर्ड भाषा (यूके, डीई, आदि) पर भिन्न हो सकते हैं। आप कमांड पैलेट में "शॉर्टकट" खोजकर अपने शॉर्टकट की सूची देख सकते हैं। + +## इस भंडार को फोर्क करें + +fork this repository + +इस रेपो को फोर्क करने के लिए इस पेज के ऊपर दाईं ओर फोर्क बटन पर क्लिक करें। यह आपके GitHub खाते में इस रिपॉजिटरी की एक प्रति बनाएगा। + +गिटहब आपके रेपो और उस रेपो के बीच संबंधों का ट्रैक रखता है जिसे आपने इसे फोर्क किया है। आप अपने रेपो को एक कार्यशील प्रति के रूप में सोच सकते हैं। + +अधिकांश शीर्ष-स्तरीय गिटहब रेपो (यानी किसी अन्य रेपो से फोर्क नहीं किए गए) में लोगों की एक छोटी सी कोर टीम होती है जो सीधे बदलाव कर सकती है। अन्य सभी योगदानकर्ताओं को रेपो को फोर्क करना होगा और फोर्क में परिवर्तन करना होगा, फिर एक पुल अनुरोध बनाना होगा ताकि उनके परिवर्तनों को शीर्ष-स्तरीय रेपो में वापस विलय करने के लिए कहा जा सके। यदि शीर्ष-स्तरीय रेपो व्यवस्थापक परिवर्तनों को पसंद करता है तो उन्हें विलय कर दिया जाएगा और आपको तुरंत प्रसिद्धि और भाग्य प्राप्त होगा! इसे बाद में कैसे करें, इसके बारे में अधिक। + +## अपने भंडार को क्लोन करें + +clone this repository + +अगला कदम अपने रेपो को अपनी मशीन पर क्लोन करना है ताकि आप बदलाव करना शुरू कर सकें। वीएस कोड को आपके रेपो के यूआरएल की जरूरत है, इसलिए "क्लोन" बटन पर क्लिक करें और फिर "क्लिपबोर्ड पर कॉपी करें" आइकन पर क्लिक करें। + +**सावधान:** एक गलती जो नए योगदानकर्ता अक्सर करते हैं, वह है रेपो का क्लोन बनाना जो आपने अपने रेपो को क्लोन करने के बजाय _from_ को फोर्क किया था। अपने ब्राउज़र के एड्रेस बार की जाँच करें और सुनिश्चित करें कि आप अपने रेपो की क्लोनिंग कर रहे हैं। + +अब विजुअल स्टूडियो कोड खोलें। वीएस कोड का वेलकम पेज खुल जाएगा। वहां से नीचे दिखाए गए बार को खोलने के लिए `F1` दबाएं। ध्यान दें कि टेक्स्ट फ़ील्ड में पहले से ही एक `>` (इससे बड़ा) चिन्ह है। आप `CTRL-P` दबाकर इनपुट प्रॉम्प्ट पर भी जा सकते हैं और फिर `>` वर्ण टाइप कर सकते हैं। + +Clone Popup (Command Popup) + +आप देख सकते हैं कि नीचे सूचीबद्ध कुछ अस्पष्ट आदेश पहले से ही हैं। वे मेरे हाल ही में उपयोग किए गए आदेश हैं। तो बस उनकी परवाह मत करो। + +Clone repo + +अब 'गिट क्लोन' टाइप करें, केवल 'गिट' या 'क्लोन' (यह एक खोज की तरह काम करता है)। +प्रविष्टि `गिट: क्लोन` का चयन करें और `एंटर` दबाएं + +Paste Repository URL in + +अपनी रिपॉजिटरी का URL पेस्ट करें और `Enter` दबाएं। यह एक फ़ाइल एक्सप्लोरर खोलेगा जहाँ आप तब चुन सकते हैं जहाँ Git रिपॉजिटरी को संग्रहीत किया जाना चाहिए। + +**महत्वपूर्ण**: सुनिश्चित करें कि यह फोर्कड रिपोजिटरी है और मूल नहीं है, अन्यथा यह काम नहीं करेगा। + +Status popup + +आपको विजुअल स्टूडियो कोड के नीचे दाईं ओर एक स्टेटस पॉपअप देखना चाहिए। इसके समाप्त होने के बाद, आप संवाद में बटनों का उपयोग करके क्लोन रिपॉजिटरी (अब आपकी मशीन पर एक फ़ोल्डर) खोल सकते हैं। + +## एक शाखा बनाएं + +`F1` दबाकर फिर से कमांड पैलेट खोलें। `शाखा` टाइप करें और वहां से `शाखा बनाएं` कमांड चुनें। अगले चरण में अपनी नई शाखा का नाम टाइप करें, उदाहरण के लिए `ऐड-डेविड-क्रोल`। एंटर दबाएं और ब्रांच बन जाएगी. The branch is also already checked out. [What does checkout mean?](https://www.git-scm.com/docs/git-checkout) + +Branches Command Palette + +## आवश्यक परिवर्तन करें + +`Contributors.md` खोलें और फ़ाइल में कहीं भी अपना नाम जोड़ें। इस फ़ाइल में GFM (GitHub Flavored Markdown) है जो markdown सिंटैक्स का मालिकाना स्वाद है। + +अन्य योगदानकर्ताओं में से एक की प्रतिलिपि बनाएँ' लाइनों और इसे अपने नाम के साथ संशोधित करें यह सुनिश्चित करने के लिए कि आपको सिंटैक्स सही मिलता है - यह पिक्य हो सकता है। + +Add your name + +## गिटहब में बदलाव करें और पुश करें + +वीएस कोड के बाईं ओर एक मेनू है जिसमें 5 आइकन प्रदर्शित होते हैं। संस्करण नियंत्रण/स्रोत नियंत्रण चिह्न का चयन करें। +(शॉर्टकट : Ctrl + Shift + G) + +Commit changes + +फ़ाइल एक्सप्लोरर उन सभी फाइलों को प्रदर्शित करता है जिन्हें अंतिम प्रतिबद्धता के बाद बदल दिया गया था। फाइलों को मँडराकर और `+` (प्लस) पर क्लिक करके फाइलों का मंचन किया जाता है। + +Stashed Files + +एक्सप्लोरर के ऊपर लाइन में कुछ टाइप करें और चेकमार्क दबाएं। परिवर्तन अब आपकी स्थानीय प्रति के लिए प्रतिबद्ध हैं। अब परिवर्तनों को वापस GitHub पर धकेलना होगा। + +Stashed Files + +मेनू खोलने के लिए थ्री-डॉट आइकन का उपयोग करें जहां आप `पब्लिश ब्रांच` विकल्प का चयन करते हैं। यह आपके GitHub क्रेडेंशियल्स को डालने के लिए एक डायलॉग खोलना चाहिए। + +स्टैश की गई फ़ाइलें + +## समीक्षा के लिए अपने परिवर्तन सबमिट करें + +इस बिंदु पर आपने अपना परिवर्तन पूरा कर लिया है लेकिन यह अभी भी केवल आपके रेपो में रहता है। यह चरण आपको दिखाएगा कि अपने परिवर्तन को मर्ज करने के लिए शीर्ष-स्तरीय रेपो के व्यवस्थापक को अनुरोध कैसे सबमिट करें। + +गिटहब पर अपने रेपो में आपको नई शाखा अधिसूचना के बगल में `तुलना और पुल अनुरोध` बटन दिखाई देगा। उस बटन पर क्लिक करें। + +एक पुल अनुरोध बनाएं + +अब पुल रिक्वेस्ट सबमिट करें। + +पुल अनुरोध सबमिट करें + +जल्द ही मैं आपके सभी परिवर्तनों को इस परियोजना की मास्टर शाखा में मिला दूंगा। परिवर्तनों को मर्ज कर दिए जाने के बाद आपको एक सूचना ईमेल प्राप्त होगी। + +## यहाँ से कहाँ जाएं? + +बधाई! आपने अभी-अभी मानक _fork -> क्लोन -> संपादित करें -> PR_ वर्कफ़्लो पूरा किया है जिसका आप अक्सर एक योगदानकर्ता के रूप में सामना करेंगे! + +अपने योगदान का जश्न मनाएं और [वेब ऐप](https://firstcontributions.github.io#social-share) पर जाकर इसे अपने दोस्तों और अनुयायियों के साथ साझा करें। + +यदि आपको किसी सहायता की आवश्यकता हो या कोई प्रश्न पूछना हो तो आप हमारी सुस्त टीम में शामिल हो सकते हैं। [स्लैक टीम में शामिल हों](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)। + + +### [अतिरिक्त सामग्री](../additional-material/git_workflow_scenarios/additional-material.md) + +## अन्य टूल्स का उपयोग करने वाले ट्यूटोरियल +[मुख्य पृष्ठ पर वापस जाएं](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools) diff --git a/gui-tool-tutorials/translations/github-windows-vs-code-tutorial.pt_br.md b/gui-tool-tutorials/translations/github-windows-vs-code-tutorial.pt_br.md new file mode 100644 index 00000000000..ce9a77d1945 --- /dev/null +++ b/gui-tool-tutorials/translations/github-windows-vs-code-tutorial.pt_br.md @@ -0,0 +1,117 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Primeiras Contribuições + +| Visual Studio Code | Visual Studio Code | +| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ | + + +É difícil. É sempre difícil a primeira vez que você faz algo. Especialmente quando você está colaborando, cometer erros não é uma coisa confortável. Mas o código aberto tem tudo a ver com colaboração e trabalho em conjunto. Queríamos simplificar a maneira como os novos colaboradores de código aberto aprendem e contribuem pela primeira vez. + +Ler artigos e assistir a tutoriais pode ajudar, mas o que é melhor do que realmente fazer as coisas sem estragar nada. Este projeto visa fornecer orientação e simplificar a maneira como os novatos fazem sua primeira contribuição. Lembre-se, quanto mais relaxado você estiver, melhor você aprenderá. Se você está procurando fazer sua primeira contribuição, basta seguir os passos simples abaixo. Nós prometemos a você, vai ser divertido. + +Se você não tiver o Visual Studio Code em sua máquina, [instale-o](https://code.visualstudio.com/download). + +**Atenção:** Este tutorial foi feito usando o Visual Studio Code (Versão 1.27.2) em uma máquina Windows 10. Mais adiante neste tutorial, usaremos alguns atalhos de teclado. Eles podem diferir em outros sistemas operacionais (macOS/Linux), bem como no idioma do teclado (UK, DE, etc). Você pode percorrer sua lista de atalhos pesquisando "atalho" na Paleta de Comandos. + +## Fork este repositório + +fork this repository + +Fork este repositório clicando no botão fork no canto superior direito desta página. Isso criará uma cópia deste repositório em sua conta do GitHub. + +O GitHub acompanha o relacionamento entre seu repositório e aquele do qual você o bifurcou. Você pode pensar em seu repositório como uma cópia de trabalho. + +A maioria dos repositórios de alto nível do GitHub (ou seja, aqueles que não são bifurcados de nenhum outro repositório) têm uma pequena equipe principal de pessoas que podem confirmar alterações diretamente. Todos os outros contribuidores devem bifurcar o repositório e fazer alterações na bifurcação e, em seguida, criar uma solicitação de pull para solicitar que suas alterações sejam mescladas novamente no repositório de nível superior. Se o administrador de repo de nível superior gostar das alterações, elas serão mescladas e você ganhará fama e fortuna instantâneas! Mais sobre como fazer isso mais tarde. + +## Clone seu repositório + +clone this repository + +A próxima etapa é clonar seu repositório para sua máquina para que você possa começar a fazer alterações. O VS Code precisa do URL do seu repositório, então clique no botão "clone" e depois clique no ícone "copiar para a área de transferência". + +**CUIDADO:** Um erro que os novos contribuidores costumam cometer é clonar o repositório que você bifurcou _de_ em vez de clonar seu repositório. Verifique a barra de endereços do seu navegador e certifique-se de estar clonando seu repositório. + +Agora abra o Visual Studio Code. A página de boas-vindas do VS Code aparecerá. A partir daí, pressione `F1` para abrir a barra mostrada abaixo. Observe que já existe um sinal `>` (maior que) no campo de texto. Você também pode acessar o prompt de entrada pressionando `CTRL-P` e digite o caractere `>`. + +Clone Popup (Command Popup) + +Você pode notar que já existem alguns comandos obscuros listados abaixo. Esses são meus comandos usados recentemente. Então, simplesmente não se importe com eles. + +Clone repo + +Agora digite `git clone`, apenas `git` ou `clone` (funciona como uma pesquisa). +Selecione a entrada `Git: Clone` e pressione `Entrar` + +Colar URL do repositório + +Cole a URL do seu repositório e pressione `Entrar`. Isso abrirá um File Explorer onde você pode escolher onde o repositório Git deve ser armazenado. + +**Importante**: Certifique-se de que é o repositório bifurcado e não o original, caso contrário não funcionará. + +Status popup + +Você deve ver um pop-up de status no canto inferior direito do Visual Studio Code. Depois de terminar, você pode abrir o repositório clonado (agora uma pasta em sua máquina) usando os botões da caixa de diálogo. + +## Criar uma branch + +Abra a paleta de comandos novamente pressionando `F1`. Digite `branch` e selecione o comando `criar branch` a partir daí. Na próxima etapa digite o nome do seu novo branch, por exemplo `add-david-kroell`. Pressione enter e a ramificação será criada. A filial também já foi verificada. [O que significa checkout?](https://www.git-scm.com/docs/git-checkout) + +Branches Command Palette + +## Faça as alterações necessárias + +Abra `Contributors.md` e adicione seu nome em qualquer lugar do arquivo. Este arquivo contém GFM (GitHub Flavored Markdown), que é um sabor proprietário da sintaxe markdown. + +Copie um dos outros contribuidores' linhas e modifique-o com seu nome para ter certeza de obter a sintaxe correta - pode ser exigente. + +Add your name + +## Confirmar e enviar alterações para o GitHub + +No lado esquerdo do VS Code há um menu com 5 ícones exibidos. Selecione o ícone de controle de versão/Controle de origem. +(Atalho: Ctrl + Shift + G) + +Commitar alterações + +O explorador de arquivos exibe todos os arquivos que foram alterados após o último commit. Ao passar o mouse sobre os arquivos e clicar em `+` (mais), os arquivos são encenados. + +Arquivos guardados + +Digite algo na linha na parte superior do explorer e pressione a marca de seleção. As alterações agora estão confirmadas em sua cópia local. Agora as alterações precisam ser enviadas de volta ao GitHub. + +Arquivos guardados + +Use o ícone de três pontos para abrir o menu onde você seleciona a opção `Publicar Branch`. Isso deve abrir uma caixa de diálogo para colocar suas credenciais do GitHub. + +Arquivos guardados + +## Envie suas alterações para revisão + +Neste ponto, você concluiu sua alteração, mas ela ainda reside apenas em seu repositório. Esta etapa mostrará como enviar uma solicitação ao administrador do repositório de nível superior para mesclar sua alteração. + +Em seu repositório no GitHub, você verá o botão `Comparar & pull request` ao lado da nova notificação de branch. Clique nesse botão. + +crie uma pull request + +Agora envie a solicitação PR - pull request. + +submit pull request + +Em breve estarei mesclando todas as suas alterações no branch master deste projeto. Você receberá um e-mail de notificação assim que as alterações forem mescladas. + +## Para onde ir a partir daqui? + +Parabéns! Você acabou de concluir o fluxo de trabalho padrão _fork -> clone -> editar -> PR_ que você encontrará frequentemente como colaborador! + +Comemore sua contribuição e compartilhe com seus amigos e seguidores acessando [aplicativo da web](https://firstcontributions.github.io#social-share). + +Você pode se juntar à nossa equipe do slack caso precise de ajuda ou tenha alguma dúvida. [Junte-se à equipe do Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +### [Material adicional](../additional-material/translations/additional-material.pt_br.md) + +## Tutoriais usando outras ferramentas +[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools) diff --git a/gui-tool-tutorials/translations/github-windows-vs-code-tutorial_id.md b/gui-tool-tutorials/translations/github-windows-vs-code-tutorial_id.md new file mode 100644 index 00000000000..40d48ce4b40 --- /dev/null +++ b/gui-tool-tutorials/translations/github-windows-vs-code-tutorial_id.md @@ -0,0 +1,121 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Kontribusi Pertama + +| Visual Studio Code | Visual Studio Code | +| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ | + +Sulit. Memang selalu sulit melakukan sesuatu untuk pertama kali. Khususnya ketika kamu berkolaborasi, membuat sebuah masalah bukanlah hal yang mengenakkan. Tetapi proyek terbuka +berarti kolaborasi dan kerjasama. Kami ingin menyederhanakan cara belajar bagi kontributor dan cara berkontribusi untuk pertama kali. + +Membaca artikel & menonton tutorial bisa membantu, tetapi lebih baik praktek langsung tanpa membuat masalah apapun pada proyek. Laman ini bertujuan untuk memberikan panduan & menyederhanakan cara bagi pemula untuk membuat kontribusi pertama. Ingat semakin santai kamu, maka semakin baik kamu belajar. Jika kamu ingin membuat kontribusi pertama, cukup ikuti langkah-langkah sederhana di bawah ini. Kami janji, ini akan menyenangkan kok. + +Jika kamu belum punya Visual Studio Code pada perangkat mu, [install disini](https://code.visualstudio.com/download). + + +**Perlu Diingat:** Tutorial ini dibuat menggunakan Visual Studio Code (Versi 1.27.2) pada Windows 10. Nanti dalam tutorial ini kita akan menggunakan beberapa shortcut keyboard. Ini mungkin berbeda pada sistem operasi lain (macOS/Linux) serta bahasa keyboard (UK, DE, dll). Kamu dapat menelusuri daftar pintasan mu dengan mencari "shortcut" di Palet Perintah. + +## Fork repositori ini + +fork this repository + +Fork repo ini dengan mengklik tombol fork di kanan atas halaman ini. Ini akan membuat salinan repositori ini di akun GitHub Anda. + +GitHub selalu menjaga repo mu dan sumber repo yang sudah kamu fork supaya tetap pada jalurnya. Kamu bisa menganggap repo mu sebagai salinan pekerjaan. + +Sebagian besar repo GitHub tingkat atas (yaitu yang tidak di-copy dari repo lain mana pun) mempunyai tim inti yang terdiri dari orang-orang yang dapat langsung melakukan perubahan. Semua kontributor lain harus melakukan fork repo dan membuat perubahan pada fork, lalu membuat Pull Request untuk meminta perubahan mereka digabungkan kembali ke repo tingkat atas. Jika administrator repo tingkat atas menyukai perubahan, mereka akan menggabungkan perubahan mu dan kamu bisa mendapatkan reputasi dan nasib baik! Lebih lanjut tentang cara melakukannya akan dibahas nanti. + +## Klon Repositori mu + +clone this repository + +Langkah selanjutnya adalah mengkloning repo mu ke perangkat mu sehingga bisa segera mulai membuat perubahan. VS Code membutuhkan URL repo mu agar terhubung, jadi klik tombol "clone" dan kemudian klik ikon "copy to clipboard". + +**HATI-HATI:** Satu kesalahan yang sering dilakukan oleh kontributor baru adalah mengkloning repo utama yang kamu fork _sumbernya_ daripada mengkloning repo mu sendiri. Periksa alamat browser mu dan pastikan kamu mengkloning repo mu sendiri. + +Sekarang buka Visual Studio Code. Halaman selamat datang dari VS Code akan muncul. Dari sana tekan `F1` untuk membuka bar yang ditunjukkan di bawah ini. Perhatikan bahwa sudah ada tanda `>` (lebih besar dari) di kolom teks. Anda juga dapat membuka input prompt dengan menekan `CTRL-P` lalu ketik `>`. + +Clone Popup (Command Popup) + +Anda mungkin memperhatikan bahwa sudah ada beberapa perintah tidak jelas yang tercantum di bawah ini. Itu adalah perintah yang digunakan baru-baru ini. Jadi, hiraukan saja. + +Clone repo + +Sekarang ketik `git clone`, hanya `git` atau `clone` (berfungsi seperti melakukan pencarian). +Pilih Entri `Git: Clone` dan tekan `Enter` + +Paste Repository URL in + +Tempelkan URL repositori kamu dan tekan `Enter`. Ini akan membuka File Explorer di mana kamu dapat memilih di mana repositori Git harus disimpan + +**Penting**: Pastikan itu adalah repositori yang kamu fork dan bukan yang asli, jika tidak maka tidak akan berfungsi + +Status popup + +Kamu akan melihat status popup di kanan bawah Visual Studio Code. Setelah selesai, kamu dapat membuka repositori kloning (di folder yang sudah kamu pilih) menggunakan tombol di dialog. + +## Membuat Cabang (Branch) + +Buka kembali palet perintah dengan menekan `F1`. Ketik `branch` dan pilih perintah `create branch` dari sana. Pada langkah berikutnya ketik nama cabang baru kamu, misalnya `add-david-kroell`. Tekan enter dan cabang akan dibuat. Cabang juga sudah siap dipakai. [Apa artinya checkout?](https://www.git-scm.com/docs/git-checkout) + +Branches Command Palette + +## Buat Perubahan yang diperlukan + +Buka `Contributors.md` dan tambahkan nama kamu di mana saja di file. File ini berisi GFM (GitHub Flavoured Markdown) yang merupakan ciri khas sintaks markdown. + +Salin salah satu kontributor lain' baris dan modifikasi dengan nama mu untuk memastikan kamu menggunakan sintaks yang benar - itu bisa pilih-pilih + +Add your name + +## Commit & Push perubahan ke GitHub + +Di sisi kiri VS Code adalah menu dengan 5 ikon yang ditampilkan. Pilih ikon versi kontrol/Sumber Kontrol. +(Pintasan: Ctrl + Shift + G) + +Commit changes + +File explorer menampilkan semua file yang diubah setelah komit terakhir. Dengan mengarahkan penunjuk pada file dan mengklik `+` (plus) file akan disiapkan. + +Stashed Files + +Ketik sesuatu pada baris di atas explorer dan tekan tanda centang. Perubahan telah tersimpan pada salinan lokal kamu. Sekarang perubahan harus di _push_ kembali ke GitHub. + +Stashed Files + +Gunakan ikon titik tiga untuk membuka menu tempat kamu akan memilih opsi `Publish Branch`. Ini akan membuka dialog untuk memasukkan kredensial GitHub kamu. + +Stashed Files + +## Submit perubahan mu untuk diperiksa + +Dititik ini kamu telah menyelesaikan perubahan mu tetapi masih berada di repo mu sendiri. Langkah ini akan menunjukkan bagaimana cara mengirimkan permintaan ke administrator repo tingkat atas untuk menggabungkan perubahan + +Pada repo mu di GitHub, kamu akan melihat tombol `Compare & pull request` di sebelah pemberitahuan cabang baru. Klik tombol itu. + +create a pull request + +Sekarang kirimkan permintaan _pull_. + +submit pull request + +Segera saya akan menggabungkan semua perubahan mu ke dalam cabang utama proyek ini. Kamu akan mendapatkan email pemberitahuan setelah perubahan digabungkan. + +## Kemana lagi setelah ini? + +Selamat! kamu baru saja menyelesaikan alur kerja _fork -> clone -> edit -> PR_ standar yang akan sering kamu temui sebagai kontributor! + +Rayakan kontribusi mu dan bagikan dengan teman dan pengikut kamu dengan membuka [web app](https://firstcontributions.github.io#social-share). + +Kamu dapat bergabung dengan tim slack kami jika memerlukan bantuan atau memiliki pertanyaan. [Bergabung dengan tim Slack](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY). + + +### [ Materi tambahan ](../../additional-material/translations/additional-material.id.md) + + + +## Tutorial menggunakan Alat lain +[Kembali ke halaman utama](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools) diff --git a/gui-tool-tutorials/translations/github-windows-vs-code-tutorial_pt_br.md b/gui-tool-tutorials/translations/github-windows-vs-code-tutorial_pt_br.md new file mode 100644 index 00000000000..b550dedda04 --- /dev/null +++ b/gui-tool-tutorials/translations/github-windows-vs-code-tutorial_pt_br.md @@ -0,0 +1,124 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Primeiras Contribuições + +| Visual Studio Code | Visual Studio Code | +| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ | + +É difícil, sempre é difícil quando fazemos alguma coisa pela primeira vez. Especialmente quando você está colaborando, cometendo erros, não é nada confortável. No entanto, o open source é totalmente sobre colaboração e trabalho em equipe. Por isso, nós queremos simplificar a maneira como os novos colaboradores de código aberto aprendem e contribuem pela primeira vez. + +Ler artigos e assistir a tutoriais até podem ajudar, mas o que é melhor do que fazer as coisas sem bagunçar nada. Este projeto tem como objetivo orientar & simplificar a forma como os iniciantes fazem a sua primeira contribuição. Lembre-se que você aprende melhor quando está relaxado. Se você deseja fazer sua primeira contribuição, basta seguir os passos abaixo. Nós prometemos a você que será divertido! + +Se você não tem o Visual Studio 2017 na sua máquina, [instale-o](https://code.visualstudio.com/download). + +**Nota:** Este tutorial foi feito utilizando o Visual Studio Code (Versão 1.27.2) no Windows 10. Mais tarde, neste tutorial, vamos utilizar alguns atalhos no teclado. Eles podem ser diferentes em outros sistemas operacionais (mac/OS/Linux) assim como em teclados de outras linguagens (UK, DE, etc). Você pode pesquisar na lista de atalhos, buscando por "atalhos" na Paleta de Comando. + +## Faça o *Fork* deste repositório + +fork this repository + +Faça um *fork* deste repositório clicando no botão *fork* (bifurcar) no canto superior direito desta página. Isso criará uma cópia deste repositório em sua conta do GitHub. + +O GitHub rastreia a relação entre seu repositório e o original, o qual você fez o *fork*. Você pode pensar em seu repositório como uma cópia de trabalho. + +Muitos dos repositórios matrizes do GitHub (ou seja, aqueles que não são *Fork* de nenhum outro repositório) tem um pequeno grupo de pessoas que podem fazer commits de modificações diretamente. Todos os outros contribuidores devem fazer um *fork* do repositório e fazer alterações no *fork*, em seguida, devem criar um Pull Request para solicitar um *Merge* (mesclagem) das modificações feitas no repositório original. + +Se um dos administradores do repositório gostar e aprovar as tuas mudanças, eles *mergearão* e você ganhará fama e fortuna imediatamente! Abaixo, há mais detalhes sobre como fazer isso. + +## Clone o seu repositório + +clone this repository + + +O próximo passo será clonar seu repositório em sua máquina para que você possa modificá-lo. Visual Studio precisa da URL do seu repositório, portanto clique no botão "clone" e então clique no ícone "copy to clipboard". + +**CUIDADO:** Um erro que os novatos cometem com frequência é clonar o repositório do qual você fez o fork, ao invés de clonar seu repositório. Verifique a barra de endereços do seu navegador e certifique-se de que você está clonando o seu repositório. + +Agora, abra o Visual Studio Code. A página principal do VS Code vai minimizar. A partir daí, pressione `F1` para abrir a barra mostrada abaixo. Perceba que já existe um `>` (maior que) no campo de texto. Você pode também chegar até o prompt de entrada pressionando `CTRL-P` e então inserindo o caracter `>`. + +Clone Popup (Command Popup) + +Você pode notar que já aí já existem alguns comandos de sugestão abaixo. Esses são os seus comandos utilizados recentemente. Então, apenas ignore-os. + +Clone repo + +Agora, digite `git clone`, apenas `git` ou `clone` (isso funcionará como uma pesquisa). +Selecione a opção `Git: Clone` e então aperte `Enter`. + +Paste Repository URL in + +Cole a URL do seu repositório e aperte `Enter`. Isso vai abrir o Explorador de Arquivo onde você pode escolher onde o repositório Git será armazenado. + +**Importante**: Tenha certerza que este é o repositório *forkeado* e não é o original. Se não, não funcionará. + +Status popup + +Você pode ver uma janela do status no canto inferior direito do Visual Studio Code. Depois de finalizado esse processo, você pode abrir o repositório clonado (agora, uma pasta na sua máquina) e usar os botões no diálogo. + +## Crie uma *branch* + +Abra a Paleta de Comando novamente, pressionando `F1`. Digite nele `branch` e selecione o comando `create branch` a partir das sugestões. No próximo passo, digite o nome da sua nova *branch*, por exemplo: `add-david-kroell`. Presione `Enter` e a *branch* será criada. A *branch* também está preparada para o *check out*. [*O que isso significa?*](https://www.git-scm.com/docs/git-checkout) + +Branches Command Palette + +## Faça as mudanças necessárias + +Abra o arquivo `Contributors.md` e adicione o seu nome no fim da lista. Esse arquivo contém GFM (GitHub Flavored Markdown), que é uma função nativa da sintaxe do markdown. + +Copie uma das outras linhas dos contribuidores e modifique-a com o seu nome. Tenha certeza que a sintaxe está correta - ela pode ser exigente. + +Add your name + +## Faça um *Commit* & um *Push* das suas mudanças para o GitHub + +No lado esquerdo do VS Code tem um menu com 5 ícones a amostra. Selecione o ícone de `Controle de Versão/Controle da Fonte`. +(Atalho : Ctrl + Shift + G) + +Commit changes + +O Explorador de arquivos mostra todos os arquivos que foram mudados depois do último commit. Sobrepondo o mouse nos arquivos e clicando no `+` (mais) os arquivos serão colocados no *stage*. + +Stashed Files + +Escreva algo na caixa de texto, no topo do explorador e pressione o botão de *check*. As mudanças agora foram *commitadas* para a sua cópia local. Agora, as mudanças tem que serem mandadas para o GitHub. + +Stashed Files + +Use o ícone dos três pontos para abrir o menu onde você selecionará a opção `Publicar Branch`. Isso deve abrir uma caixa de diálogo para colocar as tuas credenciais do GitHub. + +Stashed Files + +## Submeta suas mudanças para uma revisão + +Nesse ponto, você completou suas mudanças, mas elas ainda estão no seu repositório. Esse passo vai mostrar para você como submeter uma requisição para o administrador do repositório original para *mergear* suas mudanças. + +No seu repositório no GitHub você verá o botão `Compare & Pull request` próximo a notificação da branch. Clique nesse botão. + +create a pull request + +Agora, submeta o *pull request*. + +submit pull request + +Breve as suas mudanças serão *mergeadas* na branch `master` desse projeto. Você será notificado por email uma vez que as mudanças forem *mergeadas*. + +## Para onde ir ? + + +Parabéns! Você acabou de completar o fluxo de trabalho *fork -> clone -> edit -> PR* que vocẽ vai realizar frequentemente como um contribuidor! + +Celebre a sua contribuição e compartilhe-a com os seus amigos e seguidores indo para o [web app](https://firstcontributions.github.io#social-share). + +Você pode se juntar à nossa comunidade no slack, caso precise de alguma ajuda ou tenha alguma dúvida. + +[Faça parte da nossa comunidade no Slack!](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY) + + +### [Material adicional](../additional-material/git_workflow_scenarios/additional-material.md) + +## Tutoriais utilizando outras ferramentas + +[Retorne para a página principal](https://github.com/firstcontributions/first-contributions/blob/master/translations/README.pt_br.md) diff --git a/gui-tool-tutorials/translations/github-windows-vs2017-tutorial.pt_br.md b/gui-tool-tutorials/translations/github-windows-vs2017-tutorial.pt_br.md new file mode 100644 index 00000000000..69047f36334 --- /dev/null +++ b/gui-tool-tutorials/translations/github-windows-vs2017-tutorial.pt_br.md @@ -0,0 +1,149 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Primeiras Contribuições + +|Visual Studio 2017|Visual Studio 2017 Edition| +|---|---| + +É difícil. Sempre é difícil fazer algo pela primeira vez. Especialmente quando você está colaborando, cometer erros não é confortável. Mas o open sourece tem tudo a ver com colaboração e trabalho em equipe. Nós queremos simplificar a maneira de aprendizagem aos novos contribuidores de open source e ajudar em sua primeira contribuição. + +Lendo artigos e olhando tutoriais podem ajudar, mas o que é melhor do que realmente fazer as coisas sem estragar nada. +Esse projeto visa em providenciar uma orientação e simplificar a maneira dos novatos a conseguirem a sua primeira contribuição. +Lembre-se, quanto mais relaxado melhor será o aprendizado. Se você está procurando em fazer a sua primeira contribuição, siga esses passos abaixo. Nós prometemos a você que vai ser divertido. + +Se você não possui o Visual Studio 2017 na sua máquina, [instale-o aqui](https://www.visualstudio.com/downloads/). + +## Faça um Fork deste repositório + +fork this repository + +Para fazer um Fork deste repositório, basta clicar no botão de fork no topo da página. Isso criará uma cópia do repositório na +sua conta GitHub. + +O GitHub acompapanhará o seu Fork e o repositório principal. Em outras palavras, podemos afirmar que o seu Fork é uma cópia do repositório principal. + +Os respositórios de mais alto nível do GitHub (exemplo: aqueles que não há um fork de nenhum outro repositório), tem uma pequena equipe principal de pessoas que podem diretamente fazer os seus commits. Os outros contribuidores deverão criar um Fork do respositório e fazer as mudanças nesse Fork, em seguida criar um Pull Request perguntando se essas mudanças poderão ser mescladas no repositório de alto nível. Se o administrador do repositório gostar das alterações ele irá mesclar as modificações e você ganhará instantaneamente fama e fortuna! Abaixo há um tutorial de como realizar. + +## Clone o seu repositório + +clone this repository + +O próximo passo será clonar seu repositório em sua máquina para que você possa modificá-lo. Visual Studio precisa da URL do seu repositório, portanto clique no botão "clone" e então clique no ícone "copy to clipboard". + +**CUIDADO:** Um erro que os novatos cometem com frequência é clonar o repositório do qual você fez o fork, ao invés de clonar seu repositório. Verifique a barra de endereços do seu navegador e certifique-se de que você está clonando o seu repositório. + +Agora é a hora de ir para o Visual Studio 2017! Você estará trabalhando na aba *Team Explorer* na maior parte do tutorial. Se ela não estiver aberta por padrão, clique em `View > Team Explorer` para abrí-la. + +Team Explorer + +*Team Explorer* tem muitas áreas e muitos botões de navegação, localizados no topo para te ajudar a achar essas diferentes áreas. Para clonar o repositório, você vai precisar estar na *Connect view*, que deve ser a padrão. Se você não conseguir ver o botão *clone*, clique no botão verde, em formato de tomada, no topo. + +Click the `Clone` option under **Local Git Repositories** and paste the URL to your repo in the text box. This should be the URL you copied to your clipboard from GitHub previously. + +Clique na opção `Clone` abaixo de **Local Git Repositories** e cole a URL do seu repositório na caixa de texto. Essa URL tem que ser a mesma que você copiou no GitHub anteriormente. + +Clique no botão `Clone` para iniciar o processo. + +Clone repo + +Quando o processo estiver completo, você será movido para a aba *Solution Explorer*, onde você poderá ver o conteúdo do repositório clonado. O seu parecerá um pouco diferente da foto abaixo, por que os arquivos estão em constante mudança! + +Solution Explorer + +## Crie uma *branch* + +Clique de volta na aba *Team Explorer* e use o a seleção principal de navegação para mostrar as *Branchs* disponíveis. + +Branches view + +Você deve ver o repositório **first-contributions** e a branch padrão, que é chamada `main`. Clique com o botão direito na `main` e escolha `New Local Branch From...`. + +New branch + +Dê à sua branch um nome como `add-` por exemplo: `add-alonzo-church`. + +Deixe a caixa de seleção `Checkout branch` marcada e clique no botão `Create Branch`. + +Create branch + +Você deverá ver a sua branch nova na lista. + +See new branch + +## Faça as mudanças necessárias + +Abra o arquivo `Contributors.md` e adicione o seu nome no fim da lista. Esse arquivo contém GFM (GitHub Flavored Markdown), que é uma função nativa da sintaxe do markdown. + +Copie uma das outras linhas dos contribuidores e modifique-a com o seu nome. Tenha certeza que a sintaxe está correta - ela pode ser exigente. + +Add your name + +## Commit & Push changes to GitHub + +Volte para a aba *Team Explorer* e navegue para a aba *Changes*. + +Changes + +Coloque a informação que você queira, poste o seu *commit* e clique em `Save`. O Visual Studio relembrará isso para futuros *commits*. + +Git user information + +**NOTA:** Visual Studio usa uma pasta escondida, chamada `.vs` para salvar suas configurações e preferências pessoais. O conteúdo desta pasta **não deverá ser salvo no Git**. +Se ela não estiver sido ingnorada ainda, você deve informar ao Git para ignorar essa pasta, com o intuito dela não ser mandada para o repositório. + +Essa pasta já foi ignorada neste repositório, então você não tem que realizar este passo. Ele está aqui somente para você ter uma referência para projetos futuros. + +Ignore vs folder + +Agora você deve ver uma lista de arquivos modificados e uma caixa de texto para digitar um cometário do *commit*. Os comentários devem ser breves, mas concretos. Não tem nada pior do que ler um comentário de um *commit* e ver algo como: `"Eu atualizei algumas coisas"`. Tire alguns segundos para realizar o seu *commit*. O seu time vai agradecer bastante mais tarde e você pode até agradecer a você mesmo! + +Clique em `Commit All and Push` para realizar um *commit* local e fazer um *push* das suas mudanças para o seu repositório, tudo em um único passo. + +**NOTA:** Um *Commit* pode ser realizado separadamente de um *Push*. Fazemos os dois juntos por conveniência. As mudanças realizadas e salvas em *commits* locais não serão refletidos no teu repositório no GitHub até que você faça um *Push*. + +Commit and Push + +A primeira vez que você realizar um *Push* para o GitHub, Visual Studio solicitará as suas credenciais do GitHub. Depois disso, ele as guardará no *cache*, para que você não precise realizar isso frequentemente. + +Login + +Depois de realizar uma operação de *Push*, abra o seu repositório no GitHub e deverá ver uma mensagem indicando um *push* recente de uma *branch*. + +Você pode ver suas mudanças abrindo a seleção `Branch: main` e selecionando a sua `branch`. Parabéns! Você pode compartilhar a URL da `branch` com o mundo e mostrar o seu progresso! + +View pushed branch on GitHub + +## Submeta as suas mudanças para uma revisão + +Neste ponto, você completou as mudanças, mas elas ainda estão somente no seu repositório. Esse passo te mostrará como submeter essas mudanças para um administrador para que ele possa fazer um *merge* das tuas mudanças. + +No seu repositório no GitHub, você verá o botão `Compare & pull request` próximo à notificação da *branch*. Cloque nesse botão. + +create a pull request + +Agora submeta o *Pull Request*. + +submit pull request + +Assim que possível, essas mudanças serão *mergeadas* para a `main branch` deste projeto. Você será notificado via email, quando essa movimentação for realizada. + +## Para onde ir daqui? + +Parabéns! Você acabou de completar o fluxo de trabalho *fork -> clone -> edit -> PR* que vocẽ vai realizar frequentemente como um contribuidor! + +Celebre a sua contribuição e compartilhe-a com os seus amigos e seguidores indo para o [web app](https://firstcontributions.github.io#social-share). + +You can join our slack team in case you need any help or have any questions. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY). + +Você pode se juntar à nossa comunidade no slack, caso precise de alguma ajuda ou tenha alguma dúvida. + +[Faça parte da nossa comunidade no Slack!](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY) + + +### [Material adicional](../additional-material/git_workflow_scenarios/additional-material.md) + +## Tutoriais utilizando outras ferramentas +[Retorne para a página principal](https://github.com/firstcontributions/first-contributions/blob/master/translations/README.pt_br.md) diff --git a/gui-tool-tutorials/translations/gitkraken-tutorial.pt-br.md b/gui-tool-tutorials/translations/gitkraken-tutorial.pt-br.md new file mode 100644 index 00000000000..d4e2e3d60c3 --- /dev/null +++ b/gui-tool-tutorials/translations/gitkraken-tutorial.pt-br.md @@ -0,0 +1,126 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Primeiras Contribuições + +|Visual Studio 2017|Visual Studio 2017 Edition| +|---|---| + +É difícil. Sempre é difícil fazer algo pela primeira vez. Especialmente quando você está colaborando, cometer erros não é confortável. Mas o open sourece tem tudo a ver com colaboração e trabalho em equipe. Nós queremos simplificar a maneira de aprendizagem aos novos contribuidores de open source e ajudar em sua primeira contribuição. + +Lendo artigos e olhando tutoriais podem ajudar, mas o que é melhor do que realmente fazer as coisas sem estragar nada. +Esse projeto visa em providenciar uma orientação e simplificar a maneira dos novatos a conseguirem a sua primeira contribuição. +Lembre-se, quanto mais relaxado melhor será o aprendizado. Se você está procurando em fazer a sua primeira contribuição, siga esses passos abaixo. Nós prometemos a você que vai ser divertido. + + + +## Git Kraken + +Baixe [GitKraken](https://www.gitkraken.com), Instale e abra. + +Provavelmente aparecerá um "Bem-vindo ao GitKraken" com um espaço para entrar na sua conta do GitHub e permitir que o GitKraken possa ter o acesso dela. + + +login to GitHub + +(opcional) Vá para Aqruivos -> Preferências e ajuste o diretório do seu projeto para a raiz de seus repositórios locais. + + +## Faça um Fork deste repositório + +Para fazer um Fork deste repositório, basta clicar no botão de fork no topo da página. +fork this repository +Isso criará uma cópia do repositório na sua conta GitHub. + + +## Clone o seu repositório + +No GitKraken, vá até Arquivo -> Clone Repositório. + + +clone this repository + + +Selecione GitHub.com no painel direito. De baixo do nome de usuário, deverá aparecer "first-contributions". Clique nesse repositório e confirme na parte inferior do painel, se aparece o local do diretório onde você quer clonar. + +Quando estiver tudo certo com o diretório, clique em "Clone o repositório!" + + +## Crie uma Branch + +Clique o botão branch na barra de ferramentas. + +Nomeie a sua branch "add-seu-nome", for example: "add-william-sutton" + +name your branch + + +## Faça mudanças necessárias e faça um commit nelas + +Agora abra o arquivo `Contributors.md` em um editor de texto e adicione o seu nome, em seguida salve-o. + +Se você estiver com o repositório aberto no GitKraken, haverá mudanças. +Revise e faça um Stage nessas mudanças selecionando o commit mais recente marcado com "// WIP" e com número de arquivos modificados e o tipo de mudança. + +edit some file(s) + +Revise esses arquivos que foram modificados e decida o que colocar no Stage. O Stage é importante, pois informa o Git extamente quais arquivos modificados você quer mandar no commit. + + +stage your changes + + +Quando escrever uma boa mensagem no commit ("Add para a lista de Contribuidores" parece bom e descritivo) e satisfeito com as suas mudanças, você pode apertar no "Stage todas as mudanças" para fazer o Stage em todas as alterações ou "Stage Arquivo" para cada arquivo modificado individualmente. + + +clone this repository + + +Se você mudar de ideia, você pode fazer um Unstage (processo reverso do Stage) das sua modificações ou discartar todas elas juntas. +CUIDADO: A palavra discartar fala por si só, ou seja, é uma operação destrutiva. Só faça isso, se você não quer nenhuma mundança no repositório que estiver trabalhando. + +Aperte commit. + +Parabéns, você acabou de fazer um commit de todas as suas mudanças na sua branch local do seu Fork. Em diante! + + +## Faça um Push nas suas modificações para o GitHub + +push your changes + +Na barra de ferramentas, clique no botão Push. + +origin or branch + +Se você quer enviar as mudanças direto para branch master, você pode enviar para a branch de origem. Caso contrário, selecione uma branch apropriada para mandar. + + +## Envie as suas mudanças para revisão + +No seu repositório do GitHub você vai ver um botão escrito: `Compare & pull request`, que fica ao lado da notificação da nova branch. Clique nesse botão. + +create a pull request + +Agora envie esse Pull Request. + +submit pull request + +Logo irei mesclar todas as suas mudanças na branch master do projeto. Você receberá uma notificação pelo e-mail quando as alterações forem mescladas. + +## Onde eu posso ir a partir daqui? + +Parabéns! Você completou o fluxo de trabalho básico _fork -> clone -> edit -> PR_, onde você encontrará muito como contribuidor. + +Celebre a sua contribuição e compartilhe com seus amigos e seguidores no [web app](https://firstcontributions.github.io/#social-share). + +Caso precise de ajuda ou tenha alguma pergunta, você pode se juntar à nossa equipe Slack. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + + +### [Material Adicional](../additional-material/git_workflow_scenarios/additional-material.md) + + +## Tutoriais usando outras ferramentas +[Voltar para página principal](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools) diff --git a/translations/README.afk.md b/translations/README.afk.md new file mode 100644 index 00000000000..9118757470e --- /dev/null +++ b/translations/README.afk.md @@ -0,0 +1,129 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Eerste Bydraes + +Dit is moeilik. Dit is altyd moeilik om die eerste keer iets te doen. Veral wanneer jy saamwerk, maak foute nie 'n gemaklike ding nie. Ons wou die manier waarop nuwe open source bydraers vir die eerste keer leer en bydra, vereenvoudig. + +Lees artikels en kyk tutoriale kan help, maar wat is beter as om die goed in die praktyk te doen? Hierdie projek het ten doel om leiding te gee en die manier waarop beginners hul eerste bydrae maak, te vereenvoudig. As jy jou eerste bydrae wil maak, volg die onderstaande stappe. + +#### *As jy nie gemaklik is met die opdraglyn nie, [is daar tutoriale wat GUI-instrumente gebruik.](#Bykomende-materiaal )* + + +fork this repository + +As jy nie git op jou masjien het nie, [installeer dit]( https://help.github.com/articles/set-up-git/). + +## Vork hierdie bewaarplek + +Vork hierdie repo deur op die vurk knoppie bo-aan hierdie bladsy te klik. Dit sal 'n kopie van hierdie repository in u rekening skep. + +## Klone die repository + +clone this repository + +Klone nou die vurk repo aan jou masjien. Gaan na jou GitHub-rekening, maak die vurk repo oop, klik op die kloonknop en klik dan op die kopie na die knipbord- ikoon. + +Open 'n terminaal en voer die volgende git opdrag uit: + +``` +git clone "url you just copied" +``` + +waar "url jy net gekopieer" het (sonder die aanhalingstekens) is die url na hierdie repository (jou vurk van hierdie projek). Sien die vorige stappe om die url te verkry. + +copy URL to clipboard + +Byvoorbeeld: + +``` +git clone https://github.com/this-is-you/first-contributions.git +``` + +waar `this-is-youis` jou GitHub gebruikersnaam Hier kopieer jy die inhoud van die eerste bydrae repository in GitHub na jou rekenaar. + +## Skep 'n tak + +Verander na die repository gids op jou rekenaar (as jy nie reeds daar is nie): + +``` +cd first-contributions +``` + +Skep nou 'n tak met die git `checkout` opdrag: + +``` +git checkout -b +``` + +Byvoorbeeld: + +``` +git checkout -b add-alonzo-church +``` + +(Die naam van die tak hoef nie die woord by te voeg nie, maar dit is 'n redelike ding om in te sluit omdat die doel van hierdie tak is om jou naam by 'n lys te voeg.) + +## Maak die nodige veranderinge en verbind die veranderinge + +Nou oop `Contributors.md` lêer in 'n teksredigeerder, voeg jou naam daarby. Moet dit nie aan die begin of einde van die lêer byvoeg nie. Sit dit oral tussenin. Stoor nou die lêer. + +git status + +As u na die projekgids gaan en die opdrag uitvoer `git status`, sal u sien dat daar veranderinge is. + + +Voeg die veranderinge by die tak wat jy net geskep het deur die `git add` opdrag te gebruik: + +``` +git add Contributors.md +``` + +Doen nou die veranderinge deur die `git commit` opdrag te gebruik: + +``` +git commit -m "Add to Contributors list" +``` + +vervang `` met jou naam. + +## Druk veranderinge na GitHub + +Druk jou veranderinge deur die opdrag te gebruik `git push`: + +``` +git push origin +``` + +vervang `` met die naam van die tak wat jy vroeër geskep het. + +## Dien jou veranderinge in vir hersiening + +As jy na jou repository op GitHub gaan, sal jy 'n `Compare & pull` requestknoppie sien. Klik op daardie knoppie. + +create a pull request + +Dien nou die trekversoek in. + +submit pull request + +Binnekort sal ek al jou veranderinge in die meestertak van hierdie projek saamsmelt. U sal 'n kennisgewing-e-pos ontvang sodra die veranderinge saamgesmelt is. + +## Waarheen gaan jy vandaan? + +Geluk! Jy het net die standaardvurk voltooi -> klone -> wysig -> PR- werkvloei wat jy dikwels as 'n bydraer sal ervaar! + +Vier jou bydrae en deel dit met jou vriende en volgelinge deur na die [webprogram te](https://roshanjossey.github.io/first-contributions/#social-share) gaan . + +U kan by ons span aansluit indien u enige hulp nodig het of enige vrae het. [Sluit aan by 'n slapende span](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Kom ons begin met die bydrae tot ander projekte. Ons het 'n lys van projekte saamgestel met maklike probleme waarmee u kan begin. Kyk na [die lys van projekte in die web app](https://roshanjossey.github.io/first-contributions/#project-list). + +### [Bykomende materiaal](../additional-material/git_workflow_scenarios/additional-material.md) + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visuele Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visuele Studio Kode](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.al.md b/translations/README.al.md new file mode 100644 index 00000000000..a9712316bce --- /dev/null +++ b/translations/README.al.md @@ -0,0 +1,127 @@ +[![Open Source Love](https://firstcontributions.github.io/open-source-badges/badges/open-source-v1/open-source.svg)](https://github.com/firstcontributions/open-source-badges) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Kontributet e Para + +Është e vështirë. Është gjithmonë e vështirë hera e parë kur bën diçka. Sidomos kur bashkëpunon, të bësh gabime nuk është një ndjenjë e mirë. Ne duam ta thjeshtësojmë mënyrën se si kontribuesit e open-source mësojnë dhe kontribuojnë për herë të parë. +Leximi i artikujve & shikimi i tutorialve ndihmojnë, por ç'është më mirë se sa ta bësh këtë gjë në një vend praktike? Ky projekt synon të udhëzojë & të thjeshtësojë mënyrën se si fillestarët bëjnë kontributin e tyre të parë. Nëse dëshiron të bësh kontributin tënd të parë, ndiqi hapat më poshtë. + +#### _Nëse ende nuk ndjehesh komod me command line, [këtu ke tutoriale që përdorin veglat e GUI](#Tutoriale-duke-përdorur-vegla-tjera)_ + +fork this repository + +Nëse nuk ke Git të instaluar në pajisjen tënde, [instaloje](https://help.github.com/articles/set-up-git/). + +## Bëje fork këtë repozitor + +Për të bërë fork këtë repozitor kliko butonin fork në majë të kësaj faqeje. Kjo do të krijojë një kopje të ketij repozitori në llogarinë tënde. + +## Klonoje këtë repozitor + +clone this repository + +Tani klonoje në pajisjen tënde repozitorin që bëre fork. Shko te llogaria e GitHub, hap forked repository, kliko butonin Code dhe pastaj kliko ikonën _copy to clipboard_. + +Hap terminalin dhe bëje run git komandën në vazhdim: + +``` +git clone "url që sapo ke kopjuar" +``` + +ku "url që sapo ke kopjuar" (pa thonjëzat) është url e këtij repozitori (repozitori që bëre fork). Shiko hapat e mëparshëm për të marrë url-në. + +copy URL to clipboard + +Për shembull: + +``` +git clone https://github.com/ky-je-ti/first-contributions.git +``` + +ku `ky-je-ti` është emri jot në GitHub. Këtu ti e kopjon përmbajtjen e repozitorit first-contributions në GitHub te kompjuteri jot. + +## Krijo një degë (branch) + +Ndryshoje lokacionin te repozitori në kompjuterin tënd (nëse nuk je në lokacionin e duhur): + +``` +cd first-contributions +``` + +Tani krijo një degë duke përdorur komandën `git checkout`: + +``` +git checkout -b +``` + +Për shembull: + +``` +git checkout -b add-filan-fisteku +``` + +(Emri i degës nuk është e nevojshme të ketë fjalën _add_ në të, por është e arsyeshme të përfshihet pasi që qëllimi i kësaj dege është të shtojë emrin tënd në një listë.) + +## Bëji ndryshimet e nevojshme dhe bëji commit + +Tani hap fajllin `Contributors.md` në një program për editim të tekstit dhe shto emrin tënd. Mos e shto në fillim ose në fund. Shtoje ku të duash në mes. Tani, ruaj fajllin. + +git status + +Nëse shkon te lokacioni i projektit dhe e ekzekuton komandën `git status`, do shohësh se ka ndryshime. + +Shtoji këto ndryshime te dega që sapo krijove duke përdorur komandën `git add`: + +``` +git add Contributors.md +``` + +Tani bëji commit këto ndryshime duke përdorur komandën `git commit`: + +``` +git commit -m "Add to Contributors list" +``` + +zëvendëso `` me emrin tënd. + +## Bëji push (shtyji) ndryshimet në GitHub + +Bëji push ndryshimet duke përdorur komandën `git push`: + +``` +git push origin +``` + +zëvendëso `` me emrin e degës që krijove më herët. + +## Bëji ndryshimet submit për shqyrtim + +Nëse shkon te repozitori jot në GitHub, do të shohësh një buton `Compare & pull request`. Klikoje. + +create a pull request + +Tani bëje submit këtë pull request. + +submit pull request + +Së shpejti do të bashkoj (bëj merge) të gjitha ndryshimet te dega master e këtij projekti. Ti do të njoftohesh me email kur të bëhen ndryshimet. + +## Ku të shkosh nga këtu? + +Urime! Ti sapo ke kompletuar procesin _fork -> clone -> edit -> PR_ që do ta hasësh shpesh si kontributor! + +Festoje kontributin tënd dhe ndaje me shokët dhe ndjekësit duke shkuar te [web aplikacioni](https://firstcontributions.github.io/#social-share). + +Ti mund të bashkohesh në ekipin tonë në slack nëse të duhet ndihmë ose nëse ke ndonjë pyetje. [Bashkohu ekipit në slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Tani të të ndihmojmë që të kontribuosh në projekte tjera. Ne kemi krijuar një listë projektesh me probleme të lehta tek të cilat mund të fillosh. Shiko [listën e projekteve në web apliacion](https://firstcontributions.github.io/#project-list). + +### [Materiale shtesë](additional-material/git_workflow_scenarios/additional-material.md) + +## Tutoriale duke përdorur vegla tjera + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.am.md b/translations/README.am.md new file mode 100644 index 00000000000..03c82dabcf6 --- /dev/null +++ b/translations/README.am.md @@ -0,0 +1,124 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# የመጀመሪያ አስተዋጽዖዎች + +ይህ ፕሮጀክት ጀማሪዎች የመጀመሪያ አስተዋጾ የሚያደርጉበትን መንገድ ለማቅለል እና ለመምራት ያለመ ነው። የመጀመሪያዎን አስተዋፅዖ ለማድረግ ከፈለጉ ከታች ያሉትን ደረጃዎች ይከተሉ + + +#### command line ካልተመቸህ, [GUI መሳሪያዎችን በመጠቀም አጋዥ ስልጠናዎች አሉ።.](#Tutorials-Usin'-Other-Tools) + +fork this repository + +በማሽንዎ ላይ git ከሌለዎት, [ይጫኑት](https://help.github.com/articles/set-up-git/). + +## Fork this repository + +በዚህ ገጽ ላይኛው ክፍል ላይ ያለውን fork ቁልፍን ጠቅ በማድረግ ይህንን ይጫኑት። +ይህ በአንተ መለያ ውስጥ የዚህን repository ቅጂ ይፈጥራል። + +## Clone the repository + +clone this repository + +አሁን Fork ይህን repository ወደ ማሽንዎ. ወደ GitHub መለያዎ ይሂዱ, የእርሶን repository ይክፈቱ. የኮድ ምልክቱን ጠቅ ያድርጉ እና ከዚያ ቅጂውን ምልክቱን ጠቅ ያድርጉ ለመቅዳት. + +``` +git clone "የቀዱትን url' ያስገቡ" +``` +"የቀዱትን url' ያስገቡ" (ያለ ጥቅስ ምልክቶች) ይህ የዚህ repository url ነው(የእርሶ ቅጂ ፕሮጀክት). url ለማግኘት የቀደመውን ደረጃዎች ይመልከቱ. + +copy URL to clipboard + +ለምሳሌ: + +``` +git clone https://github.com/this-is-you/first-contributions.git +``` + +where `this-is-you` የእርስዎ GitHub መለያ ስም ነው።. እዚህ በ GitHub ላይ ያለውን የመጀመሪያ አስተዋፅዖ repository ይዘቶችን ወደ ኮምፒውተርዎ እየገለበጡ ነው። + +## Create a branch(ቅርንጫፍ ይፍጠሩ) + +በኮምፒተርዎ ላይ ያለውን repository ማውጫ ይቀይሩ (እዚያ ከሌለዎት): + +``` +cd first-contributions +``` + +አሁን የ `git checkout` ትዕዛዝን በመጠቀም ቅርንጫፍ ይፍጠሩ: + +``` +git checkout -b +``` + +ለምሳሌ: + +``` +git checkout -b github-ethiopia +``` + +## አስፈላጊ ለውጦችን ያድርጉ እና ለውጦችን commit ያድርጉ + +አሁን የ Contributors.md ፋይልን በጽሑፍ አርታኢ(editor) ውስጥ ይክፈቱ፣ ስምዎን በእሱ ላይ ያክሉ። በፋይሉ መጀመሪያ ወይም መጨረሻ ላይ አይጨምሩት። በመካከል የትኛውም ቦታ ላይ ያስቀምጡት. አሁን, ፋይሉን ያስቀምጡ(save). + +git status + +ወደ የፕሮጀክት ማውጫው ሄደው የ git status ከፈጸሙ ለውጦች እንዳሉ ያያሉ። + +የ `git add` ትእዛዝን በመጠቀም እነዚያን ለውጦች አሁን በፈጠሩት ቅርንጫፍ ላይ አክል፡ + +``` +git add Contributors.md +``` + +አሁን የ `git commit` ትዕዛዝ በመጠቀም እነዚህን ለውጦች ያድርጉ፡ + +``` +git commit -m "Add <የእርስዎ-ስም> to Contributors list" +``` + +<የእርስዎ-ስም> ፋንታ የራስዎትን ስም ይጻፉ. + +## ለውጦችን ወደ GitHub ይጫኑ + +`git push` የሚለውን ትዕዛዝ በመጠቀም ለውጦችዎን ይጫኑ + +``` +git push origin <የእርስዎ-branch-name> +``` + +`<የእርስዎ-branch-name>` ፋንታ የራስዎትን branch ስም ያስገቡ + +## ለውጦችዎን ለግምገማ ያስገቡ + +በ GitHub ላይ ወደ repository ከሄዱ፣ `Compare & pull request` ጥያቄን ያያሉ። በዚያ ቁልፍ ላይ ጠቅ ያድርጉ። + +create a pull request + +አሁን pull request ጥያቄውን ያስገቡ + +submit pull request + +በቅርቡ ሁሉንም ለውጦችዎን ወደ የዚህ ፕሮጀክት ዋና ቅርንጫፍ አዋህዳለሁ. ለውጦቹ ከተዋሃዱ በኋላ የማሳወቂያ ኢሜይል ይደርስዎታል። + +## ከዚህ ወዴት መሄድ አለብዎት ? + +እንኳን ደስ ያለህ! አሁን መደበኛ fork -> clone -> edit -> pull request ሂደትን ጨርሰዋል. እንደ አስተዋጽዖ አበርካች ብዙ ጊዜ ይህ ሂደት ያጋትሞታል + +አስተዋጾዎን ያክብሩ እና ለጓደኞችዎ እና ተከታዮችዎ ያካፍሉ ወደ [ዲህረ ገጾ በመሄድ](https://firstcontributions.github.io/#social-share). + +ማንኛውም እርዳታ ከፈለጉ ወይም ማንኛውም ጥያቄ ካለዎት የእኛን [Slack ቡድን](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY) መቀላቀል ይችላሉ. + +አሁን ለሌሎች ፕሮጀክቶች በማበርከት እንጀምር. እርስዎ ሊጀምሩባቸው የሚችሉ ቀላል ጉዳዮች ያላቸውን የፕሮጀክቶች ዝርዝር አዘጋጅተናል።. [እኚህን ማስፈተሪያ ይከተሉ](https://roshanjossey.github.io/first-contributions/#project-list). + +### [ተጨማሪ ቁሳቁስ](../additional-material/git_workflow_scenarios/additional-material.md) + +## ሌሎች መሳሪያዎችን በመጠቀም አጋዥ ስልጠናዎች + +|GitHub Desktop|Visual Studio 2017|GitKraken| +|---|---|---| +|[GitHub Desktop](../github-desktop-tutorial.md)|[Visual Studio 2017](../github-windows-vs2017-tutorial.md)|[GitKraken](../gitkraken-tutorial.md)| diff --git a/translations/README.ar.md b/translations/README.ar.md new file mode 100644 index 00000000000..d706f392749 --- /dev/null +++ b/translations/README.ar.md @@ -0,0 +1,179 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +#
مساهمتك الأولى
+ +
+الصعوبة متوقعة عندما تبدأ بأي عمل جديد، خصوصاً إذا كان العمل يتضمن أشخاص آخرون، مما يجعل الوقوع في الخطأ مزعجا. +
+لكن المساهمة في مشاريع مفتوحة المصدر يتطلب ويتوقع الخطأ ولهذا السبب الآخرون سيساعدونك في تصحيح هذا الخطأ. +
+في هذا المشروع هدفنا هو تسهيل الطريق لمساهمتك الأولى. +
+ + +
+قراءة ومشاهدة التعليمات المتوفرة على الإنترنت ستساعدك حتماً، لكنك ستستفيد أكثر إذا استطعت المساهمة في مشروع دون الخوف من الوقوع في الخطأ. هذا المشروع يركز على توفير التوجيهات والتعليمات البدائية لإتمام أول مساهمة لك. +تذكر أن الخطأ متوقع والهدف أن تتجاوز الخطأ في هذه البيئة، نريد منك أن تكون مسترخيا ومتابعا الخطوات المتوفرة لإتمام مشاركتك الأولى. نعدك ستستمع بذلك. +
+ + +
+إذا لم يكن لديك git على الجهاز الخاص بك،قم بتثبيته من هنا +
+ +##
افرق هذا المشروع - Fork this Repository
+fork this repository +
+افرق هذا المشروع بالضغط على زر Fork في أعلى هذه الصفحة. +من خلال ذلك ستنشأ نسخة من هذا المشروع على حسابك الخاص. +
+ +##
استنسخ هذا المشروع - Clone the repository
+ +clone this repository + +
+استنسخ هذا المشروع على جهازك. +انقر على زر Clone ثم انقر على أيقونة Copy to clipboard +
+copy URL to clipboard +
+افتح الطرفية واكتب الأمر التالي: +
+ +``` +git clone "url you just copied" +``` + +
قم باستبدال "url you just copied" بالرابط الذي نسخته من الخطوة السابقة، هذا الرابط يحتوي على المشروع.
+ +
على سبيل المثال:
+ +``` +git clone https://github.com/this-is-you/first-contributions.git +``` + +
+في هذا المثال لاحظ 'this-is-you' سيكون اسم حسابك في موقع github يليه رابط المشروع الذي فرقته في أول خطوة، هذا الأمر سينسخ محتويات المشروع على جهازك لتتمكن من التعديل عليه بحرية. +
+
+ +##
إنشاء فرع - Create a branch
+ + +
انتقل إلى المجلد الذي يحتوي على المشروع عن طريق الأمر التالي:
+ +``` +cd first-contributions +``` + +
الآن قم بإنشاء فرع عن طريق الأمر التالي:
+ +``` +git checkout -b "add-your-name" +``` + +
اسمك بدل add-your-name
+ +
على سبيل المثال:
+ +``` +git checkout -b "add-alonzo-church" +``` + +
+ +##
قم بإجراء التعديلات المطلوبة وأتممها
+ +
+الآن قم بفتح الملف "Contributors.md" في محرر النصوص المفضل لديك وأضف اسمك ثم احفظ الملف. +بعد ذلك اذهب إلى الطرفية واكتب الأمر هذاgit status هذا الأمر سيظهر لك التغيرات التي حدثت في المشروع. +لإضافة هذه التغييرات قم بإضافتها عن طريق هذا الأمر git add. +
+ +``` +git add Contributors.md +``` + +
الآن قم بإتمام التغييرات باستخدام الأمر git commit.
+ +``` +git commit -m "Add to Contributors list" +``` + +
استبدل <your-name> باسمك.
+
+ +##
ارفع التغييرات إلى github - Push changes to Github
+ +
ارفع التغيررات عن طريق الأمر git push
+ +``` +git push origin "add-your-name" +``` + +
استبدل <add-your-name> باسم الفرع الذي أنشأته من قبل.
+ + +
+

سلم تغيراتك للمراجعة

+ + +
في صفحة المشروع الخاصة بك يوجد زر Compare & pull request. اضغط على هذا الزر.
+ +create a pull request + +
والآن سلم طلبك لتتم مراجعته
+ +submit pull request + +
بعد المراجعة سوف أقوم بدمج تغيرراتك إلى الفرع الرئيس في المشروع. سيتم تنبيهك عن طريق البريد الإلكتروني بذلك.
+ +
الفرع الرئيس الخاص بك لن يحتوي على هذه التغيررات. عليك مزامنته مع الفرع الرئيس عن طريق الخطوات التالية.
+ +##
مزامنة نسختك مع المشروع الرئيسي
+ +
الخطوة الأولى، انتقل إلى الفرع الرئيس.
+ +``` +git checkout master +``` + +
ثانياً، أضف رابط مشروعي كـupstream remote url.
+ +``` +git remote add upstream https://github.com/Roshanjossey/first-contributions +``` + +
بهذه الطريقة نخبر git أن هناك نسخة أخرى من هذا المشروع في هذا الرابط ونسميها upstream. +بعد أن أوافق على تغيرراتك، قم بسحب النسخة الجديدة من المشروع عن طريق الأمر التالي: +
+ +``` +git fetch upstream +``` + +
هنا سنقوم بسحب جميع التغييرات من (upstream remote). والآن، عليك أن تدمج التحديثات الجديدة من فرعي إلى فرعك الرئيس.
+ +``` +git rebase upstream/master +``` + +
وهنا تطبق التغييرات إلى الفرع الرئيس. إذا رفعت التغييرات لفرعك الرئيس سيتم تحديث مشروعك
+ +``` +git push origin master +``` + +
لاحظ أنك ترفع إلى remote اسمه origin.
+
+ +##
توجيهات بإستخدام أدوات أخرى
+ +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.aze.md b/translations/README.aze.md new file mode 100644 index 00000000000..d153768f683 --- /dev/null +++ b/translations/README.aze.md @@ -0,0 +1,116 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# İlk töhfələr + +Bu layihə yeni başlayanların ilk töhfələrini vermə yollarını sadələşdirmək və istiqamətləndirmək məqsədini daşıyır. İlk töhfənizi vermək istəyirsinizsə, aşağıdakı addımları izləyin. + +_Əgər komanda sətri ilə rahat deyilsinizsə, [burada GUI alətlərindən istifadə edən təlimatlar tapa bilərsiniz.](#Digər-alətlərin-istifadəsi-üçün-təlimlər)_ + +fork this repository + +#### Maşınınızda (yəni, kompüterinizdə) GIT yoxdursa, [buradan quraşdıra bilərsiniz](https://help.github.com/articles/set-up-git/). + +## Layihəni "çəngəlləmək" + +Səhifənin yuxarı hissəsindəki "Fork" düyməsini vuraraq bu layihəni çəngəlləyin. +Bu hesabınızda deponun bir kopyasını yaradacaqdır. + +## Deponu (Repository) klonlaşdırma + +clone this repository + +İndi çəngəlli deponu kompüterinizə klonlaşdırın. GitHub hesabınıza daxil olun, çəngəlli deponu açın, kod düyməsinə vurun və sonra _copy to clipboard_ simgəsinə klikləyin. + +Daha sonra terminalı açın və aşağıdakı git komandasını daxil edin: + +``` +git clone "kopyaladığınız-url" +``` +"kopyaladığınız-url" (dırnaq işarəsi olmadan) yerinə bu deponun GitHub səhifəsindən aldığınız linki kopyalayın. + +copy URL to clipboard + +Misal üçün: +``` +git clone https://github.com/istifadəçi-adı/first-contributions.git +``` +`istifadəçi-adı` sizin GitHub istifadəçi adınızdır. Burada siz GitHub-da ilk töhfələr deposunun məzmununu kompüterinizə köçürürsünüz. + +## Budaq (Branch) yaratmaq + +Kompüterinizdəki depo qovluğuna keçin (əgər orada deyilsinizsə): + +``` +cd first-contributions +``` +`git checkout` əmrini istifadə edərək bir Budaq (Branch) yaradın: +``` +git checkout -b +``` + +Misal üçün: +``` +git checkout -b add-alonzo-church +``` + +## Lazımi dəyişiklikləri edin və bu dəyişiklikləri həyata keçirin + +İndi `Contributors.md` faylını mətn redaktorunda açın, adınızı əlavə edin. Faylın əvvəlinə və ya sonuna əlavə etməyin. Arada bir yerə qoyun. İndi faylı yadda saxlayın. + +git status + +Layihə qovluğuna gedib `git status` əmrini icra etsəniz, dəyişikliklərin olduğunu görəcəksiniz. + +Bu dəyişiklikləri `git add` əmrindən istifadə edərək yaratdığınız Budağa əlavə edin: + +``` +git add Contributors.md +``` + +İndi `git commit` əmrindən istifadə edərək bu dəyişiklikləri edin: + +adınızla `` ilə əvəz olunsun. + +## Dəyişiklikləri GitHub-a itələyin (push) + +Dəyişikliklərinizi "git push" əmrindən istifadə edərək itələyin: + + +``` +git push origin +``` + +`` yerinə öz istifadəçi adınızı daxil edin. + +## Dəyişikliklərinizi nəzərdən keçirmək üçün göndərin + +GitHub-dakı deponuza daxil olsanız, bir `Compare & pull request` düyməsini görəcəksiniz. Bu düyməni vurun. + +create a pull request + +İndi çəkmə tələbini (pull request) göndərin. + +submit pull request + +Tezliklə bütün dəyişikliklərinizi bu layihənin master filialına birləşdirəcəyəm. Dəyişikliklər birləşdirildikdən sonra bildiriş e-poçtu alacaqsınız. + +## Bundan sonra nə edə bilərəm? + +Təbriklər! Töhfə olaraq tez-tez qarşılaşacağınız standart _fork -> clone -> edit -> pull request_ tamamlamısınız! + +Töhfənizi qeyd edin və [veb tətbiqə](https://firstcontributions.github.io/#social-share) girərək dostlarınız və izləyicilərinizlə bölüşün. + +Hər hansı bir köməyə ehtiyacınız və ya suallarınız olarsa, [Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) komandamıza qoşula bilərsiniz. + +İndi başqa layihələrə töhfə verməyə başlayaq. Başlaya biləcəyiniz asan məsələləri olan layihələrin siyahısını hazırladıq, [siyahıya baxın](https://firstcontributions.github.io/#project-list). + +### [Əlavə Məlumat](additional-material/git_workflow_scenarios/additional-material.md) + +## Digər alətlərin istifadəsi üçün təlimlər + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.bg.md b/translations/README.bg.md new file mode 100644 index 00000000000..90811f838fa --- /dev/null +++ b/translations/README.bg.md @@ -0,0 +1,124 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Първи стъпки + +Трудно е. Когато правиш нещо за пръв път винаги е трудно. Още повече, когато се работи съвместно с други хора. Затова решихме да опростим процеса на учене за новобранците в допринасянето към отворен софтуеър. + +Четенето на статии и гледането на видео уроци помага, но има ли по-добър учител от практиката в защитена среда? Целта на този проект е да напътства и опрости първите стъпки на новобранците в участието и приноса към отворен софтуеър. Ако искате да направите първата си контрибуция и да станете част от обществото на отворен софтуеър, следвайте стъпките по-долу. + +#### *Ако не се чувствате комфортно използвайки command line (терминал), [ето и уроци за използването на програми с графичен интерфейс](#Уроци-за-иползването-на-други-приложения)* + + +fork this repository + +Ако нямате git на вашия компютър, [инсталирайте го]( https://help.github.com/articles/set-up-git/). + +## Направете Разклонение (Fork) на това хранилище (repository) + +Направете разклонение на хранилището като натиснете бутона "Fork" в горната част на тази страница. +Това ще направи копие на това хранилище във вашия GitHub профил. + +## Клонирайте това хранилище + +clone this repository + +Сега клонирайте локално на вашия компютър разклоненото хранилище. Отидете във вашия GitHub профил, отворете разклоненото хранилище, +кликнете на бутона 'Clone' и копирайте линка или натиснете иконката 'copy to clipboard' (копирай в клипборда). + +Отворете терминал и въведете следната команда + +``` +git clone "линка който току-що копирахте" +``` +като на мястото на "URL-а който току-що копирахте" (без кавичките) поставете линка към това хранилище (Вашето Разклонение на този проект). Вижте +предните стъпки за това как да се сдобиете с линка. +copy URL to clipboard + +Например: +``` +git clone https://github.com/this-is-you/first-contributions.git +``` +Като на мястото на `this-is-you` се намира вашето потребителско име. В тази стъпка вие направихте копие на съдържанието на GitHub хванилището на 'first contributions' във вашия компютър. + +## Създайте клон (branch) + +Стигнете до местоположението във вашия компютър, където копирахте хранилището (ако вече не се намирате там): + +``` +cd first-contributions +``` +Сега създайте клон използвайки командата `git checkout`: +``` +git checkout -b +``` + +Например: +``` +git checkout -b add-alonzo-church +``` +(Името на клона не е задължително да съдържа думата *add*, но е препоръчително, защото целта на този клон е да добавите името си към списък.) + +## Направете нужните промени и ги commit-нете + +Сега отворете файла `Contributors.md` в текстов редактор и добавете името си вн его. Не го добавяйте в началото или края на файла. Поставете го някъде посредата. Сега запазете промените. + +git status + + +Ако навигирате през терминала до директорията на проекта и въведете командата `git status`, ще видите че има променени файлове. + + +ДОбавете тези промени към клона, който създадохте, използвайки командата `git add`: + +``` +git add Contributors.md +``` + +Сега commit-нете тези промени с командата `git commit`: +``` +git commit -m "Add to Contributors list" +``` +като смените `` с вашето име. + +## Качете (Push) промените в GitHub + +Качете вашите промени като въведете командата `git push`: +``` +git push origin +``` +сменяйки `` с името на клона, който създадохте по-рано. + +## Предайте вашите промени за рецензия + +Ако отидете във вашето хранилище в GitHub, ще видите бутона `Compare & pull request`. Натиснете го. + +create a pull request + +Сега предайте вашите промени за рецензия. + +submit pull request + +Скоро аз ще слея (merge) всички ваши промени в главния клон (мастер branch) на този проект. Вие ще бъдете уведомени по електронната поща когато това се случи. + +## От тук накъде? + +Поздравления! Вие току що изпълнихте стандарните _fork -> clone -> edit -> PR_ операции, които ще срещнете като сътрудник! + +Отпразнувайте вашия принос и го споделете с приятели и последователи като посетите [уеб приложението](https://roshanjossey.github.io/first-contributions/#social-share). + +Можете да се присъедините към нашия slack team в случай, че имате допълнителни въпроси или нужда от помощ [Присъединете се към slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Време да започнете да допринасяте и към други приекти. Ние сме съставили списък с проекти съдържащи лесни проблеми, които са лесни за начало. Проверете [списъка от приекти в уеб приложението](https://roshanjossey.github.io/first-contributions/#project-list). + +### [Допълнителни материали](../additional-material/git_workflow_scenarios/additional-material.md) + + +## Уроци за иползването на други приложения + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.bih.md b/translations/README.bih.md new file mode 100644 index 00000000000..328c5d20e60 --- /dev/null +++ b/translations/README.bih.md @@ -0,0 +1,124 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Prvi doprinosi + +Ovaj projekat ima za cilj da pruži konkretne korake i olakša način na koji početnici prilažu svoje prve doprinose (eng. contributions). Ukoliko ste se prepoznali u tekstu iznad i zelite da probate i doprinesete ovome ili nekom drugom projektu, pratite slijedece korake. + +#### _Ukoliko niste bas sigurni u vas rad sa komandnom linijom/terminalom (terminal -> za macOs), [mozete koristit ovaj link kroz GUI alate.](#Uputstva-za-druge-alate)_ + +Napravite fork repozitorijuma + +Ukoliko nemate git instaliran na vašoj mašini, [instalirajte ga ovde](https://help.github.com/articles/set-up-git/). + +## Uradite fork repozitorijuma + +Uradite račvanje (fork) tako što ćete kliknuti na dugme _fork_ na vrhu stranice. Ovako pravite kopiju repozitorijuma na vašoj github stranici. + +## Klonirajte repozitorijum + +clone this repository + +Slijedeće, klonirajte repozitorijum koji ste prethodno račvali (fork). Posjetite svoj GitHub profil, otvorite repozitorijum koji ste račvali, kliknite na _clone_ (kloniraj/kopiraj) dugme i kliknite na ikonicu _copy to clipboard_. + +Otvorite terminal i upišite slijedece git komande: + +``` +git clone "url koji ste prethodno kopirali sa vaseg github profila" (bez navodnika i razmaka) +``` + +copy URL to clipboard + +Na primjer: + +``` +git clone https://github.com/ovo-ste-vi/first-contributions.git +``` + +Gdje je umjesto `ovo-ste-vi` upisano vaše _github_ korisničko ime. Ovim kopirate sadržaj repozitorijuma _first-contributions_ na vašu mašinu. + +## Pravljenje grane _branch_ + +Prebacite se u radni direktorij na vašoj mašini: + +``` +cd first-contributions (ili pratite gdje se tacno nalazi na vasoj masini) +``` + +Pa zatim napravite novo grananje _branch_ koristeći `git checkout` comandu: + +``` +git checkout -b +``` + +Na primer: + +``` +git checkout -b add-alonzo-church +``` + +(Naziv grane ne mora da sadrži _add_ na početku ili vase _ime_, ali je zgodno uključiti ga jer je svrha ove grane da doda vaše ime na listu. + +## Napravite potrebne izmjene i potvrdite promjene + +Otvorite `Contributors.md` fajl u tekst editoru i dodajte vaše ime. Nemojte dodavati ime na sam početak ili kraj. Stavite ga negdje u sredinu. Potom sačuvajte fajl. + +git status + +Ukoliko odete u radni direktorijum i izvršite komandu `git status`, primjetit ce te da postoje promjene. + +Dodajte ove promjene u granu koju ste gore napravili koristeći `git add` komandu: + +``` +git add Contributors.md +``` + +Sada potvrdite ove promjene koristeći `git commit` komandu: + +``` +git commit -m "Add to Contributors list" +``` + +Gdje umjesto `` upisujete svoje ime. + +## Push changes to GitHub + +Pošaljite izmjene u repozitorijum na GitHub nalogu `git push`: + +``` +git push origin +``` + +gdje umjesto `` stavljate ime vašeg grananja koje ste prethodno napravili. + +## Pošaljite izmjene na reviziju + +Ukoliko odete na repozitorijum na vašem GitHub profilu primetićete `Compare & pull request` Dugme. Kliknite na njega. + +create a pull request + +a potom pošaljite zahtjev klikom na dugme _Create pull request_. + +submit pull request + +Nakon toga, admin će spojiti promjene koje ste napravili sa master granom projekta. Dobićete mejl potvrde kada se grane spoje. + +## Šta dalje? + +Čestitamo! Završili ste standardni _fork -> clone -> edit -> PR_ tok koji će vas pratiti kroz vaš čitav programerski život! + +Proslavite tako što ćete podjeliti vaš doprinos sa prijateljima i pratiocima otvaranjem [stranice](https://firstcontributions.github.io/#social-share). + +Pridružite se i našem Slack timu u slučaju da vam je potrebna ikakva pomoć ili imate bilo kakvih pitanja. [Slack tim](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +A sada, možemo početi sa doprinosima drugim projektima. Napravili smo spisak projekata sa jednostavnim problemima na kojima možete početi da radite. Posetite stranicu sa [the list of projects na našem sajtu](https://firstcontributions.github.io/#project-list). + +### [Dodatni materijali](../additional-material/git_workflow_scenarios/additional-material.md) + +## Uputstva za druge alate + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.bn.md b/translations/README.bn.md new file mode 100644 index 00000000000..c1570746ee8 --- /dev/null +++ b/translations/README.bn.md @@ -0,0 +1,122 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# প্রথম অবদান + +প্রথমবারের মত কোন কাজ করতে গেলে তা কঠিন বলেই মনে হবে। আর আপনি যদি অন্যদের কাজে সহযোগিতা করেন, তাহলে ভুলভ্রান্তিগুলো অত্যন্ত বিব্রতকর। অথচ 'ওপেন সোর্স'-এর মূল বিষয়টিই হচ্ছে পারস্পরিক সহযোগিতা ও একত্রে কাজ করা। আমরা চাই ওপেন সোর্সে অবদান রাখতে ইচ্ছুক নবীনরা যেন সহজেই শিখতে পারে এবং প্রথমবারের মত তাদের অবদান রাখতে পারে। + +প্রবন্ধ পড়ে এবং টিউটোরিয়াল দেখে অনেক কিছুই শেখা যায়, কিন্তু ব্যবহারিক পদ্ধতিতে কাজ করার চেয়ে ভালো কিছু হতে পারে না। এই প্রজেক্টের লক্ষ্য হচ্ছে নবীনদের দিকনির্দেশনা দেওয়া আর সেই সাথে তাদের প্রথম অবদান রাখার কাজটি সহজ করে তোলা। আপনি যদি ওপেন সোর্সে আপনার প্রথম অবদান রাখতে চান, তাহলে নিচের সহজ ধাপগুলো অনুসরণ করুন। কথা দিচ্ছি, এই প্রক্রিয়াটি অত্যন্ত মজার ও আনন্দদায়ক। + +#### _কমান্ড লাইন ইন্টারফেস এ স্বাচ্ছন্দ্য বোধ না করলে, [এখান থেকে গ্রাফিকাল ইন্টারফেস দিয়ে কিভাবে কাজ টি করতে হয় তার টিউটোরিয়াল দেখুন।](#অন্যান্য-টুল-ব্যবহারের-টিউটোরিয়াল)_ + + +fork this repository + +আপনার কম্পিউটারে গিট না থাকলে, [ ইনস্টল করুন ](https://help.github.com/articles/set-up-git/)। + +## এই রিপোজিটরি ফর্ক করুন + +এই পৃষ্ঠার উপরের অংশে ফর্ক (fork) বাটনে ক্লিক করে এই রিপোজিটরি ফর্ক করুন। +এই প্রক্রিয়ায় আপনার অ্যাকাউন্টে এই রিপোজিটরির একটি কপি তৈরি হবে। + +## রিপোজিটরি ক্লোন করুন + +clone this repository + +এখন এই রিপোজিটরিটি আপনার কম্পিউটারে ক্লোন করুন। এজন্যে প্রথমে ক্লোন(Clone) বাটনে ক্লিক করুন। এরপর ক্লিক করুন _ক্লিপবোর্ডে কপি করুন(copy to clipboard)_ আইকনটিতে। + +আপনার টার্মিনাল (উইন্ডোজের ক্ষেত্রে কমান্ড প্রম্পট (CMD)) চালু করুন এবং নিচের কমান্ড রান করুন: + +``` +git clone "url you just copied" +``` + +যেখানে "url you just copied" (উদ্ধৃত চিহ্ণ ব্যতীত) হচ্ছে এই রিপোজিটরির ইউআরএল যা আপনি পূর্বের ধাপেই পেয়েছেন। + +copy URL to clipboard + +উদাহরণ: + +``` +git clone https://github.com/this-is-you/first-contributions.git +``` + +এখানে `this-is-you` হচ্ছে আপনার গিটহাব ইউজারনেম। এই কমান্ডটির মাধ্যমে গিটহাবে অবস্থিত first-contributions রিপোজিটরির একটি কপি তৈরি হচ্ছে আপনার কম্পিউটারে। + +## একটি ব্রাঞ্চ তৈরি করুন + +আপনার কম্পিউটারে রিপোজিটরির ডিরেক্টরিতে যান (যদি এখনো অন্য ডিরেক্টরিতে থাকেন): + +``` +cd first-contributions +``` + +এখন `git switch` কমান্ডের মাধ্যমে একটি ব্রাঞ্চ তৈরি করুন: + +``` +git switch -c +``` + +উদাহরণ: + +``` +git switch -c add-alonzo-church +``` + +(ব্রাঞ্চের নামে _add_ শব্দটি যুক্ত থাকা জরুরী নয়। তবে এই ব্রাঞ্চের উদ্দেশ্য যেহেতু আপনার নাম তালিকাভুক্ত করা, সেহেতু _add_ শব্দটি যুক্ত থাকাই কাম্য।) + +## প্রয়োজনীয় পরিবর্তন করুন ও পরিবর্তনগুলো কমিট করুন + +এখন যে কোন টেক্সট এডিটরে `Contributors.md` ফাইলটি খুলুন, এতে আপনার নাম যুক্ত করুন, অতঃপর ফাইলটি সেভ করুন। এবার প্রজেক্ট ডিরেক্টরি থেকে `git status` কমান্ড রান করলে আপনি পরিবর্তনগুলো দেখতে পাবেন। `git add` কমান্ড দ্বারা এই পরিবর্তনগুলো আপনার তৈরি ব্রাঞ্চে যুক্ত করুন: + +``` +git add Contributors.md +``` + +এরপর `git commit` কমান্ড ব্যবহার করে এই পরিবর্তনগুলো কমিট করুন: + +``` +git commit -m "Add to Contributors list" +``` + +``-এর বদলে আপনার নাম লিখতে ভুলবেন না। + +## পরিবর্তনগুলো গিটহাবে পুশ করা + +`git push` কমান্ড ব্যবহার করে পরিবর্তনগুলো পুশ করুন: + +``` +git push origin -u +``` + +এক্ষেত্রে ``-এর বদলে পূর্বে আপনার তৈরি ব্রাঞ্চের নাম লিখুন। + +## রিভিউয়ের জন্য আপনার পরিবর্তনগুলো জমা দিন + +আপনার গিটহাব রিপোজিটরিতে `Compare & pull request` বাটনে ক্লিক করুন। + +create a pull request + +এখন _পুল রিকোয়েস্ট_ সাবমিট করুন। + +submit pull request + +আমি যথা শীঘ্র সম্ভব আপনার পরিবর্তনগুলো এই প্রজেক্টের মাস্টার ব্রাঞ্চে মার্জ করব। মার্জ করা সম্পন্ন হলে আপনি একটি নিশ্চিতকরণ ই-মেইল পাবেন। + +## এরপর কী করব? + +আপনার অবদানের আনন্দ উপভোগ করুন এবং [ওয়েব অ্যাপ](https://roshanjossey.github.io/first-contributions/#social-share)-এর মাধ্যমে বন্ধু ও অনুসরণকারীদের সাথে শেয়ার করুন। + +কোন সহায়তার প্রয়োজন হলে বা আপনার কোন প্রশ্ন থাকলে আপনি আমাদের স্ল্যাক টিমে যুক্ত হতে পারেন। [স্ল্যাক টিমে যোগ দিন](https://firstcontributions.herokuapp.com) + +এখন আপনি অন্যান্য প্রজেক্টগুলোতেও অবদান রাখতে পারেন। আপনার সুবিধার্থে আমরা সহজ সমস্যা সম্বলিত প্রজেক্টগুলোর একটি তালিকা তৈরি করেছি। ওয়েব অ্যাপে [প্রজেক্টগুলোর তালিকা](https://roshanjossey.github.io/first-contributions/#project-list) দেখুন। + +### [ অতিরিক্ত উপাদানসমূহ ](../additional-material/git_workflow_scenarios/additional-material.md) + +## অন্যান্য টুল ব্যবহারের টিউটোরিয়াল + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [গিটহাব ডেস্কটপ](../gui-tool-tutorials/github-desktop-tutorial.md) | [ভিজুয়াল স্টুডিও ২০১৭](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [গিটক্র্যাকেন](../gui-tool-tutorials/gitkraken-tutorial.md) | [ভিজুয়াল স্টুডিও কোড](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [আটলাসিয়ান সোর্সট্রি](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [ইন্টেলিজ আইডিয়া](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.by.md b/translations/README.by.md new file mode 100644 index 00000000000..2aa05668615 --- /dev/null +++ b/translations/README.by.md @@ -0,0 +1,151 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Першы ўклад у праект + +Складана. Заўсёды складана пачынаць нешта з самага пачатку. Даволі непрыемна рабіць памылкі, асабліва калі вы працуеце ў камандзе. Увесь open source складаецца з супрацоўніцтва і сумеснай працы. Мы хочам аблегчыць першыя крокі ў навучанні і супрацоўніцтве пачаткоўцам распрацоўнікам. + +Чытанне артыкулаў і падручнікаў можа дапамагчы, але што можа быць лепш, чым сапраўдны практычны вопыт, без рызыкі што-небудзь сапсаваць. Мэта гэтага праекта - належным чынам накіраваць маладых навабранцаў, а таксама даць ім магчымасць зрабіць іх першы ўклад. Памятаеце: чым менш вы напружаныя, тым лепш вы вучыцеся. Калі вы шукаеце магчымасць ажыццявіць свой першы ўклад, проста прытрымлівайцеся простым крокам, размешчаным ніжэй. Абяцаем, будзе цікава. + +fork this repository + + +Калі ў вас не ўсталяваны git на кампутары, [ ўсталюйце яго ]( https://help.github.com/articles/set-up-git/ ) + +## Стварыце асобную галінку + +Стварыце асобную галінку, націснуўшы на кнопку `fork` зверху гэтай старонкі. Такім чынам вы створыце копію гэтага рэпазітара ў сваім запісе. + +## Капіюйце рэпазітар + +clone this repository + +Цяпер каб скапіяваць ваш рэпазітар на персанальны кампутар. Націсніце на кнопку `clone`, а затым на абразок `copy to clipboard`, каб скапіяваць спасылку. + +Адкрыйце тэрмінал і запусціце наступную git каманду: + +``` +git clone "url you just copied" +``` +Дзе "url you just copied" (без двукоссяў) гэта спасылка на ваш рэпазітар. Паглядзіце папярэднія крокі, каб атрымаць гэтую спасылку. + +copy URL to clipboard + +Напрыклад: +``` +git clone https://github.com/this-is-you/first-contributions.git +``` +Дзе `this-is-you` ваш лагін на github. Такім чынам вы капіруеце рэпазітар 'first-contributions' з GitHub на ваш персанальны кампутар. + +## Стварыце галінку + +Перайдзіце ў каталог рэпазітара на вашым кампутары, калі вы яшчэ не там. + +``` +cd first-contributions +``` +Цяпер стварыце галінку, з дапамогай `каманды git checkout` + +``` +git checkout -b +``` + +Напрыклад: +``` +git checkout -b add-alonzo-church +``` +(Сінтаксічную не патрабуецца, каб назва галіны ўтрымлівала слова * add *, але гэта апраўдана, паколькі падкрэслівае прызначэнне гэтай галіны - дадаць ваша імя ў спісы.) + +## Занясіце неабходныя змены і стварыце commit + +Цяпер адкрыйце файл `Contributors.md` ў вашым тэкставым рэдактары, запішыце ваша імя і захавайце файл. Калі вы пяройдзеце ў дырэкторыю праекта і выканайце `git status`, вы ўбачыце змены. Дадайце гэтыя змены з дапамогай каманды `git add`. + +``` +git add Contributors.md +``` + +Цяпер занясіце дадзеныя змены з дапамогай каманды `git commit`. +``` +git commit -m "Add to Contributors list" +``` +Зменіце `` на ваша імя + +## Занясіце дадзеныя змены на github + +Занясіце вашыя змены з дапамогай каманды `git push` +``` +git push origin +``` +Зменіце `` на імя галіны, якую вы стварылі раней. + +## Пацвердзіце змены для праверкі вашага кода + +Калі вы зойдзеце ў свой рэпазітар на GitHub, вы ўбачыце кнопку `Compare & pull request`. Націсніце на яе. + +create a pull request + +Цяпер пацвердзіце pull-request. + +submit pull request + +Хутка я ўчыню аб'яднанне ўсіх вашых змяненняў з асноўнай галіной гэтага праекта. Вы атрымаеце паведамленне па электроннай пошце, калі змены будуць прынятыя (ўнесены ў галоўную галіну). + +Асноўная галіна вашага рэпазітара не будзе зменена. Для сінхранізацыі выканайце крокі, размешчаныя ніжэй. + +## Сінхранізуецца ваша адгалінаванне з дадзеным рэпазітаром + +Перш за ўсё перайдзіце ў асноўную галіну: +``` +git checkout master +``` +Затым дадайце url майго рэпазітара ў полі `upstream remote url`: +``` +git remote add upstream https://github.com/Roshanjossey/first-contributions +``` +Такім чынам мы паведамім git, што існуе іншая версія дадзенага праекта па пэўнай спасылцы, і мы яе лічым майстрам. Як толькі змены смержены, падгрузіць новую версію майго рэпазітара. +``` +git fetch upstream +``` + +Такім чынам мы забралі ўсе змены ў маім адгалінаванні (upstream remote). Пасля, вам трэба зліць новую версію майго рэпазітара з вашай майстар-галіной. +``` +git rebase upstream/master +``` +Так вы ўжываеце ўсе змены, якія вы падцягнулі да вашай майстар-галіны. Калі вы запушите зараз майстар-галіна, ваша адгалінаванне таксама будзе ўтрымліваць змены. +``` +git push origin master +``` +Звярніце ўвагу, што вы робіце push ў выдаленай рэпазітар origin. + +На гэтым этапе я аб'яднаў вашу галіну `` са сваёй майстар-галіной, а вы аб'ядналі сваю майстар-галіна з маёй. Ваша галіна больш не патрэбна, вы можаце выдаліць яе: +``` +git branch -d +``` +Таксама можаце выдаліць яе версію ў аддаленым рэпазітары: +``` +git push origin --delete +``` +Гэта зусім не абавязкова, але назва гэтай галіны адлюстроўвае яе даволі спецыфічнае прызначэнне. І працягласць яе жыцця можа быць адпаведна кароткай. + +## Выкарыстанне іншых інструментаў + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + + +## Што далей? + +Ніжэй некалькі папулярных рэпазітароў, дзе вы можаце знайсці заданні для пачаткоўцаў. Наперад, перайдзіце ў рэпазітары, каб даведацца больш. + +| [![exercism](https://avatars2.githubusercontent.com/u/5624255?v=3&s=100)](https://github.com/exercism/exercism.io/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+patch%22) | [![fun-retro](https://avatars3.githubusercontent.com/u/15913975?v=3&s=100)](https://github.com/funretro/distributed/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly) | [](https://github.com/facebook/react/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+bug%22) | [![habitat](https://avatars1.githubusercontent.com/u/18171698?v=3&s=100)](https://github.com/habitat-sh/habitat/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [![scikit-learn](https://avatars0.githubusercontent.com/u/365630?v=3&s=100)](https://github.com/scikit-learn/scikit-learn/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [](https://github.com/technomancy/leiningen/issues?q=is%3Aopen+is%3Aissue+label%3ANewbie) | [](https://github.com/numpy/numpy/issues?q=is%3Aopen+is%3Aissue+label%3A%22Easy+Fix%22) | [![elasticsearch](https://avatars2.githubusercontent.com/u/6764390?v=3&s=100)](https://github.com/elastic/elasticsearch/issues?q=is%3Aopen+is%3Aissue+label%3A%22low+hanging+fruit%22) | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [exercism](https://github.com/exercism/exercism.io/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+patch%22) | [Fun Retros](https://github.com/funretro/distributed/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly) | [react](https://github.com/facebook/react/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+bug%22) | [habitat](https://github.com/habitat-sh/habitat/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [scikit-learn](https://github.com/scikit-learn/scikit-learn/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [Leiningen](https://github.com/technomancy/leiningen/issues?q=is%3Aopen+is%3Aissue+label%3ANewbie) | [numpy](https://github.com/numpy/numpy/issues?q=is%3Aopen+is%3Aissue+label%3A%22Easy+Fix%22) | [elasticsearch](https://github.com/elastic/elasticsearch/issues?q=is%3Aopen+is%3Aissue+label%3A%22low+hanging+fruit%22) | +| [![homebrew](https://avatars2.githubusercontent.com/u/1503512?v=3&s=100)](https://github.com/Homebrew/brew/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) | [![rust](https://avatars1.githubusercontent.com/u/5430905?v=3&s=100)](https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Aissue+label%3AE-easy) | [![vuejs](https://avatars1.githubusercontent.com/u/6128107?v=3&s=100)](https://github.com/vuejs/vue/issues?q=is%3Aopen+is%3Aissue+label%3A%22contribution+welcome%22) | [![Suave](https://avatars2.githubusercontent.com/u/5822862?v=3&s=100)](https://github.com/SuaveIO/suave/issues?q=is%3Aopen+is%3Aissue+label%3Ahardness-easy) | [![OpenRA](https://avatars3.githubusercontent.com/u/409046?v=3&s=100)](https://github.com/OpenRA/OpenRA/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [![PowerShell](https://avatars0.githubusercontent.com/u/11524380?v=3&s=100)](https://github.com/powershell/powershell/issues?q=is%3Aopen+is%3Aissue+label%3AUp-for-Grabs) | [![coala](https://avatars2.githubusercontent.com/u/10620750?v=3&s=100)](https://github.com/coala/coala/issues?q=is%3Aopen+is%3Aissue+label%3Adifficulty%2Flow+label%3Adifficulty%2Fnewcomer) | [![moment](https://avatars2.githubusercontent.com/u/4129662?v=3&s=100)](https://github.com/moment/moment/issues?q=is%3Aopen+is%3Aissue+label%3AUp-For-Grabs) | +| [homebrew](https://github.com/Homebrew/brew/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) | [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Aissue+label%3AE-easy) | [vuejs](https://github.com/vuejs/vue/issues?q=is%3Aopen+is%3Aissue+label%3A%22contribution+welcome%22) | [Suave](https://github.com/SuaveIO/suave/issues?q=is%3Aopen+is%3Aissue+label%3Ahardness-easy) | [OpenRA](https://github.com/OpenRA/OpenRA/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [PowerShell](https://github.com/powershell/powershell/issues?q=is%3Aopen+is%3Aissue+label%3AUp-for-Grabs) | [coala](https://github.com/coala/coala/issues?q=is%3Aopen+is%3Aissue+label%3Adifficulty%2Flow+label%3Adifficulty%2Fnewcomer) | [moment](https://github.com/moment/moment/issues?q=is%3Aopen+is%3Aissue+label%3AUp-For-Grabs) | +| [![ava](https://avatars0.githubusercontent.com/u/8527916?v=3&s=100)](https://github.com/avajs/ava/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+for+beginner%22) | [![freeCodeCamp](https://avatars0.githubusercontent.com/u/9892522?v=3&s=100)](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only) | [![webpack](https://avatars3.githubusercontent.com/u/2105791?v=3&s=100)](https://github.com/webpack/webpack/issues?q=is%3Aopen+is%3Aissue+label%3A%22D1%3A+Easy+%28Contrib.+Difficulty%29%22) | [![hoodie](https://avatars1.githubusercontent.com/u/1888826?v=3&s=100)](https://github.com/hoodiehq/hoodie/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only) | [![pouchdb](https://avatars3.githubusercontent.com/u/3406112?v=3&s=100)](https://github.com/pouchdb/pouchdb/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) | [![neovim](https://avatars0.githubusercontent.com/u/6471485?v=3&s=100)](https://github.com/neovim/neovim/issues?q=is%3Aopen+is%3Aissue+label%3Aentry-level) | [![babel](https://avatars2.githubusercontent.com/u/9637642?v=3&s=100)](https://github.com/babel/babel/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly) | [](https://github.com/adobe/brackets/labels/Starter%20bug) | +| [ava](https://github.com/avajs/ava/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+for+beginner%22) | [freeCodeCamp](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only) | [webpack](https://github.com/webpack/webpack/issues?q=is%3Aopen+is%3Aissue+label%3A%22D1%3A+Easy+%28Contrib.+Difficulty%29%22) | [hoodie](https://github.com/hoodiehq/hoodie/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only) | [pouchdb](https://github.com/pouchdb/pouchdb/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) | [neovim](https://github.com/neovim/neovim/issues?q=is%3Aopen+is%3Aissue+label%3Aentry-level) | [babel](https://github.com/babel/babel/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly) | [brackets](https://github.com/adobe/brackets/labels/Starter%20bug) | +| [![Node.js](https://avatars1.githubusercontent.com/u/9950313?v=3&s=100)](https://github.com/nodejs/node/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22) | [](https://github.com/Semantic-Org/Semantic-UI-React/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22) | +| [Node.js](https://github.com/nodejs/node/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22) | [Semantic-UI-React](https://github.com/Semantic-Org/Semantic-UI-React/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22) | diff --git a/translations/README.ca.md b/translations/README.ca.md new file mode 100644 index 00000000000..f2b095cd54e --- /dev/null +++ b/translations/README.ca.md @@ -0,0 +1,122 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Primeres Contribucions + +És difícil. Sempre ho és, quan es fa quelcom per primera vegada. Sobretot quan es col·labora amb altres, ja que equivocar-se no és gens agradable. Volem simplificar la manera d'aprendre a contribuir i col·laborar en projectes de codi obert per primera vegada. + +Llegir articles i mirar tutorials pot ser útil, però què millor que fer les coses en un entorn pràctic real? Aquest projecte és una guia per a principiants que vol simplificar la primera contribució a projectes de codi oberts. Si vols fer la teva primera contribució, segueix les instruccions que es mostren a continuació: + +#### *Si no et sents còmode/a amb la línia d'ordres (*Command Line*), [aquí trobaràs tutorials utilitzant eines que tenen Interfície Gràfica (GUI)](#Tutorials-amb-Altres-Eines)* + +fer fork d'aquest repositori + +Si no tens git al teu ordinador, l'hauràs d'[instal·lar]( https://help.github.com/articles/set-up-git/). + +## Bifurca (*Fork*) aquest respositori + +Fes una *fork* d'aquest repositori clicant al botó "*Fork*" a la part superior dreta d'aquesta pàgina. +Això crearà una còpia d'aquest repositori al teu compte de GitHub. + +## Clona (*Clone*) el repositori + +clonar aquest repositori + +Clona aquest repositori al teu ordinador: ves al teu compte de GitHub, fes clic al botó clonar "*clone or download*" del repositori, i després clica a la icona de *copiar al porta-retalls*. + +Obre una terminal/línia d'ordre i executa el següent comandament de git: + +``` +git clone "url que acabes de copiar" +``` +on "url que acabeu de copiar" (sense cometes dobles) és la *url* per a aquest repositori (la vostra bifurcació o *fork* d'aquest projecte). Per obtenir la *url*, torna als passos anteriors. + +copiar URL al porta-retalls + +Per exemple: +``` +git clone https://github.com/aquest-soc-jo/first-contributions.git +``` +on `aquest-soc-jo` és el teu nom d'usuari de GitHub. En aquest pas, estàs copiant el contingut del repositori *first-contributions* de GitHub al teu ordinador. + +## Crea una branca (*branch*) + +Canvieu al directori del repositori del vostre ordinador (si no hi esteu allà ja): + +``` +cd first-contributions +``` +Crea una nova branca (*branch*) utilitzant el comandament `git checkout`: +``` +git checkout -b +``` + +Per exemple: +``` +git checkout -b add-nom-cognom +``` +(No fa falta que el nom de la branca contingui la paraula *add* però és recomanable, ja que l'objectiu d'aquesta branca és afegir el teu nom a la llista.) + +## Fes els canvis necessaris i confirma (*commit*) els canvis + +Obre l'arxiu `Contributors.md` en un editor de text i afegeix-hi el teu nom. No l'afegeixis ni al principi, ni al final de l'arxiu. Posa'l en qualsevol altre posició. Llavors desa l'arxiu. + +git status + + +Ara, si vas al directori del projecte i executes el comandament `git status`, veuràs els canvis. + + +Afegeix aquests canvis a la branca que acabes de crear utilitzant el comandament `git add`: + +``` +git add Contributors.md +``` + +Confirma (*commit*) els canvis utilitzant el comandament `git init`: +``` +git commit -m "Add to Contributors list" +``` +reemplaçant `` amb el teu nom. + +## Empeny (*Push*) els canvis cap a GitHub + +Envia els canvis utilitzant el comandament `git push`: +``` +git push origin +``` +reemplaçant `` amb el nom de la branca que has creat anteriorment. + +## Envia (*Submit*) els canvis per tal que siguin revisats + +Si ara vas al teu respositori a GitHub, veuràs un botó `Compare & pull request` (Compara i fes una solicitud d'incorporació). Fes clic en aquest botó. + +crear una pull request + +Envia la solicitud d'incorporació (*pull request*). + +envia la pull request + +Quan un administrador vegi la solicitud, la revisarà i incorporarà els teus canvis a la branca principal (*main branch*) del projecte. Rebràs una notificació per correu electrònic quan els canvis s'hagin incorporat. + +## I ara què? + +Enhorabona! Acabes de completar el procés de treball principal que et trobaràs com a col·laborador de projectes de codi obert: *_fork -> clone -> edit -> PR_*. + +Ara, celebra la teva contribució i comparteix-la amb els teus amics i seguidors anant a [la web](https://roshanjossey.github.io/first-contributions/#social-share). + +Podeu unir-vos al nostre equip d'*slack* en cas de que necessiteu ajuda o tingueu alguna pregunta. [Unir-se a l'equip d'slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +A continuació, et pots preparar per contribuir a altres projectes. Hem reunit una llista de projectes amb tasques (*issues*) pendents fàcils per tal de poder començar. Fes un cop d'ull a [la llista de projectes aquí](https://roshanjossey.github.io/first-contributions/#project-list). + +### [Material extra](../additional-material/git_workflow_scenarios/additional-material.md) + + +## Tutorials utilitzant altres eines + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](https://www.jetbrains.com/idea/download/#section=windows) | diff --git a/translations/README.cs.md b/translations/README.cs.md new file mode 100644 index 00000000000..6d83aa5a304 --- /dev/null +++ b/translations/README.cs.md @@ -0,0 +1,127 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# První příspěvek + +Život je těžký. Obzvláště když něco děláte poprvé. V případě, že na něčem spolupracujete, není dělání chyb něco, co by vám dělalo radost. My bychom rádi zjednodušili cestu novým přispěvovatelům do open-source při jejich učení se jak na to. + +Čtení článků nebo zhlédnutí video návodů jsou také cesty, ale co je lepší než si danou věc přímo osahat na vlastní kůži v reálném prostředí? Tento projekt je zaměřen na poskytnutí pomoci začátečníkům s jejich prvním přispěním do open-source. Pokud jste jím právě vy, následujte kroky popsané níže. + +#### *Pokud nemáte rádi příkazovou řádku, [zde najdete návody na použití nástrojů s GUI (grafické uživatelské rozhraní)](#Návod-za-použití-dalších-nástrojů)* + + +forkněte tento repozitář + +Pokud namáte nainstalovaný git, [nainstalujte si jej]( https://help.github.com/articles/set-up-git/). + +## Forkněte tento repozitář + +Forkněte (vytvoření kopie z originálu, z anglického *fork* – *vidlička*, jako vytvoření nové odnože) tento repozitář kliknutím na tlačítko **Fork** nahoře na této stránce. Tím vytvoříte kopii tohoto repozitáře na svém vlastním GitHub účtu. + +## Naklonujte repozitář + +naklonujte tento repozitář + +Nyní naklonujte (anglicky *clone*) forknutý repozitář na váš počítač, naklonování není nic jiného než stáhnutí obrazu repozitáře k vám na počítač. Na vašem GitHub účtu si otevřete forknutý repozitář, klikněte na tlačítko **Clone or download** a následně v okýnku, které se objeví, klikněte na tlačítko s ikonkou **copy to clipboard** vedle URL adresy, čímž si ji zkopírujete do schránky. + +Teď otevřete terminál a spusťte následující příkaz: + +``` +git clone "url které jste právě zkopírovali" + +``` + +zkopírujte adresu do schránky + +Například: + +``` +git clone https://github.com/vase-username/first-contributions.git +``` + +Tímto na svém počítači vytvoříte složku se soubory daného repozitáře. + +## Vytvořte větev + +V příkazové řádce se přepněte do složky s repozitářem (pokud v ní už nejste) + +``` +cd first-contributions +``` + +Nyní vytvořte novou větev (anglicky *branch*) za použití příkazu `git checkout`: + +``` +git checkout -b +``` + +Například: +``` +git checkout -b pridani-meho-jmena +``` + +Jméno větve by mělo vypovídat o tom, co kód nebo cokoliv jiného do ní přidané bude dělat/vykonávat, případně proč se daná věc děje. + +## Udělejte změny a zaznamenejte je + +Otevřete soubor `Contributors.md` v textovém editoru a přidejte do něj své jméno. Napiště jej někam doprostřed a soubor uložte. + +git status + +Pokud teď v příkazové řádce spustíte příkaz `git status`, uvidíte jaké změny byly v repozitáři provedeny. + +Tyto změny do dané větvě přidáte příkazem `git add`: + +``` +git add Contributors.md +``` + +Zbývá už jen potvrdit (anglicky *commit*) změny příkazem `git commit`: + +``` +git commit -m "Add to Contributors list" +``` + +Za přepínač `-m` se píše co dané změny představují, popis by měl být jednoduchý ale výstižný. + +## Protlačte změny na GitHub + +Nyní změny provedené lokálně na počítači protlačíme (anglicky *push*) na GitHub příkazem `git push`: + +``` +git push origin +``` + +## Předložte své změny k posouzení + +Pokud se nyní podíváte do svého GitHub repozitáře, uvidíte tlačítko **Compare & pull request**. Klikněte na něj. + +vytvořte pull request + +Teď vytvořte žádost o přetažení vaší větve do originálního repozitáře (anglicky *pull request*). + +potvrďte pull request + +Brzy budou správci provádět zapracování vašich změn do hlavní (anglicky *master*) větve tohoto projektu. Až se do ní vaše změny dostanou, dostanete e-mailové upozornění. + +## Kam dále? + +Blahopřejeme! Právě jste dokončili standardní _fork -> clone -> edit ->_ průběh práce (anglicky *workflow*), se kterým se jako přispěvatel do projektů setkáte dennodenně. + +Oslavte svůj první příspěvek se svými přáteli a následovníky přes [webovou aplikaci](https://roshanjossey.github.io/first-contributions/#social-share). + +V případě, že byste měli jakékoliv otázky nebo potřebovali pomoct, můžete se [přidat k našemu Slack teamu](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Nyní vám už nic nebrání v příspívání do ostatních projektů. Připravili jsme pro vás seznam projektů, které mají jednoduché záležitosti k vyřešení/naprogramování, se kterými můžete začít. Podívejte se [zde](https://roshanjossey.github.io/first-contributions/#project-list). + +### [Další materiály](../additional-material/git_workflow_scenarios/additional-material.md) + + +## Návod za použití dalších nástrojů + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.da.md b/translations/README.da.md new file mode 100644 index 00000000000..2f28bb575ed --- /dev/null +++ b/translations/README.da.md @@ -0,0 +1,123 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Første bidrag + +Det er svært. Det er altid svært når det er første gang. Specielt hvis man samarbejder er det ikke rart at begå fejl. Vi vil simplificere den store udfordring det er for nybegyndere at lære om open-source, og at lave deres første bidrag. + +At læse artikler og se video guides hjælper, men hvad er bedre end at bruge det i praksis? Dette projekt håber at kunne tilbyde vejledning og gøre det overkommeligt for alle at lave deres første open-source bidrag. + +#### *Hvis du ikke er komfortabel med command line, [her er vejledninger til GUI værktøjer](#Guides-med-andre-værktøjer)* + + +fork this repository + +Har du ikke Git på din maskine kan du [installere det]( https://help.github.com/articles/set-up-git/). + +## Fork dette repository + +Fork dette repo ved at klikke på "fork" knappen øverst på siden. +Dette vil lave en kopi af projektet i din Github konto. + +## Clone dette repository + +clone this repository + +Næste trin er at "clone" dit nye repository til din maskine. Naviger til din Github account og åbn dit nye repository, derefter find "clone" øverst oppe og tryk på knappen. Tryk *copy to clipboard* ikonet. + +Åbn en terminal og kør den følgende git command: + +``` +git clone "din url" +``` + +hvor "din url" skal erstattes med den URL du kopieret i forrige trin. + +copy URL to clipboard + +Eksempel: +``` +git clone https://github.com/dit-brugernavn/first-contributions.git +``` +Erstat 'dit-brugernavn' med dit GitHub brugernavn. Her kopierer vi indholdet af first-contributions repositoriet fra din Github konto, til din lokale PC. + +## Opret en branch + +Åbn en konsol og cd til dit lokale repository (hvis ikke du allerede er der): + +``` +cd first-contributions +``` +Derefter opretter du en branch med kommandoen `git checkout`: +``` +git checkout -b +``` + +Eksempel: +``` +git checkout -b add-alonzo-church +``` +(Navnet på din branch behøver ikke at indeholde ordet *add*, men det giver mening at inkludere det her da branchen er til for at tilføje dit navn til en liste med navne.) + +## Lav dine ændringer og commit dem + +Åben filen `Contributors.md` i en text editor og tilføj dit navn til listen. Undgå at tilføje dit navn øverst eller nederst på listen, men helst et sted i mellem. Når dette er gjort så gem filen. + +git status + + +Hvis du går til konsollen og kører kommandoen `git status`, vil du se dine ændringer. + + +Tilføj disse ændringer til din branch med kommandoen `git add`: +``` +git add Contributors.md +``` + +Derefter commit ændringerne med kommandoen `git commit`: +``` +git commit -m "Add to Contributors list" +``` +Erstat `` med dit Github brugernavn. + +## Push ændringer til Github + +Push dine ændringer til Github med kommandoen `git push`: +``` +git push origin +``` +Erstat `` med navnet på den branch du oprettede tidligere. + +## Indgiv ændringer til inspektion + +Hvis du går ind på dit repository på Github, så vil du se en `compare & pull request` knap. Klik på den. + +create a pull request + +Indgiv nu din pull request. + +submit pull request + +Snart vil jeg merge dine ændringer ind i master branch'en af projektet. Du vil modtage en notifikation per email når dine ændringer er blevet merget. + +## Hvor til nu? + +Tillykke! Du har nu gennemført den udbredte _fork -> clone -> edit -> PR_ workflow som du vil støde oftest på som contributor! + +Fejr dit bidrag og del det med dine venner og følgere ved at gå til [web app](https://roshanjossey.github.io/first-contributions/#social-share). + +Du er velkommen til at kigge forbi vores Slack hvis du mangler hjælp, eller har spørgsmål. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Tillad os også at hjælpe dig i gang med dine næste bidrag. Vi har kompileret en liste af projekter med letty, overkommelige problemer du kan starte ud med. Check den ud her: [the list of projects in web app](https://roshanjossey.github.io/first-contributions/#project-list). + +### [ekstra materiale](../additional-material/git_workflow_scenarios/additional-material.md) + + +## Guides med andre værktøjer + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.de.md b/translations/README.de.md new file mode 100644 index 00000000000..25734fad45b --- /dev/null +++ b/translations/README.de.md @@ -0,0 +1,114 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# First Contributions + +Repository forken + +Aller Anfang ist schwer. Gerade dann, wenn wir gemeinsam an etwas arbeiten, will niemand etwas Falsches tun. Aber Open Source dreht sich um Kooperation und lebt von den Beiträgen vieler Freiwilliger. Deshalb haben wir es uns zur Aufgabe gemacht, neuen Mitgliedern in der Open-Source-Gemeinde ihre ersten Schritte so einfach wie möglich zu machen. + +Natürlich helfen die vorhandenen Artikel und Videoanleitungen. Aber was kann besser sein, als es einfach einmal auszuprobieren mit dem Wissen, dass man nichts kaputt machen kann? Dieses Projekt will Anfängern zeigen, wie sie möglichst einfach ihren ersten Beitrag leisten. Bedenke: Je entspannter du bist, desto besser lernst du. Wenn du deinen ersten Beitrag leisten möchtest, folge diesen einfachen Schritten. Wir versprechen dir, es wird Spaß machen. + + +Wenn du Git noch nicht installiert hast, [ installiere es ]( https://help.github.com/articles/set-up-git/ ) + +## Repository forken + +Forke das Repository durch das Anklicken der Schaltfläche "Fork". Dadurch erhältst du deine eigene Version des Projektes in deinem Profil. + +## Repository klonen + +Repository klonen + +Klone das Repository auf deinen Computer. Klicke auf die Schaltfläche "Clone or download" und anschließend auf das "copy to clipboard"-Symbol. + +Öffne eine Kommandozeile und gib das folgende git-Kommando ein: + +``` +git clone "Deine kopierte URL" +``` +Statt 'Deine kopierte URL' (ohne Anführungszeichen) füge die Repository-URL aus dem vorherigen Schritt ein. + +URL kopieren + +Beispiel: +``` +git clone https://github.com/dein-Name/first-contributions.git +``` +An der Stelle 'dein-Name' muss dein GitHub-Username stehen. Mit diesem Befehl kopierst du den Inhalt deines first-contributions-Repository von GitHub auf deinen Computer. + +## Erstelle einen Branch + +Wechsle zum Repository-Verzeichnis auf deinem Computer (falls du es nicht schon getan hast). + +``` +cd first-contributions +``` +Erstelle nun einen Branch mit dem Befehl `git checkout`: +``` +git checkout -b +``` + +Beispiel: +``` +git checkout -b add-max-mustermann +``` + +(Der Name des Branches muss nicht unbedingt das Wort *add* beinhalten aber hier ist es sinnvoll, denn der Zweck deines Branches ist es ja, deinen Namen zur Liste hinzuzufügen.) + +## Mache die nötigen Änderungen und committe sie + +Öffne `Contributors.md` in einem Text-Editor und füge deine Namen hinzu. Beachte, dass du den Namen nicht am Anfang oder am Ende der Datei hinzufügst. Speichere die Datei anschließend. + +Gibst du in der Kommandozeile nun `git status` ein, siehst du die Änderungen. + +Füge die Änderungen mit dem Befehl `git add` zu deinem eben erstellten Branch hinzu: +``` +git add Contributors.md +``` + +Nun committest du deine Änderungen mit `git commit`: +``` +git commit -m "Add to Contributors list" +``` +Ersetze `` mit deinem Namen. + +## Pushe die Änderung zu GitHub + +Pushe die Änderungen mit `git push`: +``` +git push origin +``` +Ersetze `` mit dem Namen des Branches, den du zuvor erstellt hast. + +## Sende deine Änderungen zum Review + +Wenn du jetzt zu deinem Repository auf GitHub gehst, siehst du einen Knopf `Compare & pull request`. Klicke darauf. + +Erstelle einen pull request + +Erstelle einen Pull Request indem du auf die Schaltfläche `Create pull request` klickst. + +Pull Request senden + +Roshan Jossey wird nun deine Änderungen in den Master Branch dieses Projekts mergen. Du erhältst eine E-Mail sobald dies geschehen ist. + +## Wie geht es weiter? + +Glückwunsch! Du hast so eben den Standard-Workflow *Fork -> Clone -> Edit -> Pull Request* beendet, der dir als Mitwirkender häufig begegnen wird. + +Feiere deinen Beitrag zum Projekt und teile ihn mit deinen Freunden und Followern über unsere [Web-App](https://firstcontributions.github.io/#social-share). + +Wenn du weitere Fragen hast, kannst du Mitglied in unserem Slack-Team werden. [Join Slack Team](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Falls du jetzt zu anderen Projekten beitragen möchtest, dann haben wir für dich eine Liste von einfachen, ersten Issues zusammengestellt, an denen du arbeiten kannst. Diese Projekt-Liste findest du [in unserer Web-App](https://firstcontributions.github.io/#project-list). + +## Tutorials mit anderen Tools + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + diff --git a/translations/README.eg.md b/translations/README.eg.md new file mode 100644 index 00000000000..24435d0814a --- /dev/null +++ b/translations/README.eg.md @@ -0,0 +1,154 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) +#
مساهمتك الأولى
+ +
+الصعوبة متوقعة لما تبدأ أي مشروع جديد، خصوصاً لو كان المشروع بيتضمن ناس تانية، ودة بيخلي الوقوع في الخطأ مزعج ومتعب. +
+لكن المساهمة في مشاريع مفتوحة المصدر اسسها العمل الجماعي والعطاء. +
+في المشروع دة هدفنا هو تبسيط الطريق لأول مساهمة ليك. +
+ +
+ممكن تقرأ وتتفرج على فيديوهات على الإنترنت عشان تعرف تبدأ فى المساهمة للمشاريع مفتوحة المصدر، لكن هتستفيد أكتر لو عرفت تساهم في مشروع دلوقتي من غير خوف لحسن تعمل حاجة غلط. المشروع اللى انت فاتحه حاليا بيركز انه يوفرلك التوجيهات الأولية اللي هتحتجها عشان تبدأ أول مساهمة ليك. مش مشكلة تغلط المهم انك تتعلم من الغلط ودة الهدف هنا. تابع الخطوات واحدة واحدة ونوعدك انك هتستمتع. +
+ + +
+لو ماكنش عندك git على جهازك حمله من هنا. +
+ +##
أفصل المشروع دة - Fork this Repository
+fork this repository +
+خد نسخة من المشروع دة (أو افصله) عن طريق انك تدوس على Fork في أعلى الصفحة. +لو عملت كدة فأنت اخدت نسخة من الفولدر دة فى حسابك على github. +
+ +##
إنسخ المشروع دة - Clone the repository
+ +clone this repository + +
+انسخ المشروع دة لجهازك. +دوس على Clone بعدين دوس على أيقونة Copy to clipboard +
+copy URL to clipboard +
+إفتح التريمنال وأكتب الأمر دة: +
+ +``` +git clone "url you just copied" +``` + +
بدل "url you just copied" حط الرابط اللي نسخته من الخطوة اللي فاتت، الرابط دة بتاع المشروع.
+ +
على سبيل المثال:
+ +``` +git clone https://github.com/this-is-you/first-contributions.git +``` + +
+في المثال دة لاحظ ان 'this-is-you' هيكون إسم حسابك في موقع github، الأمر دة هينسخ محتويات المشروع لجهازك الخاص عشان تقدر تعدل عليه بحرية في أي وقت. +
+
+ +##
إنشاء فرع - Create a branch
+ + +
بما اننا عايزين نعمل تغيير فى الفايل اللى عملناله نسخة على الجهاز.. الأول ننتقل للفولدر اللي لسة نسخينه:
+ +``` +cd first-contributions +``` + +
قبل مانعمل التغيير هنعمل "فرع" وهنديله اسم زي كدة:
+ +``` +git checkout -b "add-your-name" +``` + +
هتحط اسمك بدل your-name
+ +
مثلا:
+ +``` +git checkout -b "add-alonzo-church" +``` + +
+ +##
غيّر التغيير اللي حابب تغيره:
+ +
+التغيير اللي هتغيره فى الحالة دي انك تحط اسمك فى نهاية قايمة الأسماء فى فايل. افتح فايل اسمه "Contributors.md" بالـ text editor المفضل ليك وحط إسمك و إحفظ الفايل. +بعد كدة ارجع للترمينال وأكتب الأمر دة git status الأمر دة بيظهر لك أي تغيرات حصلت في المشروع. +عشان تضيف التغيرات دي للفرع بتاعك هتستخدم الأمر دا git add. +
+ +``` +git add Contributors.md +``` + +
حتى الأن انت عندك فرع فيه التغيير، عشان تبعت التغيير دة وتتمه هيتعمل على خطوتين: الأولى انك تعمل للتغيير دة اسم فهتستخدم الأمر git commit.
+ +``` +git commit -m "Add to Contributors list" +``` + +
إستبدل <your-name> بإسمك.
+
+ +##
بعدين ترفع التغيررات - Push changes to Github
+ +
هترفع التغيررات عن طريق الأمر git push
+ +``` +git push origin "add-your-name" +``` + +
إستبدل <add-your-name> بإسم الفرع اللي انت لسة عامله .
+ + +
+

سلم تغيراتك للمراجعة

+ + +
في صفحة المشروع بتاعك على صفحتك الشخصية على github دوس على زرار Compare & pull request. هو ماكنش ظاهر قبل كدة.
+ +create a pull request + +
دلوقتي هتسلم طلبك لصاحب المشروع الأساسي عشان يراجع عليه، في الحالة دي الطلب بتاعك هيوصلي.
+ +submit pull request + +
بعد المراجعة هدمج تغيرراتك للفرع الرئيسي في المشروع. وهيتم تنبيهك عن طريق البريد الإلكتروني بدة.
+ +
لما يحصل وأقبل طلبك هتلاقي ان المشروع المنسوخ على حسابك مفيهوش التغيررات. فلازم تزامن المشروع الرئيسي باللي على حسابك بالخطوات دي:
+ + +##
طب اعمل ايه بعد كدة؟
+ +
+ احتفل بأول مساهمة ليك، أعمل شير مع صحابك ومتابعينك عن طريق زيارة الموقع دة. +
+ +
ممكن تنضم للفريق على Slack لو حابب تساعد او عندك أسئلة. إنضم للفريق على Slack
+ +
+ +
يلا نخليك تبدأ تساهم في مشاريع بجد؟ عملنا قائمة بمشاريع بمشاكل بسيطة ممكن تبدأ بيها النهاردة.
+ + +## + +##
لو هتستخدم ادوات تانية ممكن تتعلم من هنا
+ +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.en-pirate.md b/translations/README.en-pirate.md new file mode 100644 index 00000000000..d7da5e7d8ee --- /dev/null +++ b/translations/README.en-pirate.md @@ -0,0 +1,130 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# First Contributions + +'tis hard. 'tis always hard th' first time ye do somethin'. Especially when ye be collaboratin', makin' mistakes ain't a comfortable thin'. We wanted t' simplify th' way new open-source contributors learn & contribute fer th' first time. + +Readin' tales & watchin' tutorials can help, but wha''s better than actually doin' th' stuff in a practice environment? This project aims at providin' guidance & simplifyin' th' way beginners make thar first contribution. If ye be lookin' t' make yer first contribution, follow th' steps below. + +#### *If ye're nah comfortable wit' command line, [here be tutorials usin' GUI tools.](#Tutorials-Usin'-Other-Tools)* + +fork this repository + +If ye don't 'ave git on yer machine, [install it](https://help.github.com/articles/set-up-git/). + +## Fork this repository + +Fork this repo by skewerin' on th' fork button on th' top o' this page. +This will create a copy o' this repository in yer account. + +## Clone the repository + +clone this repository + +Now clone this repo t' yer machine. Go t' yer GitHub account, skewer on th' clone button 'n then skewer th' *copy to clipboard* icon. + +Open a terminal 'n run th' followin' git command: + +``` +git clone "url ye jus' copied" +``` + +where "url ye jus' copied" (without th' quote marks) be th' url t' this repository (yer fork o' this project). See th' previous steps t' obtain th' url. + +copy URL to clipboard + +Fer example: + +``` +git clone https://github.com/this-be-ye/first-contributions.git +``` + +where `this-be-ye` be yer GitHub username. Here ye're copyin' th' contents o' th' first-contributions repository in GitHub t' yer 'puter. + +## Create a branch + +Change t' th' repository directory on yer 'puter (if ye be nah already thar): + +``` +cd first-contributions +``` + +Now create a branch usin' th' `git checkout` command: + +``` +git checkout -b +``` + +Fer example: + +``` +git checkout -b add-luke-oliff +``` + +(Th' name o' th' branch does nah needs t' 'ave th' word *add* in it, but 'tis a reasonable thin' t' include 'cause th' purpose o' this branch be t' add yer name t' a list.) + +## Make necessary changes 'n commit those changes + +Now open `Contributors.md` file in a text editor, add yer name t' it. Don't add it at th' beginnin' or end o' th' file. Put it anywhere in between. Now, save th' file. + +git status + +If ye go t' th' project directory 'n execute th' command `git status`, ye'll see thar are changes. + +Add those changes t' th' branch ye jus' created usin' th' `git add` command: + +``` +git add Contributors.md +``` + +Now commit those changes usin' th' `git commit` command: + +``` +git commit -m "Add to Contributors list" +``` + +replacing `` with your name. + +## Push changes t' GitHub + +Push yer changes usin' th' command `git push`: + +``` +git push origin +``` + +replacin' `` wit' th' name o' th' branch ye created earlier. + +## Submit yer changes fer review + +If ye go t' yer repository on GitHub, ye'll see a `Compare & pull request` button. Click on that button. + +create a pull request + +Now submit th' pull request. + +submit pull request + +Soon I'll be mergin' all yer changes into th' master branch o' this project. Ye will get a notification email once th' changes 'ave been merged. + +## Where t' go from here? + +Well done! Ye jus' completed th' standard _fork -> clone -> edit -> PR_ workflow that ye'll encounter often as a contributor! + +Celebrate yer contribution 'n share it wit' yer hearties 'n followers by goin' t' [web app](https://roshanjossey.github.io/first-contributions/#social-share). + +Ye could join our slack crew in case ye needs any help or 'ave any riddles. [Join our slack crew](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Now let's get ye started wit' contributin' t' other projects. We've compiled a list o' projects wit' easy issues ye can get started on. Check out [th' list o' projects in web app](https://roshanjossey.github.io/first-contributions/#project-list). + +### [Additional material](../additional-material/git_workflow_scenarios/additional-material.md) + +## Tutorials Usin' Other Tools + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.es.md b/translations/README.es.md new file mode 100644 index 00000000000..c3e2e6a145d --- /dev/null +++ b/translations/README.es.md @@ -0,0 +1,121 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Primeras Contribuciones + +Es complicado. Resulta difícil la primera vez que haces algo, especialmente cuando colaboras con otros, pues cometer errores no es nada agradable. Nuestro objetivo es simplificar la forma en la que los nuevos contribuidores de _codigo abierto_ aprenden y contribuyen por primera vez. + +Leer artículos y ver tutoriales puede ayudar, pero, ¿Qué mejor que hacer las cosas en un entorno de prácticas? Este proyecto se enfoca en ser una guía y en simplificar la forma en la que los principiantes hacen su primera contribución. Si quieres hacer tu primera contribución, sigue los pasos que se muestran a continuación. + +#### *Si no estás familiarizado con la línea de comandos, [aquí hay tutoriales usando herramientas con Interfaz Gráfica (GUI)](#Tutoriales-con-otras-herramientas)* + +fork de este repositorio + +Si no tienes git en tu equipo, puedes encontrar instrucciones para instalarlo en [este enlace]( https://docs.github.com/es/get-started/quickstart/set-up-git ). + +## Bifurca (*Fork*) este repositorio + +Haz un *fork* de este repositorio haciendo click en el botón "*Fork*" en la parte superior derecha en esta página. +Esto creará una copia de este repositorio en tu cuenta. + +## Clona (*Clone*) el repositorio bifurcado + +clonar este repositorio + +Ahora clona este repositorio en tu equipo. Dirígete a tu cuenta de GitHub, haz click en el botón "*clone or download*" y luego haz click en el icono para *copiar al portapapeles*. + +Abre tu consola o terminal y ejecuta el siguiente comando de git: + +``` +git clone "url que acabas de copiar" +``` + +Donde pone "url que acabas de copiar" (sin las comillas dobles) es la *url* a este repositorio (tu *fork* a este proyecto). Mira los pasos previos para obtener la *url*. + +copiar URL al portapapeles + +Por ejemplo: +``` +git clone https://github.com/este-eres-tu/first-contributions.git +``` +La parte de `este-eres-tu` la reemplazarás con tu usuario de GitHub. Aquí estás copiando los contenidos del repositorio *first-contributions* en GitHub a tu equipo. + +## Crea una rama (*Branch*) + +Cambia al directorio del repositorio en tu equipo (si es que no estás ahí ya). + +``` +cd first-contributions +``` + +Ahora crea una rama (*branch*) usando el comando `git checkout`: +``` +git checkout -b +``` + +Por ejemplo: +``` +git checkout -b add-alonzo-church +``` +(El nombre de la rama no tiene por qué contener la palabra *add*, pero es razonable que lo tenga porque el objetivo de esta rama es añadir tu nombre a la lista.) + +## Haz los cambios necesarios y confirma (*Commit*) esos cambios + +Abre el archivo `Contributors.md` en un editor de texto y añade tu nombre. No lo añadas ni al principio ni al final del archivo, hazlo en cualquier otro sitio. Guarda el archivo. + +git status + +Si vas al directorio del proyecto y ejecutas el comando `git status`, verás que hay cambios. + +Agrega esos cambios a la rama (*branch*) que creaste anteriormente usando el comando `git add`: + +``` +git add Contributors.md +``` + +Ahora haz un *commit* sobre estos cambios ejecutando el comando `git commit`: +``` +git commit -m "Add to Contributors list" +``` +cambiando `` con tu nombre. + +## Sube (*Push*) tus cambios a GitHub + +Haz *push* de tus cambios usando el comando `git push`: +``` +git push origin +``` +Reemplaza `` con el nombre de la rama que creaste anteriormente. + +## Envía (*Submit*) tus cambios para ser revisados + +Si vas a tu repositorio en GitHub, verás un botón `Compare & pull request`. Haz click sobre este botón. + +crea una pull request + +Ahora envía la *pull request*. + +enviar la pull request + +Pronto estaré fusionando tus cambios (haciendo *merge*) con la rama master de este proyecto. Recibirás una notificación por correo electrónico cuando los cambios hayan sido fusionados. + +## ¿Cuáles son los siguientes pasos? + +¡Enhorabuena! ¡Has completado el flujo de trabajo *_fork -> clone -> edit -> PR_* que encontrarás habitualmente como contribuidor! + +Celebra tu contribución y compártela con tus amigos y seguidores yendo a [web app](https://roshanjossey.github.io/first-contributions/#social-share). + +También podrías unirte a nuestro *equipo* de Slack en caso de que necesites ayuda o tengas alguna pregunta. [Únete a nuestro Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Ahora empieza a contribuir a otros proyectos. Hemos reunido una lista de proyectos con *issues* sencillas para que puedas empezar. Échale un ojo a la [lista de proyectos en la aplicación web](https://firstcontributions.github.io/#project-list). + +### [Material adicional](../additional-material/git_workflow_scenarios/additional-material.md) + + +## Tutoriales con otras herramientas + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.fa.md b/translations/README.fa.md new file mode 100644 index 00000000000..62582ac578e --- /dev/null +++ b/translations/README.fa.md @@ -0,0 +1,107 @@ +[![Open Source Love](https://firstcontributions.github.io/open-source-badges/badges/open-source-v1/open-source.svg)](https://github.com/firstcontributions/open-source-badges) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +

+ +# اولین مشارکت +این پروژه قصد دارد تا مسیر مشارکت در پروژه‌های متن‌باز را برای تازه‌کارها آسان نماید. اگر شما نیز بدنبال راهی برای ثبت اولین مشارکت خود هستید، این اقدامات را دنبال کنید. + +_اگر با محیط کامندی (CLI) احساس راحتی نمی‌کنید، [راهنمای استفاده از ابزارهای گرافیکی (GUI) را مشاهده کنید](#آموزش-انجام-مشارکت-در-دیگر-ابزارها)._ + +fork this repository + +#### اگر نرم‌افزار git را آماده ندارید، [از اینجا نصب کنید](https://help.github.com/articles/set-up-git/). + +## مخزن را فورک کنید +با کلیک کردن بر روی دکمه Fork، از مخزن مورد نظر یک انشعاب بگیرید. این عملیات یک نسخه کپی از مخزن را بر روی حساب کاربری شما ایجاد می‌کند. + +## مخزن را کلون (شبیه) کنید + +clone this repository + +حال، از مخزن فورک شده، یک کلون روی سیستم کاربری خود ایجاد کنید. وارد حساب کاربری خود شده و مخزن فورک شده را باز کنید. دکمه Code را فشرده و نماد copy to clipboard را انتخاب کنید. + +سپس یک ترمینال باز کنید و دستور گیت زیر را اجرا نمایید: +``` +git clone "url you just copied" +``` +بطوری که در قسمت "url you just copied"، آدرس مخزن فورک شده بدون علامت‌های کوتیشن (نقل قول) قرار گیرد. + +copy URL to clipboard + +بعنوان مثال: +``` +git clone https://github.com/this-is-you/first-contributions.git +``` +بطوری که عبارت `this-is-you` برابر با نام حساب کاربری گیت‌هاب شما باشد. با این اقدام، تمام محتوای مورد نیاز جهت مشارکت را بر روی سیستم خود آماده می‌سازید. + +### یک شاخه ایجاد کنید +اگر در مسیر مخزن کلون شده قرار ندارید، با دستور زیر وارد مسیر مخزن شوید: +``` +cd first-contributions +``` +با استفاده از دستور `git checkout` یک شاخه جدید ایجاد کنید: +``` +git checkout -b your-new-branch-name +``` +بعنوان مثال: +``` +git checkout -b add-alonzo-church +``` +(هیچ لزومی نیست که در نام شاخه از کلمه `add` استفاده کنید. چنانچه قرار است بعنوان مشارکت، نام خود را به یک لیست اضافه کنیم، استفاده از این کلمه بعنوان نام شاخه، امری عاقلانه می‌باشد.) + +### تغییرات اساسی ایجاد کرده و کامیت کنید +در این قدم، ابتدا فایل `Contributors.md` را در یک محیط ویرایش متن باز کنید. نام خود را به این فایل اضافه کنید. توجه کنید که نام نه در ابتدا و نه در انتها قرار گیرد. نام را بین اسامی قرار دهید. فایل را ذخیره کنید. + +git status + +چنانچه وارد مسیر مخزن شوید و دستور `git status` را اجرا نمایید، مشاهده خواهید کرد که تغییراتی بر روی مخزن اعمال شده. + +با استفاده از دستور `git add`، تغییرات را به برنچ از پیش ساخته‌شده اضافه کنید: +``` +git add Contributors.md +``` + +حال، تغییرات را با دستور `git commit` کامیت و ثبت نمایید: +``` +git commit -m "Add to Contributors list" +``` +توجه داشته باشید که نام خود را با عبارت `` جایگزین کنید. + +## تغییرات را ارسال (پوش) کنید +با استفاده از دستور `git push` تغییرات ثبت شده را ارسال کنید: +``` +git push origin +``` +نام برنچی که در مراحل قبل ایجاد کردید را با عبارت `` جایگزین کنید. + +## تغییرات خود را برای بررسی، ثبت کنید +چنانچه وارد مخزن فورک شده در حساب کاربری خود شوید، گزینه‌ای تحت عنوان `Compare & pull request` مشاهده خواهید کرد. آن گزینه را انتخاب کنید. + +create a pull request + +در این مرحله، درخواست (Pull request) خود را ثبت کنید. + +submit pull request + +نهایتا، من تغییرات شما را به برنچ master پروژه اضافه (merge) خواهم کرد. بلافاصله پس از مرج شدن درخواست شما، یک ایمیل مبنی بر همین موضوع برای شما ارسال خواهد شد. + +## اقدامات بعدی +تبریک! شما مراحل فورک کردن، کلون کردن، ایجاد تغییرات و پول رکوئست را به خوبی پشت سر گذاشتید. + +مشارکت خود روی این پروژه را [از اینجا](https://firstcontributions.github.io/#social-share) با دیگر دوستان و دنبال‌کنندگان خود جشن بگیرید. + +همچنین شما می‌توانید [از اینجا](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)، وارد تیم Slack ما شوید و سوالات خود را مطرح نمایید. + +حال، شما می‌توانید مشارکت خود را روی دیگر پروژه‌ها آغاز نمایید. ما یک لیست از پروژه‌ها با مشکلات ساده ایجاد کردیم که گزینه خوبی برای شروع می‌باشد. لیست پروژه‌ها را [از این اینجا](https://firstcontributions.github.io/#project-list) دنبال کنید. + +### [اطلاعات بیشتر](additional-material/git_workflow_scenarios/additional-material.md) + +## آموزش انجام مشارکت در دیگر ابزارها | | | | | | +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + +

diff --git a/translations/README.fi.md b/translations/README.fi.md new file mode 100644 index 00000000000..d3c4812e35b --- /dev/null +++ b/translations/README.fi.md @@ -0,0 +1,129 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Ensimmäiset kontribuutiot + +Se on vaikeaa. Ensimmäiset kerrat ovat aina vaikeita. Etenkin tehdessä yhteistyötä, virheiden teko ei ole ollenkaan mukavaa. Me halusimme yksinkertaistaa tavan jolla avoimen lähdekoodin kontribuoijat oppivat sekä kontribuoivat ensimmäistä kertaa. + +Artikkeleiden lukeminen sekä tutoriaalien katsominen voi auttaa, mutta mikä onkaan parempaa kuin käytännön harjoite harjoitusympäristössä? Tämä projekti tähtää avun tarjoamiseen sekä aloittelijoiden ensimmäisen kontribuution yksinkertaistamiseen. Jos olet aikeissa kontribuoida ensimmäistä kertaa, seuraa alla olevia ohjeita. + +#### *Jos et osaa käyttää komentoriviä sulavasti, [täältä löytyy tutoriaaleja GUI-työkalujen käyttöön.](#Muiden-työkalujen-tutoriaaleja)* + +fork this repository + +Jos sinulla ei ole git asennettuna koneellesi, [asenna se](https://help.github.com/articles/set-up-git/). + +## Forkkaa tämä repositorio + +Forkkaa tämä repositorio klikkaamalla yläkulmassa näkyvää painiketta "Fork". Tämä luo kopion tästä repositoriosta käyttäjällesi. + +## Kloonaa repositorio + +clone this repository + +Seuraavaksi kloonaa juuri forkkaamasi repositorio koneellesi. Mene GitHub käyttäjäsivuillesi, avaa forkkaamasi repositorio sekä klikkaa "Clone or download"-painiketta jonka jälkeen kopioi osoite painamalla "Copy to clipboard"-ikonia. + +Avaa komentorivi ja syötä seuraava git-komento: + +``` +git clone "Juuri kopioimasi URL" +``` + +"Juuri kopioimasi URL"-tekstin sijasta (ilman lainausmerkkejä) pastea repositorion URL äskeisestä vaiheesta. + +copy URL to clipboard + +Esimerkiksi: + +``` +git clone https://github.com/nimesi/first-contributions.git +``` + +Kirjoita GitHub-käyttäjänimesi 'nimesi' teksin sijaan. Tämä komento kopioi sisällön GitHubisi first contributions-repositorion koneellesi. + +## Luo branch + +Mene repositoriosi kansioon koneellasi (ellet jo ole siellä). + +``` +cd first-contributions +``` + +Seuraavaksi luo branch komennolla `git checkout`: + +``` +git checkout -b +``` + +Esimerkiksi: + +``` +git checkout -b add-matti-meikalainen +``` + +(Branchin nimeen ei välttämättä tarvitse sisällyttää sanaa *add*, mutta tässä se käy järkeen sillä tämän branchin tarkoitus on lisätä nimesi listaan.) + +## Tee tarvittavat muutokset sekä committoi ne + +Seuraavaksi avaa `Contributors.md` tiedosto tekstieditorissa ja lisää nimesi tiedostoon. Älä lisää sitä tiedoston alkuun taikka loppuun vaan keskelle. Seuraaksi tallenna tiedosto. + +git status + +Jos menet projektin kansioon ja syötät komennon `git status`, näet muutokset. + +Lisää nuo muutokset branchiin `git add` komennolla: + +``` +git add Contributors.md +``` + +Seuraavaksi committoi muutokset `git commit` komennolla: + +``` +git commit -m "Add to Contributors list" +``` + +Korvaamalla `` nimelläsi. + +## Muutosten pushaaminen GitHubiin + +Pushaa muutoksesi komennolla `git push`: + +``` +git push origin +``` + +Korvaamalla `` nimellä jonka annoit branchillesi aikaisemmin. + +## Jätä muutoksesi arvosteltavaksi + +Jos menet repositorioosi GitHubissa, näet `Compare & pull request` painikkeen. Paina tuota painiketta. + +create a pull request + +Seuraavaksi suorita pull request. + +submit pull request + +Seuraavaksi mergeän muutoksesi tämän projektin master-branchiin. Tulet saamaan ilmoituksen sähköpostiisi kun muutokset ovat mergetty. + +## Mihin seuraavaksi? + +Onneksi olkoon! Olet juuri suorittanut tavanomaisen *Fork -> Clone -> Edit -> Pull Request* -työnkulun joka tulee vastaasi usein kontribuoijana! + +Juhlista kontribuutiotasi ja jaa se ystävillesi ja followereillesi menemällä [Web Appiin](https://roshanjossey.github.io/first-contributions/#social-share). + +Voit liittyä Slack tiimiimme jos sinulla on kysyttävää. [Liity Slack tiimiin](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Jos haluaisit kontribuoida muihin projekteihin, me olemme koonneet listan yksinkertaisista ensimmäisistä issueista työskenneltäväksesi. [Lista löytyy Web-Appistamme](https://roshanjossey.github.io/first-contributions/#project-list). + +### [Lisämateriaaleja](../additional-material/git_workflow_scenarios/additional-material.md) + +## Muiden työkalujen tutoriaaleja + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.fr.md b/translations/README.fr.md new file mode 100644 index 00000000000..1b871012078 --- /dev/null +++ b/translations/README.fr.md @@ -0,0 +1,142 @@ +[![L'amour du logiciel libre](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Premières Contributions + +C'est toujours compliqué la première fois que l'on fait quelque chose. La peur de faire des fautes n'est pas du tout confortable, spécialement quand vous collaborez. Mais le monde du logiciel libre est le fait de collaborer et de travailler en groupe. Aussi, nous voulons simplifier l'apprentissage des nouveaux contributeurs au logiciel libre en vous enseignant à contribuer pour la première fois. + +Lire des articles et des tutoriels peut aider, mais qu'y a-t-il de mieux que d'essayer sans pouvoir faire d'erreurs ? Ce projet a pour ambition de fournir des conseils et simplifier la manière dont les apprentis font leur première contribution. Souvenez-vous : plus vous êtes serein, mieux vous apprenez. Si vous aspirez à faire votre première contribution, suivez tout simplement les étapes suivantes. Promis, ce sera amusant. + +embrancher ce repertoire + +Si vous n'avez pas git sur votre ordinateur, [ installez-le ]( https://help.github.com/articles/set-up-git/ ). + +## Embranchez ce répertoire (aussi appelé un Fork) + +Embranchez ce répertoire en cliquant sur le bouton de fork en haut de la page. +Cela va créer une copie du répertoire sur votre compte. + +## Clonez ce répertoire + +clonez ce répertoire + +Maintenant, clonez ce répertoire sur votre ordinateur. Cliquez sur le bouton clone puis cliquez sur l'icone *copier dans le presse-papier*. + +Ouvrez un invite de commande et exécutez les commandes git suivantes : + +``` +git clone "l'url que vous venez de copier" +``` +où "l'url que vous venez de copier" (sans les guillemets) est l'url du répertoire. Voir la section précédente afin d'obtenir l'url. + +copier l'URL dans le presse-papier + +Par exemple : +``` +git clone https://github.com/votre-nom-d-utilisateur/first-contributions.git +``` +où `votre-nom-d-utilisateur` est votre nom d'utilisateur GitHub. Ici vous êtes en train de copier le contenu du répertoire `first-contributions` depuis GitHub sur votre ordinateur. + +## Créez une branche + +Déplacez-vous dans le répertoire du projet nouvellement cloné (si vous n'y êtes pas encore) : + +``` +cd first-contributions +``` +Maintenant créez une branche avec le commande `git checkout` : +``` +git checkout -b +``` + +Par exemple : +``` +git checkout -b add-koffi-sani +``` +(Le nom de la branche n'a pas besoin de contenir le terme *add*, mais c'est raisonnable de l'inclure parce que l'objectif de cette branche est d'ajouter votre nom à une liste.) + +## Effectuez les modifications nécessaires et engagez-les + +Maintenant, ouvrez le fichier `Contributors.md` dans un éditeur de texte, ajoutez-y votre nom, et enregistrez-le. Si vous ouvrez l'invite de commande et vous exécutez la commande `git status`, vous verrez qu'il y a des modifications. Ajoutez ces modifications à la branche que vous venez de créer avec la commande `git add` : +``` +git add Contributors.md +``` + +Maintenant engagez ces modifications avec la commande `git commit`: +``` +git commit -m "Add to Contributors list" +``` +en remplaçant `` par votre nom. + +## Poussez les modifications vers GitHub + +Poussez vos modifications avec la commande `git push` : +``` +git push origin +``` +en remplaçant `` avec le nom de la branche précédemment créée. + +## Soumettez vos changements pour révision + +Si vous visitez votre répertoire sur Github, vous verrez un bouton `Compare & pull request`. Cliquez sur ce bouton. + +create a pull request + +Maintenant soumettez la demande de tirage. + +submit pull request + +Sous peu j'aurai fusionné toutes vos modifications avec la branche main de ce projet. Vous recevrez un mail de notification dès que la fusion sera effectuée. + +La branche main de votre embranchement ne subira pas de modification à cet instant. Pour que votre embranchement soit synchronisé avec le mien, suivez les étapes suivantes. + +## Gardez votre embranchement synchronisé avec ce répertoire + + D'abord, basculez sur la branche main + ``` + git checkout main + ``` + + Et ajouter l'url de mon répertoire comme `upstream remote url` : +``` +git remote add upstream https://github.com/Roshanjossey/first-contributions +``` +Ceci est une manière de dire à git qu'une autre version de ce répertoire existe à l'adresse spécifiée et que nous l'appelons `upstream`. Une fois les modifications fusionnées, cherchez la nouvelle version de mon répertoire : +``` +git fetch upstream +``` + +Ici nous cherchons toutes les modification dans mon embranchement (upstream remote). Maintenant, vous devez fusionner la nouvelle révision de mon répertoire avec votre branche main : +``` +git rebase upstream/main +``` +Ici nous appliquons toutes les modifications que vous avez cherché à la branche main. Si vous poussez la branche main maintenant, votre embranchement aussi aura les modifications : +``` +git push origin main +``` +Avertissement: Cette fois, vous poussez au répertoire distant appelé origin. + +A ce niveau j'ai fusionné votre branche `` avec ma branche main, et vous avez fusionné ma branche main avec votre branche main. Votre branche `` n'est plus utile, donc vous pouvez la supprimer : +``` +git branch -d +``` +et vous pouvez supprimer sa version dans le répertoire distant aussi : +``` +git push origin --delete +``` +Ceci n'est pas nécessaire, mais le nom de la branche montre que son objectif est assez spécifique. Sa durée de vie peut être courte. + +## Tutoriels en utilisant d'autres outils + + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + +## Où aller ensuite ? + +Vous pouvez aussi rejoindre notre équipe sur Slack au cas où vous auriez besoin d'aide ou auriez des questions. [Rejoindre l'équipe sur Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) + diff --git a/translations/README.ge.md b/translations/README.ge.md new file mode 100644 index 00000000000..324fede12c0 --- /dev/null +++ b/translations/README.ge.md @@ -0,0 +1,123 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# პირველი კონტრიბუცია +ახალი რამის პირველად, დამოუკიდებლად, გაკეთება შეიძლება საკმაოდ რთული აღმოჩნდეს. მითუმეტეს, თუ უცხოებთან თანამშრომლობ და შეცდომების დაშვება არცთუ ისე კარგი გრძნობაა. ჩვენ გვინდოდა დამწყები ოფენ სორს კონტრიბუტორებისთვის გაგვემარტივებინა საქმე და გვესწავლებინა თუ როგორ უნდა შეიტანონ წვლილი სხვა პროექტებში. + +ეს პროექტი ეხმარება დამწყებ "დეველოპერებს" რათა გაუადვილდეთ პირველი კონტრიბუცია Github_ზე. თუ გინდა რომ პირველი შენი დაწერილი კოდი Github_ზე ათვირთო მაშინ მიყევი ქვემოთ მოცემულ ინსტრუქციას. + +კი, სტატიების წაკითხვა და ვიდეოების ყურება კარგია, მაგრამ, პრაქტიკას არც ერთი შეედრება. ეს პროექტიც ზუსტად იმისთვისაა, რომ გაგიმარტივოს გზა პირველ კონტრიბუციამდე, რომელსაც ქვემოთ ჩამოთვლილი რამდენიმე ნაბიჯი გაშორებს.\ + + +#### *თუ ტერმინალთან დიდად არ მეგობრობ, [აქ ნახავ რამდენიმე პროგრამას, რომელიც ტერმინალის გამოყენებას აგარიდებს თავიდან]( #ტუტორიალები-სხვა-პროგრამების-გამოყენებით )* + +fork this repository + +თუ კომპიუტერში გითი არ გაქვს ჩაწერილი, [მიჰყევი ლინკს]( https://help.github.com/articles/set-up-git/). + +## დაფორკე ეს რეპოზიტორია + +რეპოზიტორიის დაფორკვისთვის, ამ გვერდის მარჯვენა ზედა კუთხეში დააჭირე "Fork" ღილაკს, რომელიც მის ასლს შეგიქმნის. + +## რეპოზიტორიის დაკლონვა + +clone this repository + +ახლა, დაფორკილი რეპოზიტორია შენს კომპიუტერზე უნდა გადმოიტანო. ამისთვის შედი შენს გითჰაბის პროფილზე, გახსენი რეპოზიტორია და დააჭირე "Clone or download"-ს, შემდეგ კი *"copy to clipboard"*-ის სურათს. + +ახლა გახსენი ტერმინალი და გაუშვი შემდეგი ბრძანება: + +``` +git clone "url you just copied" +``` +სადაც "url you just copied" (ბრჭყალების გარეშე) არის შენ მიერ დაკოპირებული რეპოზიტორიის ლინკი. (თუ ეს ლინკი არ გაქვს, წინა ნაბიჯი თავიდან გაიარე). + +copy URL to clipboard + +მაგალითად: +``` +git clone https://github.com/this-is-you/first-contributions.git +``` +სადაც `this-is-you` ნაწილი, შენი გითჰაბის სახელია. ამითი რეპოზიტორიის ყველა ფაილი შენს კომპიუტერში გადმოვა. + +## შექმენი ბრენჩი + +შენი კომპიუტერით შედი რეპოზიტორიის ფოლდერში (თუ უკვე იქ არ ხარ): + +``` +cd first-contributions +``` +ახლა შექმენი ახალი ბრენჩი `git checkout` ბრძანების გამოყენებით: +``` +git checkout -b +``` + +მაგალითად: +``` +git checkout -b add-alonzo-church +``` +(ბრენჩის სახელის დასაწყისში *add*-ის მიწერა სავალდებულო არაა, თუმცა მიზანშეწონილია, რადგანაც მისი მთავარი მიზანია თქვენი სახელი დაამატოს კონტრიბუტორთა სიაში.) + +## საჭირო ფაილების შეცვლა და ატვირთვა + +ახლა რომელიმე პროგრამით (სასურველია ტექსტ ედიტორით) გახსენი ფაილი, სახელად `Contributors.md` და დაამატე შენი სახელი. ოღონდ გაითვალისწინე, რომ ის სხვების სახელებს შორის უნდა ჩაწერო და არა ფაილის დასაწყისში, ან ბოლოში. შეინახე ცვლილებები. + +git status + + +თუ პროექტის ფოლდერში გადახვალ და გაუშვებ ბრძანება: `git status`. ტერმინალი გაჩვენებს რა ფაილებში მოხდა ცვლილებები. + + +`git add`-ით დაამატე ცვლილებები შენ მიერ შექმნილ ახალ ბრენჩს: + +``` +git add Contributors.md +``` + +ახლა შეინახე ისინი `git commit`-ის გამოყენებით: +``` +git commit -m "Add to Contributors list" +``` +აქაც, `` უნდა შეცვალო შენი პროფილის სახელით. + +## ცვლილებების ატვირთვა გითჰაბზე + +ატვირთე შენი ნამუშევარი `git push`-ის მეშვეობით: +``` +git push origin +``` +`` აქ შენ მიერ შექმნილი ბრენჩის სახელით უნდა ჩაანაცვლო. + +## განხილვის მოთხოვნა + +გითჰაბზე, შენს რეპოზიტორიაში როცა გადახვალ, დაინახავ `Compare & pull request` ღილაკს. დააჭირე. + +create a pull request + +ახლა შენ მოითხოვ ცვლილებების განხილვას. + +submit pull request + +და სულ მალე, შენი ნამუშევარი ამ პროექტის მთავარ ბრენჩზე გამოჩნდება. ამის შესახებ მეილსაც მიიღებ. + +## აქედან საით? + +გილოცავ! შენ შეასრულე სტანდარტული კონტრიბუციის პროცედურა, რომელსაც მომავალში ხშირად გამოიყენებ, როგორც კონტრიბუტორი! + +აღნიშნე და გაუზიარე მეგობრებს შენი წარმატება [ამ ლინკზე გადასვლით](https://firstcontributions.github.io/#social-share). + +[შემოგვიერთდი slack-ზე](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +თუ კონტრიბუციების სხვაგან შეტანაც გინდა, ჩვენ შენთვის შედარებით მარტივად გასაგები პროექტები შევარჩიეთ, [რომლებსაც აქ ნახავ](https://firstcontributions.github.io/#project-list). + +### [დამატებითი მასალა](../additional-material/git_workflow_scenarios/additional-material.md) + + +## ტუტორიალები სხვა პროგრამების გამოყენებით + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| ------------------------------------------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ | +| [GitHub Desktop](../github-desktop-tutorial.md) | [Visual Studio 2017](../github-windows-vs2017-tutorial.md) | [GitKraken](../gitkraken-tutorial.md) | [Visual Studio Code](../github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../github-windows-intellij-tutorial.md) | \ No newline at end of file diff --git a/translations/README.gl.md b/translations/README.gl.md new file mode 100644 index 00000000000..0dabf783870 --- /dev/null +++ b/translations/README.gl.md @@ -0,0 +1,107 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Primeiras Contribucións + +É difícil. Sempre é difícil a primeira vez que fas algo. Especialmente cando estás colaborando, equivocarse non é algo agradable. Pero no *open source* (o código aberto) todo trata de colaboración e de traballar xuntos. Quixemos simplificar a forma na que novos contribuidores *open-source* aprenden e contribúen por primeira vez. + +Ler artículos e ver titoriais pode axudar, pero ¿que haberá mellor que facer as cousas nunha contorna pensada para practicar? Iste proxecto enfócase en prover unha guía e en simplificar o xeito no que os novatos fan a súa primeira contribución. Lembra que mentres máis relaxado esteas, mellor aprenderás. Se queres facer a túa primeira contribución só tés que seguir os sinxelos pasos que se amosan a continuación. E prometémosche que será entretido. + +fork de éste repositorio + +Se aínda non tés git na túa máquina, [ instálao ]( https://help.github.com/articles/set-up-git/ ) + +## Bifurca(*Fork*) este repositorio + +Fai un *fork* (bifurcación) deste repo facendo click no botón "Fork" que está na cima desta páxina. +Isto creará unha copia deste repositorio na túa conta. + +## Clona(*Clone*) o repositorio + +clonar este repositorio + +A continuación clona este repo no teu equipo. Fai click no botón "*Clone*" e despois na icona para copiar ó portapapeis (clipboard) + +Abre a túa consola ou terminal e executa o seguinte comando de git: + +``` +git clone "url que copiache" +``` +Onde "url que copiache" (sen as comiñas) é a url deste repositorio. Mira os pasos previos para obter a url. + +copiar URL a clipboard + +Por exemplo: +``` +git clone https://github.com/o-teu-nome/first-contributions.git +``` +Onde "o-teu-nome" é o teu usuario de GitHub. Aquí estarás copiando os contidos do repositorio first-contributions en GitHub para o teu computador. + +## Crear unha póla(*Branch*) + +Cambia ó directorio do repositorio no teu computador (se é que non estás xa nel). + +``` +cd first-contributions +``` + +Agora crea unha branch (póla) usando o comando `git checkout` + +``` +git checkout -b +``` + +Por exemplo +``` +git checkout -b engade-María-Soliña +``` + +(O nome da branch non ten que incluir necesariamente a palabra 'engade', pero resulta razoable se consideramos que o propósito desta póla é engadir o teu nome a unha lista). + +## Fai os cambios necesarios e efectúa(*Commit*) deses cambios + +Agora abre o arquivo `Contributors.md` nun editor de texto, engade o teu nome e despois garda o arquivo. Se vas ó directorio do proxecto e executas `git status`, verás que hai modificacións. Agrega eses cambios ou modificacións usando o comando `git add` tal como se amosa: +``` +git add Contributors.md +``` + +Agora podes facer commit sobre os cambios co comando `git commit` +``` +git commit -m "Add to Contributors list" +``` +cambiando `` polo teu nome. + +## Envía (*Push*) os teus cambios a GitHub + +Fai un *push* dos teus cambios usando o comando `git push` +``` +git push origin +``` +cambiando `` polo nome da branch que creaches antes. + +## Envía os teus cambios para seren revisados + +Se vas ó teu repositorio en GitHub, verás un botón `Compare & pull request`. Fai click nese botón: + +crea unha pull request + +Agora crea e envía a pull request: + +sube a pull request + +Axiña mesturarei os teus cambios (facendo *merge*) na master branch deste proxecto. Recibirás unha notificación por correo cando os cambios xa estean mesturados. + +### [ Material adicional ](../additional-material/git_workflow_scenarios/additional-material.md) + +## Titoriais con outras ferramentas + + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + +## Onde ir dende aquí? + +Tamén poderías unirte á nosa *equipa* en Slack no caso de que necesites axuda ou teñas algunha pregunta. [Únete ó noso Slack](https://firstcontributors.slack.com/join/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY) diff --git a/translations/README.gr.md b/translations/README.gr.md new file mode 100644 index 00000000000..95770f3c3f4 --- /dev/null +++ b/translations/README.gr.md @@ -0,0 +1,128 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Πρώτη Συνεισφορά + +Είναι πάντα δύσκολο να κάνεις κάτι για πρώτη φορά. Ειδικά όταν συνεργάζεσαι με άλλους και κάνεις λάθη, η κατάσταση γίνεται ιδιαίτερα άβολη. Αλλά το σημαντικότερο πράγμα στο ανοιχτό λογισμικό είναι η συνεργασία και το να δουλεύουμε μαζί. Θέλαμε να απλοποιήσουμε τον τρόπο με τον οποίο οι άνθρωποι που για πρώτη φορά συνεισφέρουν στο ανοιχτό λογισμικό, μαθαίνουν και κάνουν πράγματα. + +Μπορείτε να βοηθηθείτε διαβάζοντας άρθρα και βλέποντας ενημερωτικά βίντεο, αλλά τίποτα δε συγκρίνεται με το να δουλεύετε σε ένα πραγματικό project. Αυτό το έργο έχει στόχο να κατευθύνει και να απλοποιήσει τον τρόπο με τον οποίο οι σχετικά άπειροι συνεισφέρουν για πρώτη φορά σε κώδικα ανοιχτού λογισμικού. Σκεφτείτε ότι όσο πιο χαλαροί είστε τόσο πιο εύκολα μαθαίνετε. Εάν προσπαθείτε να κάνετε την πρώτη σας συνεισφορά σε κώδικα, ακολουθήστε τα επόμενα απλά βήματα. + +fork this repository + +Εάν δεν έχετε εγκατεστημένο το git στον υπολογιστή σας, [εγκαταστήστε το]( https://help.github.com/articles/set-up-git/ ) + +## Αντιγράψτε το αποθετήριο (fork) + +Αντιγράψτε το αποθετήριο πατώντας το κουμπί με τίτλο `Fork` στην κορυφή αυτής της σελίδας. Με αυτό τον τρόπο ένα ακριβές αντίγραφο του αποθετηρίου θα δημιουργηθεί στο λογαριασμό σας. + +## Αποθηκεύστε τοπικά το αποθετήριο (clone) + +clone this repository + +Τώρα αντιγράψτε το αποθετήριο στον υπολογιστή σας. Κάντε κλικ στο κουμπί `Clone or download` και μετά στο εικονίδιο δεξιά από το σύνδεσμο για αντιγραφή στο πρόχειρο. + +Ανοίξτε ένα τερματικό και τρέξτε την ακόλουθη git εντολή: + +``` +git clone "σύνδεσμος που μόλις αντιγράψατε" +``` +Όπου "σύνδεσμος που μόλις αντιγράψατε" (χωρίς τα εισαγωγικά) είναι ο σύνδεσμος για αυτό το αποθετήριο. Δείτε τα προηγούμενα βήματα για να βρείτε αυτόν τον σύνδεσμο. + +copy URL to clipboard + +Για παράδειγμα: +``` +git clone https://github.com/this-is-you/first-contributions.git +``` + +Όπου 'this-is-you' είναι το όνομα χρήστη σας στο github. Εδώ αντιγράφετε τα περιεχόμενα του αποθετηρίου `first-contributions` απο το github στον υπολογιστή σας. + +## Δημιουργήστε ένα νέο παρακλάδι (branch) + +Μεταφερθείτε στο φάκελο του αποθετηρίου στον υπολογιστή σας εάν δεν είστε ήδη εκεί. + +``` +cd first-contributions +``` +Τώρα δημιουργείστε ένα νέο παρακλάδι χρησιμοποιώντας την εντολή `git switch` : +``` +git switch -c your-new-branch-name +``` + +Για παράδειγμα: +``` +git switch -c add-alonzo-church +``` +(Το όνομα του παρακλαδιού δεν χρειάζεται να περιέχει την λέξη *add* αλλά είναι λογικό να την συμπεριλάβουμε μιας και ο σκοπός του παρακλαδιού είναι να προσθέσουμε το όνομα μας σε μια λίστα.) + +## Πραγματοποιήστε αλλαγές και σώστε τες (add & commit) + +Τώρα ανοίξτε το αρχείο `Contributors.md` με έναν επεξεργαστή κειμένου. Χρειάζεται να είστε εξοικειωμένοι με την Markdown, μια ελαφριά γλώσσα σήμανσης. Δείτε στο [cheat sheet](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet) για το πως να χρησιμοποιήσετε την Markdown. + +Σε αυτήν την περίπτωση προσθέστε την παρακάτω σειρά στο τέλος του αρχείου `Contributors.md:` + +``` +- [Το-όνομα-σας](https://github.com/Your-username) +``` + +Για παράδειγμα: + +``` +- [John Doe](https://github.com/johndoe) +``` + +Σιγουρευτείτε ότι δεν υπάρχει κενό ανάμεσα στα `](` . Αποθηκεύστε το αρχείο και κλείστε το. + +git status + +Εάν πάτε στο φάκελο του αποθετηρίου και τρέξετε την εντολή `git status`, θα δείτε ότι υπάρχουν κάποιες αλλαγές. Προσθέστε αυτές τις αλλαγές χρησιμοποιώντας την εντολή `git add`. + +``` +git add Contributors.md +``` + +Τώρα σώστε αυτές τις αλλαγές χρησιμοποιώντας την παρακάτω `git commit` εντολή. +``` +git commit -m "Add to Contributors list" +``` +όπου `` αντικαταστήστε με το όνομα σας + +## Αποθηκεύστε τις αλλαγές σας στο github (push) + +Αποθηκεύστε τις αλλαγές σας χρησιμοποιώντας την εντολή `git push` +``` +git push origin +``` +όπου `` αντικαταστήστε με το όνομα του παρακλαδιού(branch) που δημιουργήσατε προηγουμένως + +## Υποβάλλετε τις αλλαγές σας για έλεγχο + +Εάν πάτε στο αποθετήριο (repository) στο github θα δείτε ένα κουμπί με τίτλο `Compare & pull request`. Κάντε κλικ σε αυτό το κουμπί. + +create a pull request + +Τώρα υποβάλλετε το pull request. + +submit pull request + +Σύντομα θα ενσωματώσω όλες τις αλλαγές σας στο master branch του προγράμματος. Θα ειδοποιηθείτε με email όταν οι αλλαγές που κάνατε ενσωματωθούν. + +## Τι να κάνετε τώρα; + +Γιορτάστε και μοιραστείτε την συνεισφορά σας με τους φίλους και τους ακόλουθους σας πηγαίνοντας στο [web app](https://roshanjossey.github.io/first-contributions/#social-share). + +Μπορείτε να συμμετέχετε στην ομάδα μας στο slack σε περίπτωση που θέλετε κάποια βοήθεια ή έχετε κάποια ερώτηση. +[Η ομάδα μας στο slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Τώρα μπορείτε να ξεκινήσετε να συνεισφέρετε και σε άλλα project. Έχουμε φτιάξει μια λίστα από project με εύκολα προβλήματα για να ξεκινήσετε. Δείτε εδώ [τη λίστα με τα project](https://roshanjossey.github.io/first-contributions/#project-list). + +### [Επιπρόσθετο υλικό](../additional-material/git_workflow_scenarios/additional-material.md) + + +## Εκπαιδευτικό Υλικό Χρήσης Άλλων Εργαλείων + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.guj.md b/translations/README.guj.md new file mode 100644 index 00000000000..b79b80a7c02 --- /dev/null +++ b/translations/README.guj.md @@ -0,0 +1,143 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) +# પ્રથમ યોગદાન + +પ્રથમ વખત કંઈક કરવું મુશ્કેલ છે. ખાસ કરીને જ્યારે તમે મળીને કામ કરી રહ્યા હોવ ત્યારે ભૂલો કરવી સારી વાત નથી. પરંતુ એકબીજા સાથે મળીને અને એક જ સાથે કામ કરવું એ જ તો ઓપેન સોર્સ છે. અમે તમારું પ્રથમ ઓપન સોર્સ કોન્ટ્રિબ્યુશન / યોગદાન સરળ બનાવાનો પ્રયત્ન કરીશુ. + +આર્ટિકલ્સ વાંચન અને ઓનલાઇન ટ્યુટોરિયલ્સ મદદ કરી શકે છે, પરંતુ પોતે તે કામ કરવાથી સારું શું હોઇ શકે? આ પ્રોજેક્ટ તમને તમારી પ્રથમ કોન્ટ્રિબ્યુશન માટે દિશા નિર્દેશ આપશે. જો તમે તમારું પ્રથમ કોન્ટ્રીબ્યુશન કરવા માંગો છો તો આગળ આપેલા સ્ટેપ્સને અનુસરો. + +જો તમે કમાન્ડ લાઇન સાથે આરામદાયક ન હોવ, તો અહીં [ GUI ટૂલ્સનો ઉપયોગ કરવાના ટ્યુટોરિયલ્સ ](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools) છે. + +fork this repository + +જો તમારા કમ્પ્યુટર પર Git નથી, [ તો Git ઈન્સ્ટોલ કરો](https://help.github.com/articles/set-up-git/) + + +## રિપોઝીટરીને ફોર્ક કરો + +કાંટા(ફોર્ક) બટન પર ક્લિક કરવાથી આ રિપોઝીટરી ફોર્ક થાય છે, આ તમારા GitHub એકાઉન્ટમાં આ રિપોઝીટરીની એક નકલ (કોપી) બનાવશે. + + +## રિપોઝીટરી ક્લોન કરો + +clone this repository + + +હવે તમે આ રેપો તમારા કમ્પ્યુટરમાં ક્લોન કરો (અર્થાત ડાઉનલોડ કરો). તમારા GitHub એકાઉન્ટ પર જાવ, ક્લોન બટન પર ક્લિક કરો અને પછી `copy to clipboard` આઇકોન પર ક્લિક કરો. + + +તમારા કમ્પ્યુટર પર એક ટર્મિનલ / કમાંડ પ્રોમ્પ્ટ ખોલો અને નીચે દર્શાવ્યા મુજબ git આદેશ ચલાવો: + +``` +git clone "યુઆરએલ જે તમે હમણાં જ નકલ(ક્લોન) કરી" +``` + + +જ્યાં "યુઆરએલ જે તમે હમણાં જ કોપી કર્યું છે" (અવતરણ ચિહ્નો સિવાય) એ આ રિપોઝીટરી(આ પ્રોજેક્ટનો તમારો ફૉર્ક) ની URL ના સંગ્રહ માટે છે. તેની URL ને મેળવવા માટે પાછલા પગલાં જુઓ. + +ઉદાહરણ તરીકે: + +``` +git clone https://github.com/આ-તમે-છો/first-contributions.git +``` + +copy URL to clipboard + + +'આ-તમે-છો' તમારા GitHub એકાઉન્ટનું `username` છે. અહીં તમે તમારા કમ્પ્યુટરમાં GitHub થી first-contributions રિપોને કોપી કરી રહ્યા છો અથવા તેના એક સ્થાનિક / લોકલ કોપી બનાવી રહ્યા છે. + +## એક બ્રાંચ બનાવો + +તમારા કમ્પ્યુટર પર બનાવેલ રિપોઝીટરીની કોપીનાં ફોલ્ડર / ડિરેક્ટરીમાં જાવ (જો હજુ સુધી તમે ત્યાં ન હોવ તો નીચે આપેલ Command(આદેશ) ચલાવો) + + +``` +cd first-contributions +``` + + +હવે 'git checkout' command(આદેશ) નો ઉપયોગ કરીને એક નવી શાખા(Branch) બનાવો. નવી શાખા(Branch) બનાવવા માટે -b વિકલ્પનો ઉપયોગ થાય છે. + +``` +git checkout -b <તમારી-શાખા-નામ-ઉમેરો> +``` + +ઉદાહરણ તરીકે: + +``` +git checkout -b add-alonzo-church +``` + + +(શાખા(Branch)ના નામમાં 'add' ઉમેરવાની જરૂર નથી, પરંતુ તેમાં શામેલ કરવું યોગ્ય છે કારણ કે શાખા(Branch)નો હેતુ એક નામ છે, જે નામ ઉમેરવાનું છે.) + +## આવશ્યક ફેરફારો કરો અને તે ફેરફારોને કમીટ કરો- + + +હવે 'Contributors.md` ફાઇલને એક ટેક્સ્ટ એડિટરમાં ખોલો અને તેમા તમારુ નામ લખો. ફાઇલની શરૂઆત અથવા અંતે તેને ના ઉમેરતા. તેને મધ્યમાં ગમે ત્યાં રાખો. હવે, ફાઇલને સેવ કરો. + +git status + + +જો તમે પ્રોજેક્ટની ડાઈરેક્ટરીમા જશો અને `git status` નિર્દેશ ચલાવશો, તો તમે કરેલા પરિવર્તન જોઈ શક્શો. તે પરિવર્તન બનાવવામાં આવેલ શાખા(Branch)માં ઉમેરવા માટે 'git add` કમાન્ડ વાપરો. + + +``` +git add Contributors.md +``` + + +હવે તમારા પોતાના ફેરફારોને 'git commit' આદેશનો ઉપયોગ કરી કમીટ કરો. + +``` +git commit -m "Add <તમારુ-નામ> to Contributors list" +``` + +<તમારુ નામ> ની જગ્યાએ તમારું નામ દાખલ કરો + + +## +તમારા ફેરફારો ને Github માં પુશ કરો + +`git push` ઉપયોગ કરીને તમારા પરિવર્તન ને પુશ કરો + +``` +git push origin <તમારી-શાખા-નામ-ઉમેરો> +``` + +`<તમારી-શાખા-નામ-ઉમેરો>` ની જગ્યાએ તમારી શાખા(Branch)નુ નામ ઉમેરો. + +## તમારા ફેરફારોના રીવ્યુ માટે સબમિટ કરો + + +જો તમે તમારા github એકાઉન્ટ પર તમારી રિપો માં જાવ તો Compare & pull request નો ઓપ્શન હશે. તેને દબાવો. + +create a pull request + +હવે તમારી pull request સબમિટ કરો. + +submit pull request +ટૂંક સમયમાં હું તમારા ફેરફારો માટે આ પ્રોજેક્ટની માસ્ટર શાખામાં મર્જ ક્રી દઇશ. તમને એક મેલ આવશે જ્યારે તમારા ફેરફારો મર્જ થશે. + + +## હવે, અહીંથી ક્યાં જવું ? + +અભિનંદન!:tada: તમે હમણાં જ સ્ટાન્ડર્ડ `fork -> clone -> edit -> pull request` વર્કફ્લો પૂર્ણ કર્યો છે. જેનો તમે વારંવાર સહયોગકર્તા (contributor) તરીકે સામનો કરશો! + + +તમારા પ્રથમ યોગદાનની ઉજવણી કરો અને [વેબ એપ્લિકેશન](https://roshanjossey.github.io/first-contributions/#social-share) પર જઈને તમારા મિત્રો અને ફોલોઅર્સ સાથે શેર કરો. + + + +જો તમને કોઈ મદદની જરૂર હોય અથવા તમારી કોઈ સમસ્યા હોય તો તમે અમારી સ્લેક ટીમમા જોડાઈ શકો છો. [સ્લેક ટીમ જોઈન કરો.](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) + + +ચાલો, હવે તમને અન્ય પ્રોજેક્ટ્સમાં કંટ્ર્રીબ્યુટ કરવામા મદદ કરુ. અમે તમારા માટે એક યાદી બનાવી છે જેમા ખૂબ સરળ issues(મુદ્દાઓ) છે વેબ એપમા પ્રોજેક્ટ્સ ની સૂચિ જુઓ.](https://roshanjossey.github.io/first-contributions/#project-list) + +## અન્ય સાધનોનો ઉપયોગ કરીને ટ્યુટોરીયલ્સ + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.hau.md b/translations/README.hau.md new file mode 100644 index 00000000000..0056c0b442a --- /dev/null +++ b/translations/README.hau.md @@ -0,0 +1,134 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Kyauta ta Farko + +Yana da wahala. Yana da wahala lokacin da kuka fara yin wani abu. Musamman lokacin da kuke mu'amala, yin kuskure ba abu ne mai kyau ba. Muna son ƙirƙirar buɗaɗɗen hanya don sababbin mutane don koyo kuma su shiga a karon farko. + +Karatun labarai da koyawa kan layi na iya taimaka muku, amma menene ya fi yin ainihin abin? Manufar wannan aikin shine don ba da jagora & ba da damar mutane su fara ba da gudummawa. Idan kuna neman ba da gudummawarku ta farko, bi matakan da ke ƙasa. + +#### *Idan ba kwa son alamomin doka, [Anan akwai koyawa ta amfani da kayan aikin GUI.](#Koyo-don-amfani-wasu)* + +fork this repository + +Idan ba ku da inji a kan injin ku, [shigar da shi]( https://help.github.com/articles/set-up-git/). + + +## Cire wannan babban fayil ɗin + +Cire wannan repo ta danna maɓallin thumbnail a saman wannan shafin. Wannan zai haifar da ajiyar tsaro guda ɗaya a cikin asusunku. + +## Yana rufe wurin ajiya + +clone this repository + +Yanzu maye gurbin repo akan injin ku. Je zuwa asusun GitHub ɗin ku, buɗe repo don dannawa, danna maɓallin clone sannan danna gunkin alamar. + +Bude tasha kuma gudanar da umarni mai zuwa: + +``` +git clone "url you just copied" +``` + +inda "url ɗin da kuka kwafi" (ba tare da alamar magana ba) shine url don ajiya anan (ƙarshen wannan aikin). Duba matakan da suka gabata don samun url. + +copy URL to clipboard + +Misali: + +``` +git clone https://github.com/this-is-you/first-contributions.git +``` + +inda `this-is-you` shine sunan mai amfani na GitHub. Anan, kuna kwafin abun ciki na ainihin gudummawar GitHub akan kwamfutarka. + +## Ƙirƙiri reshe + +Canja zuwa tsarin shugabanci akan kwamfutarka (idan ba ku da shi a can): + +``` +cd na farko-gudunmawar +``` + +Yanzu, ƙirƙiri reshe ta amfani da umarnin 'git checkout': + +``` +git checkout -b <ƙara-sabon-reshe-name> +``` + +Misali: + +``` +git checkout -b add-alonzo-church +``` + +(Sunan reshen ba lallai ba ne a saka kalmar a cikinsa, amma yana da mahimmanci ku haɗa shi saboda manufar wannan reshen shine ƙara sunan ku a cikin jerin sunayen). + +## Yi canje-canjen da suka dace kuma ku canza waɗannan canje-canje + + +Yanzu buɗe fayil ɗin `Contributors.md` a editan rubutu, ƙara sunan ku gare shi. Ana haɗe shi zuwa farkon ko ƙarshen fayil ɗin. Saka shi wani wuri a tsakanin. Yanzu ajiye fayil ɗin. + +git status + +Idan ka je kundin kundin kamfani kuma ka aiwatar da umurnin 'git status', za ka ga cewa akwai canje-canje. + + +Ƙara waɗannan canje-canje zuwa reshen da kuka ƙirƙira ta amfani da umarnin 'git add': + +``` +git ƙara Masu ba da gudummawa.md +``` + +Yanzu aiwatar da canje-canje ta amfani da umarnin 'git Committee': + +``` +git commit -m "Ƙara zuwa lissafin Masu ba da gudummawa" +``` +Sauya `' da sunan ku. + +## Tura duk waɗannan canje-canje zuwa GitHub + + +Yi canje-canjen ku ta amfani da umarnin 'git push': + +``` +git tura asalin <ƙara-sunan-reshen ku> +``` + +Sauya `` da sunan reshe da kuka ƙirƙira a baya. + +## Ƙaddamar da canje-canjenku don dubawa + + +Idan kun je wurin ajiyar ku akan GitHub, zaku ga maɓallin 'Compare & ja buƙatar'. Danna maɓallin. + +create a pull request + +Yanzu, yi buƙatar. + +submit pull request + +Nan ba da jimawa ba zan magance duk canje-canjenku a wannan reshe. Za ku karɓi saƙon sanarwa a duk lokacin da aka yi canji. + +## Ina zan je daga nan? + +Taya murna! Ka kawai karanta uwar garken -> kwafin fitarwa -> gyara -> Zazzage sabis na PR wanda koyaushe za ku hadu a matsayin mai ba da ku! + +Duba gudunmawar ku kuma ku raba ta tare da abokanku da mabiyanku ta ziyartar [app app](https://roshanjossey.github.io/first-contributions/#social-share). + +Kuna iya shiga cikin ma'aikatan mu na abokantaka idan kuna buƙatar kowane taimako ko kuna da tambayoyi. [Haɗa ƙungiyar slack](https://join.slack.com/t/firstcontr🏴ibutors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWYZm + +Yanzu, bari mu fara da ba da gudummawa don wasu ayyuka. Mun tattara jerin ayyuka masu sauƙi da tattaunawa da za ku iya farawa. Duba [jerin ayyuka da aikace-aikacen yanar gizo](https://roshanjossey.github.io/first-contributions/#project-list). + + +### [Ƙarin Material](../additional-material/git_workflow_scenarios/additional-material.md) + +## Ilimi da amfani da sauran kayan + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + diff --git a/translations/README.hb.md b/translations/README.hb.md new file mode 100644 index 00000000000..8b0f41689e1 --- /dev/null +++ b/translations/README.hb.md @@ -0,0 +1,216 @@ +
+ Open Source Helpers + License: MIT + Open Source Love + +
+ +
+

תרומות ראשונות

+
+ +
+מטרת פרויקט זה היא לפשט ולהדריך מתחילים בדרכם אל תרומתם הראשונה לקוד פתוח. + אם אתם מחפשים דרך לבצע תרומה ראשונית, עקבו אחר ההוראות הבאות. +
+ +
+

אם אינכם חשים בנוח להשתמש בשורת פקודה, ניתן להשתמש +בכלים גרפיים.

+
+ +
+

כמו כן, ניתן לקרוא את המאמר +בשפות אחרות.

+
+ + + +
+fork this repository +
+ +
+

בצעו FORK למאגר זה

+
+ +
+כדי לבצע FORK למאגר זה, ניתן ללחוץ על כפתור ה – FORK בתחילת העמוד. פעולה זה תיצור עותק של מאגר זה בחשבון שלכם. +
+ + +
+

שכפול המאגר

+
+ +
+ clone this repository +
+ +
+ +כעת, שכפלו את המאגר הזה למחשב שלכם. לכו לדף ה-GitHub שלכם, לחצו על כפתור השכפול ואז לחצו על הצלמית `copy to clipboard`. + +פתחו טרמינל והריצו את הפקודה הבאה: +
+ +``` +git clone "url you just copied" +``` +
+ +כאשר הביטוי `"url you just copied"` (ללא סימני הגרשיים) הוא הקישור למאגר זה שביצעתם עליו FORK קודם לכן. ראו את הצעדים הקודמים כדי להשיג את הקישור. +
+ +copy URL to clipboard + +
+לדוגמא: +
+ +``` +git clone https://github.com/this-is-you/first-contributions.git +``` +
+ +כאשר `this-is-you` הוא שם המשתמש שלכם ב-GitHub. לכאן אתם מעתיקים את התוכן של מאגר first-contributions ב-GitHub לתוך המחשב שלכם. +
+ +
+

יצירת ענף

+
+ +
+החליפו לתיקיית המאגר בתוך המחשב שלכם (אם אינכם נמצאים כבר בתיקייה זו ): +
+ +``` +cd first-contributions +``` +
+ +כעת, תצרו ענף בשימוש הפעולה `git checkout`: +
+ +``` +git checkout -b your-new-branch-name +``` +
+ לדוגמא: +
+ +``` +git checkout -b add-alonzo-church +``` + +
+(שם הענף לא חייב להכיל את המילה add בתוכו, אבל זה הגיוני להוסיף אותה מכיוון שמטרת הענף היא להוסיף את שמכם לרשימה.) +
+ +
+

ערכו שינויים הכרחיים ובצעו להם commit

+
+ +
+ +כעת פתחו את הקובץ `Contributors.md` בתוכנת עריכת טקסט והוסיפו את השם שלכם אליו. אל תוסיפו את השם בתחילת הקובץ או בסופו. הוסיפו אותו באמצע. לאחר שסיימתם, שמרו את הקובץ. + + +אם תנווטו לתיקיית הפרויקט ותבצעו את הפעולה `git status`, תוכלו לראות את השינויים שביצעתם שם. +הוסיפו את השינויים האלו לענף שיצרתם תוך שימוש בפקודה `git add`: +
+ +``` +git add Contributors.md +``` +
+ +עכשיו, בצעו commit לשינויים הללו תוך שימוש בפקודת `git commit`: +
+ +``` +git commit -m "Add to Contributors list" +``` +
+ +החליפו את הביטוי `` עם השם שלכם. +
+ +
+

לדחוף את השינויים ל-GitHub

+
+ +
+ +דחפו את השינויים תוך שימוש בפקודה `git push`: +
+ +``` +git push origin +``` +
+ +החליפו את `` עם השם של הענף שיצרתם מוקדם יותר. +
+ +
+

הגישו את השינויים שלכם לסקירה

+
+ +
+ +אם תלכו למאגר שלכם ב-GitHub, תוכלו לראות כפתור עם הכיתוב `Compare & pull request`. לחצו על כפתור זה. + +create a pull request + +כעת, הגישו את בקשת הדחיפה (pull request): + +submit pull request + +בקרוב, אני אצרף את כל השינויים לתוך הענף הראשי של פרויקט זה. אתם תקבלו עדכון במייל ברגע שהשינויים ימוזגו. +
+ +
+

מחקו את הענף שלכם אחרי שבקשת הדחיפה אושרה

+
+ +
+

מה לעשות מכאן?

+
+ +
+כל הכבוד! כרגע סיימתם את מעגל הזרימה הסטנדרטי של Fork->Clone->Edit->PR שאתם תפגשו באופן שכיח כתורמים! +תחגגו את התרומתכם ושתפו אותה עם החברים והעוקבים שלכם בכך שתלכו ל-web app. +
+אתם יכולים להצטרף לצוות הסלאק שלנו אם אתם צריכים עזרה או אם יש לכם שאלות. +הצטרפו לקבוצת סלאק. + +עכשיו אפשר להתחיל לתרום לפרוייקטים אחרים. הכנו רשימה של פרוייקטים על נושאים קלים שאתם יכולים להתחיל לעבוד עליהם. + +רשימה של פרוייקטים ב-web app. +
+ + + +
+

הדרכות בשימוש כלים אחרים

+
+ + diff --git a/translations/README.hi.md b/translations/README.hi.md new file mode 100644 index 00000000000..029e826f595 --- /dev/null +++ b/translations/README.hi.md @@ -0,0 +1,125 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) +# प्रथम योगदान + +इस परियोजना का उद्देश्य शुरुआती लोगों द्वारा अपना पहला योगदान देने के तरीके को सरल और मार्गदर्शन करना है। यदि आप अपना पहला योगदान देना चाहते हैं, तो नीचे दिए गए चरणों का पालन करें। + +आर्टिकल्स पढ़ना और ऑनलाइन ट्यूटोरियलज़ देखना मददगार साबित हो सकते हैं मगर बिना कुछ गलती करे खुद वो काम करने से अच्छा क्या हो सकता है? यह प्रोजेक्ट आपको आपके पहले कॉन्ट्रिब्यूशन के लिए दिशा निर्देशन में मदद करेगा । याद रखिये - जितने तनाव मुक्त होकर आप सीखेंगे उतना ही बेहतर सीख पाएंगे । यदि आप अपनी पहली कॉन्ट्रिब्यूशन करना चाहते हैं तो नीचे दिए गए निर्देशों का पालन करें । + +fork this repository + +यदि आपके कंप्यूटर पर Git नहीं है तो, [इसे स्थापित करें](https://help.github.com/articles/set-up-git/) । + +_यदि आप कमांड लाइन के साथ सहज नहीं हैं, [तो यहाँ ग्राफिकल इंटरफेस (GUI) टूल्स का उपयोग करने वाले ट्यूटोरियल हैं](#अन्य-टूल-का-उपयोग-करके-ट्यूटोरियल) ।_ + +## रिपॉज़िटरी को फॉर्क करना + +काँटा (फॉर्क) बटन पर क्लिक करके इस रिपॉज़िटरी को फॉर्क कर सकते हैं। यह आपके GitHub खाते (अकाउंट) में इस रिपॉज़िटरी की एक प्रति (कॉपी) बना देगा जो केवल आपके लिए उपलब्ध होगी। + +## रिपॉज़िटरी को क्लोन करना + +clone this repository + +अब आप यह रिपॉज़िटरी अपने कंप्यूटर में क्लोन (अर्थात् डाउनलोड) करें । अपने GitHub अकाउंट पर जाएँ, फोर्कड रिपोजिटरी खोलें, Code/कोड बटन पर क्लिक करें और फिर copy to clipboard आइकॉन पर क्लिक करें । + +अपने कंप्यूटर पर एक टर्मिनल/कमांड प्रांप्ट खोलें और निम्न git आदेश (कमांड) चलाएँ: + +``` +git clone "यूआरएल जिसे आपने अभी कॉपी किया" +``` + +जहाँ "यूआरएल जिसे आपने अभी कॉपी किया" (उद्धरण चिह्नों के बिना) इस रिपॉज़िटरी के लिए यूआरएल है (इस परियोजना का आपका फॉर्क) । यूआरएल प्राप्त करने के लिए पिछले चरण देखें । + +उदाहरण के लिए: + +``` +git clone https://github.com/यह-आप-हैं/first-contributions.git +``` + +copy URL to clipboard + +`यह-आप-हैं` आपके GitHub अकाउंट का नाम है। यहाँ आप अपने कंप्यूटर में GitHub से first-contributions रिपॉज़िटरी को कॉपी कर रहे हैं अथवा उसकी एक लोकल/स्थानीय कॉपी बना रहे हैं । + +## एक शाखा (ब्राँच) बनाएँ + +अपने कंप्यूटर पर बनाई गई रिपॉज़िटरी की कॉपी के फोल्डर/डायरेक्टरी में जाएँ (यदि अभी तक नहीं की है तो निम्न आदेश चलाएँ) + +``` +cd first-contributions +``` + +अब एक नई शाखा बनाएँ `git switch` कमांड का उपयोग करके । +नई शाखा बनाने के लिए -c ऑप्शन का उपयोग होता है । + +``` +git switch -c <अपनी-शाखा-का-नाम-जोड़ें> +``` + +उदाहरण के लिए: + +``` +git switch -c add-alonzo-church +``` + +( शाखा के नाम में `add` जोड़ने की आवश्यकता नहीं है, लेकिन इसमें शामिल होना जरूरी है क्योंकि इस शाखा का उद्देश्य एक सूची में अपना नाम जोड़ना है। ) + +## आवश्यक परिवर्तन करें और उन परिवर्तनों को कमिट करें- + +अब `Contributors.md` फ़ाइल को एक टेक्स्ट एडिटर में खोलकर इसमें अपना नाम लिखें। फ़ाइल की शुरुआत या अंत में इसे न जोड़ें। इसे बीच में कहीं भी रखें । + +git status + + +आप यदि `git status` कमांड चलाएंगे , तो आप किये गए परिवर्तन देखेंगे। + +उन परिवर्तनों को बनाई गई शाखा में जोड़ने के लिए `git add` कमांड का उपयोग करें । + +``` +git add Contributors.md +``` + +अब अपने किये गए बदलावों को कमिट करें `git commit` कमांड का उपयोग करके । + +``` +git commit -m "Add <आपका-नाम> to Contributors list" +``` + +<आपका-नाम> की जगह अपना नाम लिखें । + +## अपने बदलावों को Github में पुश करें । + +`git push` का उपयोग कर अपने परिवर्तन को पुश करें । + +``` +git push origin <अपनी-शाखा-का-नाम-जोड़ें> +``` + +`<अपनी-शाखा-का-नाम-जोड़ें>` की जगह अपनी शाखा का नाम लिखें । + +## अपने बदलावों को रिव्यु के लिए सबमिट करें । + +यदि आप अपने Github प्रोफाइल पर अपनी रिपॉज़िटरी में जायेंगे तो आपको Compare & pull request का ऑप्शन दिखेगा। उसे दबाएं । +create a pull request + +अब अपनी pull request सबमिट करें । + +submit pull request +जल्द ही मैं आपके बदलावों को इस प्रोजेक्ट की मास्टर शाखा में मर्ज कर दूंगा। आपको एक मेल आएगी जब आपके बदलाव मर्ज होंगे । + +## यहाँ से कहाँ जाएं ? + +बधाई! आपने _fork -> clone -> edit -> PR_ वर्कफ्लो की पूर्ति कर ली है, जिसका आप अक्सर एक योगदानकर्ता के रूप में सामना करेंगे! + +अपने पहले योगदान की खुशी में जश्न मनाएं तथा इसे [वेब एप्प](https://roshanjossey.github.io/first-contributions/#social-share) के जरिये अपने मित्रों के साथ शेयर करें। + +आप हमारी स्लैक टीम को ज्वाइन कर सकते हैं यदि आपको कुछ मदद चाहिए या आपके कोई प्रश्न हों । [स्लैक पे ज्वाइन करें](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) + +अब आप अन्य प्रोजेक्ट्स पर योगदान कर सकते हैं, तो चलिए शुरू करते हैं! हमने आपके लिए एक प्रोजेक्ट्स की सूचि तैयार की है जहाँ सरल इश्यूज हैं । आप चाहें तो वहाँ से आरम्भ कर सकते हैं । [प्रोजेक्ट्स कि लिस्ट](https://roshanjossey.github.io/first-contributions/#project-list) + +## शिक्षण अन्य साधनो का उपयोग करने के लिए + +|GitHub Desktop|Visual Studio 2017|GitKraken|VS Code|Sourcetree App| +|---|---|---|---|---| +|[GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md)|[Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md)|[GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md)|[Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md)|[Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md)| diff --git a/translations/README.hne.md b/translations/README.hne.md new file mode 100644 index 00000000000..91c119322de --- /dev/null +++ b/translations/README.hne.md @@ -0,0 +1,124 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) +# प्रथम योगदान + +पहली बार कुछू करे बर कठिन होथे| ख़ास तौर पर जब आपमन मिलकर काम करथव तब गलतियां करना बने बात नहीं आय | मगर आपस म मिलना अउ एक जुट होकर काम करे ल ही त ओपन सोर्स कइथे| हमन आप मन के पहला ओपन सोर्स कॉन्ट्रिब्यूशन/योगदान आसान बनाए बर आपमन की मदद करबो | + +आर्टिकल्स पढ़े अउ ऑनलाइन ट्यूटोरियल देखके मदद मिल सकत हे मगर बिना कुछू गलत करे अउ खुद वो काम करे ले बने अउ का हो सकत हे ? यह प्रोजेक्ट आपमन के पहले कॉन्ट्रिब्यूशन बर दिशा निर्देशन करे बर बने मदद करहि | याद रखौ - जतका तनाव मुक्त होकर आप मन सिखहु ततका आपमन बने सीख पाबौ | अगर आप मन अपन पहली कॉन्ट्रिब्यूशन करना चाहत हो त आगे दिए तरीका ल बने फॉलो करौ | + +fork this repository + +आपमन के कंप्यूटर म Git नहीं हे त, [एला स्थापित करौ](https://help.github.com/articles/set-up-git/) + +## रिपॉज़िटरी ल फॉर्क करे बर + +कांटा (फॉर्क) बटन म क्लिक करके ए रिपॉज़िटरी ल फॉर्क कर सकत हो| ए ह आपमन के GitHub खाते म इही रिपॉज़िटरी के एकठन प्रति (कॉपी) बना दिहि। + +## रिपोजिटरी क्लोन + +clone this repository + +अब आपमन ए रेपो ल अपन कंप्यूटर म क्लोन (डाउनलोड) करव| अपन GitHub खाते म जाकर क्लोन बटन म क्लिक करव अउ फिर कॉपी टू क्लिपबोर्ड आइकॉन म क्लिक करव | + +अपन कंप्यूटर म एक ठन टर्मिनल/कमांड प्रांप्ट खोलव अउ निम्न git आदेश चलावव: + +``` +git clone "यूआरएल जैला आपमन कॉपी करे हावव " +``` + +जेती "यूआरएल जैला आपमन कॉपी करे हावव" (उद्धरण चिह्नों के बिना) ए भंडार बर यूआरएल हे । यूआरएल प्राप्त करे बर पिछला चरण देखव । + +उदाहरण बर: + +``` +git clone https://github.com/यह-तै-हावस/first-contributions.git +``` + +copy URL to clipboard + +यह-तै-हावस आपमन के GitHub अकाउंट के नाम हावै। एती आपमन अपन कंप्यूटर न GitHub ले फर्स्ट-कंट्रिब्यूशंज़ रेपो ल कॉपी करथव अउ ओखर एक लोकल/स्थानीय कॉपी बनावथस| + +## एक ब्राँच बनाए बर + +अपन कंप्यूटर म बनाये गए रिपॉजिटरी के कॉपी के फोल्डर/डायरेक्टरी म जावव (अगर अब तक नहीं करे हावस त निम्न आदेश चलावव) + +``` +cd first-contributions +``` + +अब एक ठी नवा शाखा बनवाव `git checkout` कमांड के उपयोग करके | +नवा शाखा बनाए बर -b ऑप्शन के उपयोग होथे। + +``` +git checkout -b <अपन-शाखा-के-नाम-जोड़ें> +``` + +उदाहरण बर: + +``` +git checkout -b add-alonzo-church +``` + +( शाखा के नाम म `add` जोड़ने के आवश्यकता नहीं हावए, लेकिन एमा जोड़ना चल जाहि काबर की ए शाखा के उद्देश्य एक सूची म अपन नाम ल जोड़े बर हे। ) + +## आवश्यक परिवर्तन करे बर अउ उन परिवर्तनों ल कमिट करे बर- + +अब `Contributors.md` फ़ाइल ल एक टेक्स्ट एडिटर म खोलकर एमा अपन नाम लिखव। फ़ाइल के शुरुआत या अंत म एला झन जोड़बे। एला बीच म कही तिरिया देहु आपमन | + +git status + + +आपमन अगर `git status` निर्देश चलाहु , त आपमन ल किये गए परिवर्तन दिखहि। + +उन परिवर्तनों ल बनाए गए शाखा म जोड़े बर `git add` कमान्ड के उपयोग करव | + +``` +git add Contributors.md +``` + +अब अपन करे गए बदलाव ल कमिट करे बर `git commit` आदेश के उपयोग करव | + +``` +git commit -m "Add <अपन-नाम> to Contributors list" +``` + +<अपन-नाम> के जगह अपन नाम डालव| + +## अपन करे बदलाव ल Github म पुश करव| + +`git push` के उपयोग कर अपन परिवर्तन ल पुश करव| + +``` +git push origin <अपन-शाखा-के-नाम-जोड़व> +``` + +`<अपन-शाखा-के-नाम-जोड़व>` के जगह अपन शाखा के नाम डालव| + +## अपन बदलाव ल रिव्यु करे बर सबमिट करव| + +आपमन अपन github प्रोफाइल म अपन रेपो म जाबा अउ Compare & pull request ल दबवाव| +create a pull request + +आप मन के pull request सबमिट करव| + +submit pull request +मैं आपमन के बदलाव ल ए प्रोजेक्ट के मास्टर शाखा म तुरते मर्ज कर दुहु| आप मन ल एक ठन मेल आ जहि जब बदलाव मर्ज होही| + +## इहा ले कती जाबो? + +बधाई हो मितान! आपमन ने_fork -> clone -> edit -> PR_ वर्कफ़्लो ल पूरा कर डरे हव! + +अपन पहली योगदान के ख़ुशी म अपन संगी मन करा शेयर करव [वेब एप्प](https://roshanjossey.github.io/first-contributions/#social-share) पे जाके | + +आपमन हमर स्लैक टीम ल ज्वाइन कर सकत हव अगर आपमन ल कोनो सहायता के जरुरत होही त | [म ज्वाइन करव](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) + +अब आपमन अउ प्रोजेक्ट्स म कंट्रीब्यूट करे बर शुरू कर सकत हव | हमन एक लिस्ट बनाए हन जेन म अड़बड़ सरल मुद्दे हवएं| [प्रोजेक्ट्स के लिस्ट](https://roshanjossey.github.io/first-contributions/#project-list) + +## अन्य टूल के उपयोग करके ट्यूटोरियल + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + diff --git a/translations/README.hr.md b/translations/README.hr.md new file mode 100644 index 00000000000..760e234a4a8 --- /dev/null +++ b/translations/README.hr.md @@ -0,0 +1,124 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Prvi doprinosi + +Cilj ovog projekta je da pruži jednostavne korake za početnike da naprave svoje prve doprinose. Ukoliko tražite da napravite prvi doprinos pratite sljedeće korake ispod. + +#### _Ukoliko niste baš sigurni u vaš rad sa naredbnom linijom/terminalom, [ovdje možete pronaći tutorijale za GUI alate.](#Uputstva-za-druge-alate)_ + +Napravite fork repozitorijuma + +Ukoliko nemate git instaliran na vašom računalu, [instalirajte ga ovdje](https://help.github.com/articles/set-up-git/). + +## Napravite fork repozitorija + +Forkajte ovaj repozitorij tako da kliknete na dugme _fork_ na vrhu stranice. Ovako pravite kopiju repozitorija na vašoj github stranici. + +## Klonirajte repozitorij + +clone this repository + +Sada klonirajte repozitorij koji ste prethodno forkali. Posjetite svoj GitHub profil, otvorite repozitorij koji ste forkali, kliknite na _clone_ (kloniraj) dugme i kliknite na ikonicu _copy to clipboard_. + +Otvorite terminal i upišite slijedeće git naredbe: + +``` +git clone "url koji ste sada kopirali" +``` + +gdje je "url koji ste sada kopirali" (bez navodnika) url na ovaj repozitorij (vaš fork ovog projekta). Pogledajte prethodne korake kako dohvatiti url. + +copy URL to clipboard + +Na primjer: + +``` +git clone https://github.com/ovo-ste-vi/first-contributions.git +``` + +Gdje je umjesto `ovo-ste-vi` upisano vaše _github_ korisničko ime. Ovime kopirate sadržaj repozitorija _first-contributions_ na vaše računalo. + +## Pravljenje grane _branch_ + +Prebacite se u radni direktorij na vašem računalu (ukoliko već niste tamo): + +``` +cd first-contributions +``` + +Pa zatim napravite novu granu _branch_ koristeći `git switch` comandu: + +``` +git switch -c add-svoje-ime +``` + +Na primjer: + +``` +git switch -c add-alonzo-church +``` + +## Napravite potrebne izmjene i potvrdite promjene + +Otvorite `Contributors.md` datoteku u tekst editoru i dodajte vaše ime. Nemojte dodavati ime na sam početak ili kraj. Stavite ga negdje u sredinu. Potom sačuvajte datoteku. + +git status + +Ukoliko odete u radni direktorij i izvršite naredbu `git status`, primijetiti ćete da postoje promjene. + +Dodajte ove promjene u granu koju ste gore napravili koristeći `git add` naredbu: + +``` +git add Contributors.md +``` + +Sada potvrdite ove promjene koristeći `git commit` naredbu: + +``` +git commit -m "Add tvoje-ime to Contributors list" +``` + +Gdje umjesto `tvoje-ime` upisujete svoje ime. + +## Pushajte promjene na GitHub + +Pošaljite promjene u repozitorij na GitHub-u koristeći naredbu `git push`: + +``` +git push origin -u ime-vaše-grane +``` + +gdje umjesto `ime-vaše-grane` stavljate ime vaše grane koje ste prethodno napravili. + +## Pošaljite izmjene na pregled + +Ukoliko odete na repozitorij na vašem GitHub profilu primijetit ćete `Compare & pull request` Dugme. Kliknite na njega. + +create a pull request + +a zatim pošaljite zahtjev klikom na dugme _Create pull request_. + +submit pull request + +Nakon toga, vlasnik će spojiti promjene koje ste napravili sa master granom projekta. Dobit ćete mail potvrde kada se grane spoje. + +## Što dalje? + +Čestitamo! Završili ste standardni _fork -> clone -> edit -> PR_ tok koji će vas pratiti kroz vaš čitav programerski život! + +Proslavite tako što ćete podjeliti vaš doprinos sa prijateljima i pratiocima otvaranjem [stranice](https://firstcontributions.github.io/#social-share). + +Pridružite se i našem Slack timu u slučaju da vam je potrebna ikakva pomoć ili imate bilo kakvih pitanja. [Slack tim](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +A sada, možemo početi sa doprinosima drugim projektima. Napravili smo popis projekata sa jednostavnim problemima na kojima možete početi raditi. Posjetite [listu projekata na naštoj stranici](https://firstcontributions.github.io/#project-list). + +### [Dodatni materijali](../additional-material/git_workflow_scenarios/additional-material.md) + +## Uputstva za druge alate + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [GitHub Desktop](gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.hu.md b/translations/README.hu.md new file mode 100644 index 00000000000..8799401024c --- /dev/null +++ b/translations/README.hu.md @@ -0,0 +1,124 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Első közreműködés nyílt forráskodú projektben + +Minden kezdet nehéz, ezért szeretnénk segíteni számodra az első lépésekben ahhoz, hogy bátran kódolj kooperatívan nyílt forráskodú projekteket. Senki sem szeret hibázni, de szerencsére itt most nyugodtan megteheted. A lényeg, hogy gyakorolj! + +A projekt célja, hogy útmutatást nyújtson, egyszerűsítse és segítse a kezdők első lépéseit nyílt forráskódú szoftverek közös programozásában. Ha te is most készülsz először ilyet csinálni, segítünk neked, kövesd az alábbi lépéseket. + +#### *Ha a parancssor kényelmetlen, [itt egy tutorial a GUI felület használatához.](#Oktatóanyagok-más-eszközök-használatával)* + +forkold ezt a repót + +Ha nincs a gépeden git, [telepítsd fel]( https://help.github.com/articles/set-up-git/). + +## Ágaztasd ezt a repót (fork) + +A Fork gomb kattintásával ágaztasd el ezt a repót. +Ezzel készítettél egy másolatot erről a reporól a te saját git fiókodba. + +## Klónozd a repót (clone) + +klónozd ezt a repót + +Most klónozd az elágaztatott repót a gépedre. Menj a GitHub fiókodra, nyisd meg a forkolt repositoryt, kattints a clone gombra, majd kattints a *copy to clipboard* ikonra. + +Nyiss egy terminált és futtasd a következő parancsot: + +``` +git clone "url-amit-most-masoltal-le" +``` +A "url-amit-most-masoltal-le" kifejezést, cseréld ki (idézőjelek nélkül) a vágólapra helyezett repository url címére (ami ebből a projektől ágazik). Az ágaztatás folyamatát lásd az előző lépésben. + +másold az URL címet a vágólapra + +Például: +``` +git clone https://github.com/a-te-git-neved/first-contributions.git +``` +A `a-te-git-neved` lesz a GitHub felhasználóneved. Ezzel letöltöd a first-contributions repositoryt GitHub-ról a saját számítógépedre. + +## Készíts egy ágat (branch) + +Navigálj a repository könytárába (ha nem ott vagy jelenleg): + +``` +cd first-contributions +``` + +Most készítsünk egy ágat `git checkout` parancs használatával: + +``` +git switch -c +``` + +Például: +``` +git switch -c add-gabor-takacs +``` +(A branch nevében nem kötelező, hogy benne legyen az *add* szó, de észszerű belefoglalni, mert ennek az ágnak az a célja, hogy hozzáadja a nevünket egy listához.) + +## Végezd el a szükséges változtatásokat és rögzítsd azokat (commit) + +Nyisd meg a `Contributors.md` fájlt egy szövegszerkesztőben, majd add hozzá a neved. Ne a fájl elejére vagy végére helyezd, hanem a kettő közé. A kettő között bárhová teheted. Mentsd el a fájlt. + +git status + + +Ha a project könyvtárába navigálsz és futtatod a `git status` parancsot, akkor a következő módosításokat fogod látni: + + +Ezeket a módosításokat add hozzá a branchez a `git add` paranccsal: + +``` +git add Contributors.md +``` + +Commitoljuk a módosításokat a `git commit` paranccsal: +``` +git commit -m "Add to Contributors list" +``` +Helyettesítsd `` kifejezést a saját neveddel. + +## Töltsd fel az elkészült változtatásokat a GitHub-ra (push) + +Töltsd fel a változtatásokat a `git push` paranccsal: +``` +git push origin +``` +Helyettesítsd az `` kifejezést annak a branchnek a nevével, amit korábban létrehoztál. + +## Küldd be a módosításaidat ellenőrzésre (pull request) + +Ha a saját repódba navigálsz GitHub-on, látnod kell a `Compare & pull request` gombot. Kattints rá! + +pull request készítése + +Sikeresen elküldted a pull requested. + +pull request beküldése + +Kis idő elteltével összevonja a változásokat a project fő ágában. Értesítést fogsz kapni emailben, ha a változások összefűzésre kerültek. + +## Hogyan tovább? + +Gratulálunk! Sikeresen teljesítetted az alapvető _fork -> clone -> edit -> PR_ folyamatot, melyet gyakran kell majd csinálnod közreműködőként! + +Ünnepeld meg az első kooperációdat és oszd meg barátaiddal és követőiddel ennek a [web app](https://firstcontributions.github.io/#social-share)-nak a segítségével. + +Bármilyen kérdésed van vagy segítségre lenne szükséged, csatlakozz slack csapatunkhoz. [Csatlakozz a slack csapathoz.](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Itt az idő egy másik projektben is közreműködni. Összeállítottunk egy listát azokról a projektekről, melyek könnyebb feladatokat tartalmaznak az induláshoz. Nézd meg a [projektek listáját](https://firstcontributions.github.io/#project-list) a webalkalmazásban. + +### [Kiegészítő anyag](../additional-material/git_workflow_scenarios/additional-material.md) + + +## Oktatóanyagok más eszközök használatával + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.hy.md b/translations/README.hy.md new file mode 100644 index 00000000000..e73401ddf6d --- /dev/null +++ b/translations/README.hy.md @@ -0,0 +1,136 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Առաջին ներդրումները(contributions) + +Այս նախագիծը նպատակ ունի պարզեցնել և առաջնորդել սկսնակներին իրենց առաջին ներդրման ճանապարհին: Եթե ցանկանում եք կատարել ձեր առաջին ներդրումը, հետևեք ստորև նշված քայլերին: + +_Եթե հրամանի տողը (command line) ձեզ հարմար չէ, [ահա ուղեցույցներ գրաֆիկական ինտերֆեյսի (GUI) կիրառմամբ.](#Ուղեցույցներ-այլ-գործիքների-կիրառմամբ)_ + +fork this repository + +#### Եթե դուք չունեք git ձեր մեքենայի վրա, [տեղադրեք այն](https://help.github.com/articles/set-up-git/) + +## Ճյուղավորեք (fork) այս պահոցը (repository) + +Ստեղծեք ձեր սեփական պատառաքաղը՝ սեղմելով այս էջի վերևում գտնվող `fork` կոճակը: +Դա կստեղծի այս պահոցի պատճենը ձեր հաշվում: + +## Կլոնավորեք պահոցը + +clone this repository + +Հիմա կլոնավորեք պահոցը ձեր համակարգչում: Հղումը պատճենելու համար սեղմեք `clone` կոճակը, այնուհետև `copy to clipboard` պատկերակը: + +Բացեք տերմինալը և գործարկեք հետևյալ git հրամանը. + +``` +git clone "url you just copied" +``` + +Որտեղ "url you just copied"-ը (առանց չակերտների) ձեր պահոցի հղումն է (այս նախագծի ձեր ճյուղավորումը). Հետևեք նախորդ քայլերին, որպեսզի ստանաք հղումը. + +copy URL to clipboard + +Օրինակ՝ + +``` +git clone https://github.com/this-is-you/first-contributions.git +``` + +Որտեղ `this-is-you`-ն github-ի ձեր մուտքանունն է. Այսպիսով դուք պատճենում եք first-contributions պահոցը GitHub-ից ձեր համակարգչի վրա: + +## Ստեղծեք ճյուղ + +Անցեք ձեր համակարգչում գտնվող պահոցը, եթե արդեն այնտեղ չեք։ + +``` +cd first-contributions +``` + +Հիմա ստեղծեք նոր ճյուղ՝ օգտագործելով `git checkout` հրամանը․ + +``` +git checkout -b +``` + +Օրինակ՝ + +``` +git checkout -b add-alonzo-church +``` + +## Կատարեք անհրաժեշտ փոփոխությունները և գործադրեք (commit) + +Հիմա բացեք `Contributors.md` ֆայլը ձեր տեքստային խմբագրիչում, գրեք ձեր անունը և պահպանեք ֆայլը։ Մի ավելացրեք այն ֆայլի սկզբում կամ վերջում: Տեղադրեք այն որևէ տեղ մեջտեղում: Այժմ պահպանեք ֆայլը: + +git status + +Եթե գնաք նախագծի պանակ և կատարեք `git status` հրամանը, կտեսնեք, որ փոփոխություններ կան: + +Ավելացրեք այդ փոփոխությունները այն ճյուղին, որը հենց նոր ստեղծեցիք՝ օգտագործելով `git add` հրամանը. + +``` +git add Contributors.md +``` + +Այժմ գործադրեք այս փոփոխությունները `git commit` հրամանով. + +``` +git commit -m "Add to Contributors list" +``` + +Փոփոքեք ``-ը ձեր անունով + +## Push արեք փոփոխությունները github + +Push արեք ձեր փոփոխությունները `git push` հրամանով․ + +``` +git push origin +``` + +Փոփոխոք ``-ը ավելի վաղ ստեղծած ճյուղի անունով: + +
+ Եթե push անելիս սխալներ եք ստանում, սեղմեք այստեղ՝ + +* ### Authentication Error + 
remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead.
+  remote: Please see https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ for more information.
+  fatal: Authentication failed for 'https://github.com//first-contributions.git/'
+ Go to [GitHub's tutorial](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account) on generating and configuring an SSH key to your account. + +
+ +## Հաստատեք փոփոխությունները վերանայման համար + +Եթե այցելեք ձեր GitHub պահոցը, կտեսնեք `Compare & pull request` կոճակը։ Սեղմեք այդ կոճակը։ + +create a pull request + +Ապա հաստատեք pull հարցումը: + +submit pull request + +Շուտով ես կմիավորեմ ձեր բոլոր փոփոխությունները այս նախագծի գլխավոր մասնաճյուղի մեջ: Փոփոխությունները միաձուլվելուց հետո դուք կստանաք ծանուցող նամակ: + +## Ու՞ր գնալ այստեղից + +Շնորհավորանքնե՛րս, դուք հենց նոր ավարտեցիք ստանդարտ _fork -> clone -> edit -> pull request_ աշխատակարգը, որը հաճախ կհանդիպեք որպես ներդրող: + +Նշեք ձեր ներդրումը և կիսվեք այն ձեր ընկերների և հետևորդների հետ՝ այցելելով [web app](https://firstcontributions.github.io/#social-share). + +Դուք կարող եք միանալ մեր Slack թիմին, եթե որևէ հարց կամ օգնության կարիք ունեք։ [Միանալ slack թիմին](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Հիմա կարող եք ձեր ներդրումն ունենալ այլ նախագծերում։ Մենք կազմել ենք հեշտ խնդիրներ ունեցող նախագծերի ցանկ, որոնցից կարող եք սկսել: Համեցեք [վեբ հավելվածի նախագծերի ցանկը](https://firstcontributions.github.io/#project-list). + +### [Լրացուցիչ նյութեր](additional-material/git_workflow_scenarios/additional-material.md) + +## Ուղեցույցներ այլ գործիքների կիրառմամբ + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.id.md b/translations/README.id.md new file mode 100644 index 00000000000..c5b35abcff5 --- /dev/null +++ b/translations/README.id.md @@ -0,0 +1,139 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Kontribusi Pertama + +Proyek ini memiliki tujuan yaitu untuk menyederhanakan dan membimbing pemula untuk membuat kontribusi pertamanya di Github. Jika Anda ingin membuat kontribusi pertama mu, ikuti langkah-langkah berikut. + + +#### _Jika Anda tidak terbiasa dengan baris perintah, [di sini ada tutorial untuk menggunakan GUI.](#Tutorial-Menggunakan-Alat-Lain)_ + +fork this repository + +Apabila Anda belum menginstall git di komputer anda, [ install segera ](https://help.github.com/articles/set-up-git/). + +## *Fork* Repositori Ini + +Fork repositori ini dengan cara klik tombol *fork* yang ada di bagian atas kanan pada halaman ini. +Dan repository ini akan disalin ke akun anda. + +## *Clone* Repositori + +clone this repository + +Sekarang klon repositori yang sudah Anda *fork* di akun Github anda ke komputer anda. Buka akun GitHub Anda, buka repository yang sudah di *fork*, Klik tombol *Code* dan kemudian klik ikon salin ke papan klip. + +Buka terminal dan jalankan perintah git berikut: + +``` +git clone "url yang telah disalin" +``` + +bagian "url yang telah disalin" (tanpa tanda petik) adalah url ke repositori ini (proyek yang telah anda *fork* ini). Lihat langkah sebelumnya untuk mendapatkan url. + +copy URL to clipboard + +Contoh: + +``` +git clone https://github.com/ini-adalah-anda/first-contributions.git +``` + +bagian `ini-adalah-anda` adalah *username* GitHub Anda. Disini Anda menyalin konten dari repositori first-contributions di GitHub ke komputer Anda. + +## Membuat Cabang (Branch) + +Pindah ke direktori repositori yang terdapat pada komputer Anda (jika Anda belum ada di sana): + +``` +cd first-contributions +``` + +Sekarang buat cabang dengan menggunakan perintah `git checkout`: + +``` +git checkout -b +``` + +Contohnya: + +``` +git checkout -b add-alonzo-church +``` + + +## Buat Perubahan yang Diperlukan Lalu Commit Perubahan Tersebut + +Sekarang buka Folder `Contributors.md` menggunakan teks editor, tambahkan nama Anda ke dalamnya. Jangan menambahkan pada awal atau akhir dari file. Simpan dimana saja di antaranya. Sekarang simpan filenya. + +git status + +Jika Anda pergi ke direktori proyek dan mengeksekusi perintah `git status`, Anda akan melihat ada perubahan. + +Tambahkan perubahan tersebut ke cabang yang baru saja Anda buat menggunakan perintah `git add`: + +``` +git add Contributors.md +``` + +Sekarang simpan perubahan tersebut menggunakan perintah `git commit`: + +``` +git commit -m "Add to Contributors list" +``` + +Ubah bagian `` dengan nama anda. + +## Dorong (Push) Perubahan ke GitHub + +*Push* perubahan menggunakan perintah `git push`: + +``` +git push origin +``` + +ganti bagian `` dengan nama cabang yang sebelumnya Anda buat. + +
+ Jika Anda mendapatkan kesalahan saat melakukan push, klik disini: + +- ### Kesalahan otentikasi + 
remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead.
+  remote: Please see https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ for more information.
+  fatal: Authentication failed for 'https://github.com//first-contributions.git/'
+ Buka [GitHub's tutorial](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account) untuk menghasilkan dan mengonfigurasi kunci SSH ke akun Anda. + +
+ +## Kirim Perubahan untuk Diperiksa + +Jika Anda membuka repositori Anda di GitHub, Anda akan melihat sebuat tombol `Compare & pull request`. Tekan tombol tersebut. + +create a pull request + +Sekarang kirimkan *Pull Request* (PR) + +submit pull request + +Saya (pengelola) akan segera menggabungkan semua perubahan Anda ke cabang utama dari proyek ini. Anda akan mendapatkan email pemberitahuan setelah perubahan digabungkan. + +## Ke Mana Lagi Setelah dari Sini? + +Selamat! Anda baru saja menyelesaikan standar *fork* -> *clone* -> ubah -> *Pull Request* sebuah alur kerja yang akan sering Anda temui sebagai kontributor! + +Rayakan kontribusi Anda dan bagikan dengan teman dan pengikut Anda dengan membuka [web app](https://roshanjossey.github.io/first-contributions/#social-share). + +Anda dapat bergabung dengan tim slack kami jika membutuhkan bantuan atau memiliki pertanyaan. [Bergabung dengan tim slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Sekarang, mari kita mulai dengan berkontribusi di proyek lain. Kami sudah menyusun daftar proyek dengan isu yang mudah dikerjakan sehingga Anda dapat segera memulai. Cek di [daftar proyek web app](https://roshanjossey.github.io/first-contributions/#project-list). + +## [ Materi tambahan ](../additional-material/translations/additional-material.id.md) + +## Tutorial Menggunakan Alat Lain + + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.igb.md b/translations/README.igb.md new file mode 100644 index 00000000000..816f7d8e280 --- /dev/null +++ b/translations/README.igb.md @@ -0,0 +1,128 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Onyinye Mbụ + +O siri ike. Ọ na-esiri gị ike mgbe mbụ i mere ihe. Karịsịa mgbe ị na-emekọ ihe, imehie ihe abụghị ihe dị mma. Anyị chọrọ ime ka ụzọ ndị ọhụrụ na-emeghe emeghe na-amụta ma tinye aka maka oge mbụ. + +Ịgụ isiokwu & nkuzi ntanetị nwere ike inyere gị aka, ma gịnị dị mma karịa ime ihe ahụ na-eme ihe omume? Ihe oru a bu iji nye nduzi & mee ka ndi mmadu bidoro ibu onyinye mbu. Ọ bụrụ na ị na-achọ ime onyinye mbụ gị, gbasoo nzọụkwụ dị n'okpuru. + +#### _Ọ bụrụ na ị naghị enwe mmasị na akara iwu, [ebe a bụ nkuzi na-eji ngwaọrụ GUI.](#Nkuzi-na-iji-ihe-ndi-ozo)_ + +fork this repository + +Ọ bụrụ na ịnweghị igwe na igwe gị, [wụnye ya](https://help.github.com/articles/set-up-git/). + +## Wepu ebe nchekwa a + +Wepu a repo site na ịpị bọtịnụ mkpịsị aka n'elu nke ibe a. Nke a ga-emepụta otu ntinye nchekwa a na akaụntụ gị. + +## Na-ekpuchi ebe nchekwa + +clone this repository + +Ugbu a, dochie ya repo na igwe gị. Gaa na akaụntụ GitHub gị, meghee repo ahụ maka pịa, pịa bọtịnụ clone ma pịazie ya na akara ngosi akara ngosi. + +Mepee ọnụ ma jikwa iwu na-esonụ: + +``` +git clone "url you just copied" +``` + +ebe "url na ị depụtaghachiri" (na-enweghị ntinye ọnụ) bụ url maka nchekwa ebe a (mgbịrịgwụ nke ọrụ a). Hụ nzọụkwụ ndị gara aga iji nweta url. + +copy URL to clipboard + +Ọmụmaatụ: + +``` +git clone https://github.com/this-is-you/first-contributions.git +``` + +ebe `this-is-you` ka aha njirimara GitHub gị. Lee, ị na-edegharị ọdịnaya nke onyinye ntinye mbụ na GitHub na kọmputa gị. + +## Mepụta alaka + +Gbanwee na nhazi ndekọ na kọmputa gị (ọ bụrụ na ịnweghị ebe ahụ): + +``` +cd first-contributions +``` + +Ugbu a, mepụta alaka ụlọ ọrụ site na iji `git checkout` iwu: + +``` +git checkout -b +``` + +Ọmụmaatụ: + +``` +git checkout -b add-alonzo-church +``` + +(Aha alaka ahụ adịghị mkpa iji tinye okwu ahụ n'ime ya, ma ọ bụ ihe dị mkpa ị gụnyere n'ihi na ebumnuche nke alaka a bụ ịgbakwunye aha gị na ndepụta.) + +## Mee mgbanwe ndị dị mkpa ma mee mgbanwe ndị ahụ + +Ugbu a mepee `Contributors.md` faịlụ na nchịkọta ederede, tinye aha gị na ya. Adakwunye ya na mmalite ma ọ bụ njedebe nke faịlụ ahụ. Tinye ya n'ebe ọ bụla n'etiti. Ugbu a, chekwaa faịlụ ahụ. + +git status + +Ọ bụrụ na ịga na ndekọ ụlọ ọrụ ma mebie iwu ahụ `git status`, ị ga-ahụ na e nwere mgbanwe. + +Tinye mgbanwe ndị a n'alaka ụlọ ọrụ ị mepụtara site na iji `git add` iwu ahụ: + +``` +git add Contributors.md +``` + +Ugbu a mee mgbanwe ndị ahụ site na iji `git commit` iwu ahụ: + +``` +git commit -m "Add to Contributors list" +``` + +jiri aha gị dochie ``. + +## Kwanye mgbanwe nile a n'ime GitHub + +Mee mgbanwe gị site na iji iwu `git push`: + +``` +git push origin +``` + +dochie `` aha alaka ụlọ ọrụ ị mepụtara n'oge gara aga. + +## Nyefee mgbanwe gị maka nyocha + +Ọ bụrụ na ị gaa ebe nchekwa gị na GitHub, ị ga-ahụ `Compare & pull request` bọtịnụ. Pịa bọtịnụ ahụ. + +create a pull request + +Ugbu a, rịọ arịrịọ ahụ. + +submit pull request + +N'oge na-adịghị anya, m ga-emeri mgbanwe gị niile n'ime ngalaba alaka ụlọ ọrụ a. Ị ga-enweta ozi ngosi mgbe ọ bụla emetụtara mgbanwe. + +## Ebee ka esi aga ebe a? + +Ekele! Naanị ị gụchara ihe nkesa -> mmepụta oyiri -> dezie -> Bọpụ ọrụ PR nke ị ga-ezute mgbe niile dị ka onye na-enye gị! + +Nalee onyinye gị ma soro ndị enyi gị na ụmụazụ gị kerịta ya site na ịga na [ngwa weebụ](https://roshanjossey.github.io/first-contributions/#social-share). + +Ị nwere ike isonyere ndị ọrụ anyị na-adịghị mma na ikpe ịchọrọ enyemaka ọ bụla ma ọ bụ nwee ajụjụ ọ bụla. [Jikọọ slack otu](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Ugbu a, ka anyị malite site na inye onyinye maka ọrụ ndị ọzọ. Anyị ejikọtawo ndepụta nke oru na okwu dị mfe ị nwere ike ịmalite. Lelee [ndepụta nke oru na ngwa weebụ ](https://roshanjossey.github.io/first-contributions/#project-list). + +### [Ihe ndi ozo](../additional-material/git_workflow_scenarios/additional-material.md) + +## Nkuzi na iji ihe ndi ozo + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.it.md b/translations/README.it.md new file mode 100644 index 00000000000..e85cccefd33 --- /dev/null +++ b/translations/README.it.md @@ -0,0 +1,117 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Il primo contributo + +È dura. È sempre difficile fare qualcosa per la prima volta. Specialmente quando si sta collaborando, sbagliare ci mette a disagio. Ma l'open source si basa sulla collaborazione e sul lavorare insieme. Pertanto volevamo semplificare il modo in cui i nuovi collaboratori imparano e contribuiscono per la prima volta a progetti open-source. + +Leggere articoli e guardare tutorial può essere utile, ma cosa c'è di meglio che provare a fare effettivamente le cose sul campo? Questo progetto punta ad essere una guida per i meno esperti. Ricorda: più sei rilassato, meglio imparerai. Se vuoi contribuire per la prima volta, segui i semplici passi elencati qui sotto. Ti promettiamo che sarà divertente. + +fork this repository + +Se non hai git sul tuo computer, [installalo]( https://help.github.com/articles/set-up-git/). + +## Forka questa repository + +Forka questa _repo_ (abbreviazione di _repository_, ossia una cartella) cliccando sul bottone **_fork_** in cima alla pagina. +Questo creerà una copia di questa repository nel tuo account. + +## Clona la repository + +clone this repository + +Ora clona questa repo nel tuo computer. Clicca sul pulsante per clonare e poi copia l'url. + +Apri il terminale e lancia il seguente comando: + +``` +git clone "url appena copiato" +``` +dove "url appena copiato" (senza le virgolette) è l'url di questa repository. Leggi i passaggi precedenti per ottenere l'url. + +copy URL to clipboard + +Per esempio: +``` +git clone https://github.com/questo-sei-tu/first-contributions.git +``` +dove `questo-sei-tu` è il tuo username GitHub. Qui stai copiando il contenuto della repository da GitHub al tuo computer. + +## Crea un branch + +Entra nella directory della repository (se non lo hai già fatto): + +``` +cd first-contributions +``` +Ora crea un branch usando il comando `git checkout -b`: +``` +git checkout -b +``` + +Ad esempio: +``` +git checkout -b aggiungi-alonzo-church +``` +(Non è necessario inserire la parola *aggiungi* nel nome del branch, ma in questo caso è ragionevole includerlo poiché lo scopo di questo branch è aggiungere il tuo nome alla lista. +Lo scopo di nominare un branch è descrivere le modifiche che andremo ad effettuare, il nome deve essere quindi descrittivo e non generale per facilitare il team con cui si collabora.) + +## Fai le modifiche necessarie e crea un commit + +Ora apri il file `Contributors.md` in un editor, inserisci il tuo nome. Non aggiungerlo all'inizio o alla fine del file ma in un qualsiasi punto nel mezzo. Ora salva il file. Se vai nella directory del progetto ed esegui il comando `git status`, vedrai quali sono i cambiamenti. Aggiungi le modifiche al branch appena creato usando il comando `git add`: +``` +git add Contributors.md +``` + +Crea ora una commit che includa le modifiche da te fatte, usando `git commit`: +``` +git commit -m "Add to Contributors list" +``` +cambiando `` con il tuo nome. + +## Invia le modifiche a GitHub + +Invia le tue modifiche con il comando `git push`: +``` +git push origin +``` +sostituendo `` con il nome del branch creato prima. + +## Invia i tuoi cambiamenti per una revisione + +Se vai nella tua repository su GitHub, vedrai il pusante `Compare & pull request`. Cliccalo. + +create a pull request + +Ora invia la pull request. + +submit pull request + +Presto avrò incorporato (*merge*) tutti i tuoi cambiamenti nel master branch di questo progetto. Ti arriverà una mail di notifica una volta che le modifiche saranno state accettate. + +### [ Prossimi passi ](../additional-material/git_workflow_scenarios/additional-material.md) + +## Tutorial usando altri tool + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + +## E ora? + +Unisciti alla nostra squadra su slack in caso tu abbia bisogno di aiuto o abbia qualche domanda. Proveremo ad aiutarti! [Unisciti alla squadra Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Qui sotto puoi trovare delle repo popolari dove cercare problemi semplici da cui partire. Continua nelle repo per imparare di più + +|[![exercism](https://avatars2.githubusercontent.com/u/5624255?v=3&s=100)](https://github.com/exercism/exercism.io/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+patch%22)|[![fun-retro](https://avatars3.githubusercontent.com/u/15913975?v=3&s=100)](https://github.com/funretro/distributed/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly)|[](https://github.com/facebook/react/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+bug%22)|[![habitat](https://avatars1.githubusercontent.com/u/18171698?v=3&s=100)](https://github.com/habitat-sh/habitat/issues?q=is%3Aopen+is%3Aissue+label%3AEasy)|[![scikit-learn](https://avatars0.githubusercontent.com/u/365630?v=3&s=100)](https://github.com/scikit-learn/scikit-learn/issues?q=is%3Aopen+is%3Aissue+label%3AEasy)|[](https://github.com/technomancy/leiningen/issues?q=is%3Aopen+is%3Aissue+label%3ANewbie)|[](https://github.com/numpy/numpy/issues?q=is%3Aopen+is%3Aissue+label%3A%22Easy+Fix%22)|[![elasticsearch](https://avatars2.githubusercontent.com/u/6764390?v=3&s=100)](https://github.com/elastic/elasticsearch/issues?q=is%3Aopen+is%3Aissue+label%3A%22low+hanging+fruit%22)| +|---|---|---|---|---|---|---|---| +|[exercism](https://github.com/exercism/exercism.io/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+patch%22)|[Fun Retros](https://github.com/funretro/distributed/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly)|[react](https://github.com/facebook/react/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+bug%22)|[habitat](https://github.com/habitat-sh/habitat/issues?q=is%3Aopen+is%3Aissue+label%3AEasy)|[scikit-learn](https://github.com/scikit-learn/scikit-learn/issues?q=is%3Aopen+is%3Aissue+label%3AEasy)|[Leiningen](https://github.com/technomancy/leiningen/issues?q=is%3Aopen+is%3Aissue+label%3ANewbie)|[numpy](https://github.com/numpy/numpy/issues?q=is%3Aopen+is%3Aissue+label%3A%22Easy+Fix%22)|[elasticsearch](https://github.com/elastic/elasticsearch/issues?q=is%3Aopen+is%3Aissue+label%3A%22low+hanging+fruit%22)| +|[![homebrew](https://avatars2.githubusercontent.com/u/1503512?v=3&s=100)](https://github.com/Homebrew/brew/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22)|[![rust](https://avatars1.githubusercontent.com/u/5430905?v=3&s=100)](https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Aissue+label%3AE-easy)|[![vuejs](https://avatars1.githubusercontent.com/u/6128107?v=3&s=100)](https://github.com/vuejs/vue/issues?q=is%3Aopen+is%3Aissue+label%3A%22contribution+welcome%22)|[![Suave](https://avatars2.githubusercontent.com/u/5822862?v=3&s=100)](https://github.com/SuaveIO/suave/issues?q=is%3Aopen+is%3Aissue+label%3Ahardness-easy)|[![OpenRA](https://avatars3.githubusercontent.com/u/409046?v=3&s=100)](https://github.com/OpenRA/OpenRA/issues?q=is%3Aopen+is%3Aissue+label%3AEasy)|[![PowerShell](https://avatars0.githubusercontent.com/u/11524380?v=3&s=100)](https://github.com/powershell/powershell/issues?q=is%3Aopen+is%3Aissue+label%3AUp-for-Grabs)|[![coala](https://avatars2.githubusercontent.com/u/10620750?v=3&s=100)](https://github.com/coala/coala/issues?q=is%3Aopen+is%3Aissue+label%3Adifficulty%2Flow+label%3Adifficulty%2Fnewcomer)|[![moment](https://avatars2.githubusercontent.com/u/4129662?v=3&s=100)](https://github.com/moment/moment/issues?q=is%3Aopen+is%3Aissue+label%3AUp-For-Grabs)| +|[homebrew](https://github.com/Homebrew/brew/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22)|[Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Aissue+label%3AE-easy)|[vuejs](https://github.com/vuejs/vue/issues?q=is%3Aopen+is%3Aissue+label%3A%22contribution+welcome%22)|[Suave](https://github.com/SuaveIO/suave/issues?q=is%3Aopen+is%3Aissue+label%3Ahardness-easy)|[OpenRA](https://github.com/OpenRA/OpenRA/issues?q=is%3Aopen+is%3Aissue+label%3AEasy)|[PowerShell](https://github.com/powershell/powershell/issues?q=is%3Aopen+is%3Aissue+label%3AUp-for-Grabs)|[coala](https://github.com/coala/coala/issues?q=is%3Aopen+is%3Aissue+label%3Adifficulty%2Flow+label%3Adifficulty%2Fnewcomer)|[moment](https://github.com/moment/moment/issues?q=is%3Aopen+is%3Aissue+label%3AUp-For-Grabs)| +|[![ava](https://avatars0.githubusercontent.com/u/8527916?v=3&s=100)](https://github.com/avajs/ava/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+for+beginner%22)|[![freeCodeCamp](https://avatars0.githubusercontent.com/u/9892522?v=3&s=100)](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only)|[![webpack](https://avatars3.githubusercontent.com/u/2105791?v=3&s=100)](https://github.com/webpack/webpack/issues?q=is%3Aopen+is%3Aissue+label%3A%22D1%3A+Easy+%28Contrib.+Difficulty%29%22)|[![hoodie](https://avatars1.githubusercontent.com/u/1888826?v=3&s=100)](https://github.com/hoodiehq/hoodie/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only)|[![pouchdb](https://avatars3.githubusercontent.com/u/3406112?v=3&s=100)](https://github.com/pouchdb/pouchdb/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22)|[![neovim](https://avatars0.githubusercontent.com/u/6471485?v=3&s=100)](https://github.com/neovim/neovim/issues?q=is%3Aopen+is%3Aissue+label%3Aentry-level)|[![babel](https://avatars2.githubusercontent.com/u/9637642?v=3&s=100)](https://github.com/babel/babel/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly) |[](https://github.com/adobe/brackets/labels/Starter%20bug)| +|[ava](https://github.com/avajs/ava/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+for+beginner%22)|[freeCodeCamp](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only)|[webpack](https://github.com/webpack/webpack/issues?q=is%3Aopen+is%3Aissue+label%3A%22D1%3A+Easy+%28Contrib.+Difficulty%29%22)|[hoodie](https://github.com/hoodiehq/hoodie/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only)|[pouchdb](https://github.com/pouchdb/pouchdb/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22)|[neovim](https://github.com/neovim/neovim/issues?q=is%3Aopen+is%3Aissue+label%3Aentry-level)|[babel](https://github.com/babel/babel/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly) |[brackets](https://github.com/adobe/brackets/labels/Starter%20bug)| +| [![Node.js](https://avatars1.githubusercontent.com/u/9950313?v=3&s=100)](https://github.com/nodejs/node/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22)|[](https://github.com/Semantic-Org/Semantic-UI-React/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22)| +| [Node.js](https://github.com/nodejs/node/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22) |[Semantic-UI-React](https://github.com/Semantic-Org/Semantic-UI-React/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22) | diff --git a/translations/README.ja.md b/translations/README.ja.md new file mode 100644 index 00000000000..319986b8144 --- /dev/null +++ b/translations/README.ja.md @@ -0,0 +1,116 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# First Contributions + +初めてのことは何でも大変なものです。特に他人と協力する時はそうで、間違うのは気持ちの良いことではありません。しかし、オープンソースにおける活動では協力することが全てです。私たちは初めてオープンソースへの貢献を始める人たちが簡単に貢献する方法を学べるようにしたいと考えています。 + +記事を読んだりチュートリアルをやってみることはためになりますが、実際にやってみる方が良いでしょう。このプロジェクトはそのガイダンスを行い、初心者が最初のオープンソースへの貢献を簡単に行えるようにするためのものです。 +覚えておいてください: リラックスしているほどより良く学ぶことができます。もし初めてのオープンソースへの貢献を行いたいのなら以下の簡単なステップに従ってください。それはとても面白いものになるはずです。 + +#### *コマンドラインでの操作に慣れていない場合、[グラフィカルなツールでもチュートリアルを行えます。]( #その他のツールを使用したチュートリアル )* + +fork this repository + +まだGitをインストールしていない場合は、[ここ](https://help.github.com/articles/set-up-git/)からインストールしてください + +## レポジトリをフォーク + +Forkボタンをクリックしてこのレポジトリをフォークしてください。 +この作業はあなたのアカウントにこのレポジトリのコピーを作ります。 + +## レポジトリをクローン + +clone this repository + +次にレポジトリをクローンします。*Clone and download*ボタンをクリックした後に*Copy to clipboard*アイコンをクリックしてください。 + +ターミナルを開いて以下のgitコマンドを実行してください： + +``` +git clone "コピーしたURL" +``` +"コピーしたURL" (ダブルクオーテーションは除いてください) は先ほどコピーしたレポジトリのURLと置き換えてください。 + +copy URL to clipboard + +例： +``` +git clone https://github.com/＜あなたのユーザー名＞/first-contributions.git +``` +`あなたのユーザー名` はご自身のGitHubユーザー名に置き換えてください。この作業でGitHub のレポジトリの内容はあなたのコンピュータにコピーされました。 + +## ブランチを作成 + +もしレポジトリのディレクトリにいなければそこまで移動してください。 + +``` +cd first-contributions +``` +`git checkout` コマンドを使用してブランチを作成します： +``` +git checkout -b +``` + +例: +``` +git checkout -b add-alonzo-church +``` +(ブランチの名前には必ずしも*add*が含まれていなければならないわけではありませんが、このブランチの目的があなたの名前をリストに加えることであることを考慮すれば含むのが適切です。) + +## コードを変更してその変更をコミット + +テキストエディタで`Contributors.md`ファイルを開いてあなたの名前を追加してください。ただし、ファイルの始めや終わりにあなたの名前をつけないようにしましょう。名前リストの間のどこか好きな場所に、あなたの名前を追加するようにしましょう。あなたの名前をファイルに加えたら、ファイルを保存します。 + +git status + +プロジェクトディレクトリに移動して`git status`を実行すると、変更がなされたことが確認できると思います。`git add`コマンドを使ってそれらの変更を適用してください。 +``` +git add Contributors.md +``` + +次に`git commit`コマンドを使ってこれらの変更をコミットします。 +``` +git commit -m "Add <あなたの名前> to Contributors list" +``` +`<あなたの名前>`をご自身の名前に置き換えてください。 + +## GitHubに変更をpushする + +`git push`コマンドを使って変更をpushしてください。 +``` +git push origin <ブランチ名> +``` +`<ブランチ名>`には先ほど作成したブランチ名を入れてください。 + +## レビューのためにプルリクエストを送る + +GitHub上であなたのリポジトリに行くと、`Compare & pull request`ボタンが表示されます。そのボタンをクリックしてください。 + +create a pull request + +プルリクエストを作ってください： + +submit pull request + +すぐに私が加えられた変更をmasterブランチにマージします。マージが終了した際にはその旨のメールが送られます。 + +## 次に何をするべきか + +おめでとうございます！ コントリビューターとして重要な _フォーク -> クローン -> 編集 -> プルリクエスト_　の基本的なワークフローが完了しました。 + +初のオープンソースへの貢献を祝って友達やフォロワーにそのことを[このウェブアプリ](https://roshanjossey.github.io/first-contributions/#social-share)を使ってシェアしましょう。 + +もし何かしら質問があるようでしたら[私たちのSlack team](https://firstcontributors.slack.com/join/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY)に入ってください。 + +他のプロジェクトへの貢献を始めましょう。簡単なイシューが立てられているプロジェクトのリストを作りました。ウェブアプリで[プロジェクトリスト](https://roshanjossey.github.io/first-contributions/#project-list)を確認て見てください。 + +### [追加リソース](../additional-material/git_workflow_scenarios/additional-material.md) + +## その他のツールを使用したチュートリアル +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + diff --git a/translations/README.ka.md b/translations/README.ka.md new file mode 100644 index 00000000000..0c15653eda5 --- /dev/null +++ b/translations/README.ka.md @@ -0,0 +1,89 @@ +[![Open Source Love](https://firstcontributions.github.io/open-source-badges/badges/open-source-v1/open-source.svg)](https://github.com/firstcontributions/open-source-badges) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# ಮೊದಲ ಕೊಡುಗೆಗಳು + +ಈ ಯೋಜನೆಯು ಆರಂಭಿಕರು ತಮ್ಮ ಮೊದಲ ಕೊಡುಗೆಯನ್ನು ನೀಡುವ ವಿಧಾನವನ್ನು ಸರಳಗೊಳಿಸುವ ಮತ್ತು ಮಾರ್ಗದರ್ಶನ ಮಾಡುವ ಗುರಿಯನ್ನು ಹೊಂದಿದೆ. ನಿಮ್ಮ ಮೊದಲ ಕೊಡುಗೆಯನ್ನು ನೀಡಲು ನೀವು ಬಯಸಿದರೆ, ಕೆಳಗಿನ ಹಂತಗಳನ್ನು ಅನುಸರಿಸಿ. + +_ನೀವು ಆಜ್ಞಾ ಸಾಲಿನೊಂದಿಗೆ ಆರಾಮದಾಯಕವಲ್ಲದಿದ್ದರೆ,[GUI ಉಪಕರಣಗಳನ್ನು ಬಳಸುವ ಟ್ಯುಟೋರಿಯಲ್‌ಗಳು ಇಲ್ಲಿವೆ.](#tutorials-using-other-tools)_ + +fork this repository + +ನಿಮ್ಮ ಯಂತ್ರದಲ್ಲಿ ನೀವು ಜಿಟ್ ಹೊಂದಿಲ್ಲದಿದ್ದರೆ,[ಅದನ್ನು ಸ್ಥಾಪಿಸಿ](https://help.github.com/articles/set-up-git/) + +## ಈ ರೀಪಾಜ಼ಟೊರೀ ಫೋರ್ಕ್ ಮಾಡಿ + +ಈ ಪುಟದ ಮೇಲ್ಭಾಗದಲ್ಲಿರುವ ಫೋರ್ಕ್ ಬಟನ್ ಅನ್ನು ಕ್ಲಿಕ್ ಮಾಡುವ ಮೂಲಕ ಈ ರೆಪೊಸಿಟರಿಯನ್ನು ಫೋರ್ಕ್ ಮಾಡಿ. +ಇದು ನಿಮ್ಮ ಖಾತೆಯಲ್ಲಿ ಈ ರೆಪೊಸಿಟರಿಯ ನಕಲನ್ನು ರಚಿಸುತ್ತದೆ. + +## ರೆಪೊಸಿಟರಿ ಕ್ಲೋನ್ + +clone this repository + +ಈಗ ನಿಮ್ಮ ಯಂತ್ರಕ್ಕೆ ಫೋರ್ಕ್ಡ್ ರೆಪೊಸಿಟರಿಯನ್ನು ಕ್ಲೋನ್ ಮಾಡಿ. ನಿಮ್ಮ GitHub ಖಾತೆಗೆ ಹೋಗಿ, ಫೋರ್ಕ್ ಮಾಡಿದ ರೆಪೊಸಿಟರಿಯನ್ನು ತೆರೆಯಿರಿ, ಕೋಡ್ ಬಟನ್ ಅನ್ನು ಕ್ಲಿಕ್ ಮಾಡಿ ಮತ್ತು ನಂತರ _copy to clipboard_ ಐಕಾನ್ ಅನ್ನು ಕ್ಲಿಕ್ ಮಾಡಿ. + +ಟರ್ಮಿನಲ್ ತೆರೆಯಿರಿ ಮತ್ತು ಕೆಳಗಿನ git ಆಜ್ಞೆಯನ್ನು ಚಲಾಯಿಸಿ: + +``` +git clone "url ನೀವು ಇದೀಗ ನಕಲಿಸಿದ್ದೀರಿ" +``` +ಎಲ್ಲಿ "url ನೀವು ಇದೀಗ ನಕಲಿಸಿದ್ದೀರಿ" (ಉದ್ಧರಣ ಚಿಹ್ನೆಗಳಿಲ್ಲದೆ) ಈ ಭಂಡಾರಕ್ಕೆ url ಆಗಿದೆ (ಈ ಯೋಜನೆಯ ನಿಮ್ಮ ಫೋರ್ಕ್). Url ಪಡೆಯಲು ಹಿಂದಿನ ಹಂತಗಳನ್ನು ನೋಡಿ. + +copy URL to clipboard + +ಉದಾಹರಣೆಗೆ: +``` +git clone https://github.com/this-is-you/first-contributions.git +``` +ಅಲ್ಲಿ `ಇದು-ನೀವು 'ನಿಮ್ಮ ಗಿಟ್‌ಹಬ್ ಬಳಕೆದಾರಹೆಸರು. ಇಲ್ಲಿ ನೀವು ನಿಮ್ಮ ಕಂಪ್ಯೂಟರ್‌ಗೆ ಗಿಟ್‌ಹಬ್‌ನಲ್ಲಿನ ಮೊದಲ ಕೊಡುಗೆಗಳ ಭಂಡಾರದ ವಿಷಯಗಳನ್ನು ನಕಲಿಸುತ್ತಿದ್ದೀರಿ. +## ಒಂದು ಶಾಖೆಯನ್ನು ರಚಿಸಿ +ನಿಮ್ಮ ಕಂಪ್ಯೂಟರ್‌ನಲ್ಲಿ ರೆಪೊಸಿಟರಿ ಡೈರೆಕ್ಟರಿಗೆ ಬದಲಾಯಿಸಿ (ನೀವು ಈಗಾಗಲೇ ಇಲ್ಲದಿದ್ದರೆ): +``` +cd first-contributions +``` +ಈಗ `git checkout` ಆಜ್ಞೆಯನ್ನು ಬಳಸಿಕೊಂಡು ಒಂದು ಶಾಖೆಯನ್ನು ರಚಿಸಿ: +``` +git checkout -b <ನಿಮ್ಮ ಹೊಸ-ಶಾಖೆ-ಹೆಸರನ್ನು ಸೇರಿಸಿ> +``` +ಉದಾಹರಣೆಗೆ: +``` +git checkout -b add-alonzo-church +``` +(ಶಾಖೆಯ ಹೆಸರಿನಲ್ಲಿ `add` ಎಂಬ ಪದವನ್ನು ಹೊಂದುವ ಅಗತ್ಯವಿಲ್ಲ, ಆದರೆ ಇದನ್ನು ಸೇರಿಸುವುದು ಸಮಂಜಸವಾದ ವಿಷಯ ಏಕೆಂದರೆ ಈ ಶಾಖೆಯ ಉದ್ದೇಶವು ನಿಮ್ಮ ಹೆಸರನ್ನು ಪಟ್ಟಿಗೆ ಸೇರಿಸುವುದು.) +## ಅಗತ್ಯ ಬದಲಾವಣೆಗಳನ್ನು ಮಾಡಿ ಮತ್ತು ಆ ಬದಲಾವಣೆಗಳನ್ನು ಮಾಡಿ +ಈಗ ಪಠ್ಯ ಸಂಪಾದಕದಲ್ಲಿ `Contributor.md` ಫೈಲ್ ಅನ್ನು ತೆರೆಯಿರಿ, ಅದಕ್ಕೆ ನಿಮ್ಮ ಹೆಸರನ್ನು ಸೇರಿಸಿ. ಅದನ್ನು ಫೈಲ್‌ನ ಪ್ರಾರಂಭ ಅಥವಾ ಕೊನೆಯಲ್ಲಿ ಸೇರಿಸಬೇಡಿ. ನಡುವೆ ಎಲ್ಲಿಯಾದರೂ ಇರಿಸಿ. ಈಗ, ಫೈಲ್ ಅನ್ನು ಉಳಿಸಿ. +git status +ನೀವು ಪ್ರಾಜೆಕ್ಟ್ ಡೈರೆಕ್ಟರಿಗೆ ಹೋಗಿ `git status` ಆಜ್ಞೆಯನ್ನು ಕಾರ್ಯಗತಗೊಳಿಸಿದರೆ, ಬದಲಾವಣೆಗಳಿವೆ ಎಂದು ನೀವು ನೋಡುತ್ತೀರಿ. +Add those changes to the branch you just created using the `git add` command: +``` +git add Contributors.md +``` +ಈಗ `git commit` ಆಜ್ಞೆಯನ್ನು ಬಳಸಿಕೊಂಡು ಆ ಬದಲಾವಣೆಗಳನ್ನು ಮಾಡಿ: +``` +git commit -m "ಕೊಡುಗೆದಾರರ ಪಟ್ಟಿಗೆ <ನಿಮ್ಮ- ಹೆಸರು> ಸೇರಿಸಿ" +``` +ನಿಮ್ಮ ಹೆಸರಿನೊಂದಿಗೆ `<ನಿಮ್ಮ- ಹೆಸರು>` ಅನ್ನು ಬದಲಾಯಿಸುತ್ತದೆ. +## ಬದಲಾವಣೆಗಳನ್ನು ಗಿಟ್‌ಹಬ್‌ಗೆ ಪುಶ್ ಮಾಡಿ +`Git push` ಆಜ್ಞೆಯನ್ನು ಬಳಸಿಕೊಂಡು ನಿಮ್ಮ ಬದಲಾವಣೆಗಳನ್ನು ಒತ್ತಿರಿ: +``` +git push origin <ನಿಮ್ಮ ಶಾಖೆಯ ಹೆಸರನ್ನು ಸೇರಿಸಿ> +``` +`` ಅನ್ನು ನೀವು ಮೊದಲು ರಚಿಸಿದ ಶಾಖೆಯ ಹೆಸರಿನೊಂದಿಗೆ ಬದಲಾಯಿಸುತ್ತದೆ. +## ನಿಮ್ಮ ಬದಲಾವಣೆಗಳನ್ನು ವಿಮರ್ಶೆಗಾಗಿ ಸಲ್ಲಿಸಿ +ನೀವು ಗಿಟ್‌ಹಬ್‌ನಲ್ಲಿರುವ ನಿಮ್ಮ ಭಂಡಾರಕ್ಕೆ ಹೋದರೆ, ನೀವು `Compare & pull request` ಬಟನ್ ನೋಡುತ್ತೀರಿ. ಆ ಗುಂಡಿಯನ್ನು ಕ್ಲಿಕ್ ಮಾಡಿ. +create a pull request +ಈಗ ಪುಲ್ ವಿನಂತಿಯನ್ನು ಸಲ್ಲಿಸಿ. +submit pull request +ಶೀಘ್ರದಲ್ಲೇ ನಾನು ನಿಮ್ಮ ಎಲ್ಲಾ ಬದಲಾವಣೆಗಳನ್ನು ಈ ಯೋಜನೆಯ ಮಾಸ್ಟರ್ ಶಾಖೆಯಲ್ಲಿ ವಿಲೀನಗೊಳಿಸುತ್ತೇನೆ. ಬದಲಾವಣೆಗಳನ್ನು ವಿಲೀನಗೊಳಿಸಿದ ನಂತರ ನೀವು ಅಧಿಸೂಚನೆ ಇಮೇಲ್ ಅನ್ನು ಪಡೆಯುತ್ತೀರಿ. +## ಇಂದಿನಿಂದ ಏನು? +ಅಭಿನಂದನೆಗಳು! ನೀವು ಕೊಡುಗೆದಾರರಾಗಿ ಆಗಾಗ್ಗೆ ಎದುರಾಗುವ ಪ್ರಮಾಣಿತ _fork -> clone -> edit -> PR_ ವರ್ಕ್‌ಫ್ಲೋ ಅನ್ನು ನೀವು ಇದೀಗ ಪೂರ್ಣಗೊಳಿಸಿದ್ದೀರಿ! +ನಿಮ್ಮ ಕೊಡುಗೆಯನ್ನು ಆಚರಿಸಿ ಮತ್ತು ಅದನ್ನು ನಿಮ್ಮ ಸ್ನೇಹಿತರು ಮತ್ತು ಅನುಯಾಯಿಗಳೊಂದಿಗೆ ಹಂಚಿಕೊಳ್ಳಿ [ವೆಬ್ ಅಪ್ಲಿಕೇಶನ್](https://firstcontributions.github.io/#social-share). +ನಿಮಗೆ ಯಾವುದೇ ಸಹಾಯ ಬೇಕಾದರೆ ಅಥವಾ ಯಾವುದೇ ಪ್ರಶ್ನೆಗಳಿದ್ದಲ್ಲಿ ನೀವು ನಮ್ಮ slack team ಸೇರಬಹುದು. [Slack team ಸೇರಿ](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). +ಈಗ ನೀವು ಹೆಚ್ಚಿನ ಯೋಜನೆಗಳಿಗೆ ಕೊಡುಗೆ ನೀಡಲು ಪ್ರಾರಂಭಿಸಬಹುದು. ನಾವು ನಿಮಗಾಗಿ ಒಂದು ಪಟ್ಟಿಯನ್ನು ತಯಾರಿಸಿದ್ದೇವೆ ಅದು ಬಹಳ ಸುಲಭವಾದ ಸಮಸ್ಯೆಗಳು. [ಯೋಜನೆಗಳ ಪಟ್ಟಿ](https://roshanjossey.github.io/first-contributions/#project-list) +## ಇತರ ಪರಿಕರಗಳನ್ನು ಬಳಸುವ ಟ್ಯುಟೋರಿಯಲ್ +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.ko.md b/translations/README.ko.md new file mode 100644 index 00000000000..61d66785e39 --- /dev/null +++ b/translations/README.ko.md @@ -0,0 +1,134 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# 첫 기여 + + +어렵습니다. 무엇을 하든 누구나 처음에는 어렵게 느껴집니다. 특히 협업을 할 때 실수를 하기라도 하면 마음이 편치 않습니다. 그래서 저희는 새로운 오픈소스 기여자들이 첫 기여를 하고 그것을 익히는 과정을 단순화하고자 했습니다. + +관련된 글을 읽거나 튜토리얼을 보는 것도 물론 도움이 되지만, 연습공간에서 직접 해보는 것보다 나은게 있을까요? 이 프로젝트의 목표는 초보자도 첫 오픈소스 기여를 할 수 있도록 단순한 방식으로 안내하는 것입니다. 첫 기여를 하고 싶으시다면 아래의 설명을 따라주세요. + +이 저장소 포크하기 + +가장 먼저, Git이 없으시다면 [설치](https://help.github.com/articles/set-up-git/)해주세요. + +## 저장소 포크하기 + +이 페이지의 상단에 있는 Fork 버튼을 클릭하여 이 저장소를 포크하세요. 그러면 본인의 깃헙 계정에 이 저장소의 복제본이 생성될 겁니다. + +## 저장소 클론하기 + +이 저장소 복제하기 + +이제 이 저장소를 자신의 기기에 클론합니다. Clone or download 버튼을 클릭하고 클립보드로 복사 아이콘을 클릭합니다. + +터미널을 열고 다음 Git 명령을 실행합니다: + +``` +git clone "방금 복사한 URL" +``` + +위에 (따옴표를 제외한) "방금 복사한 URL"는 이 저장소의 URL입니다. URL은 이전 단계에서 찾을 수 있습니다. + +URL 을 클립보드로 복사 + +예시: + +``` +git clone https://github.com/this-is-you/first-contributions.git +``` + +예시의 `this-is-you`는 본인 깃헙 계정으로 바꾸어주세요. 이 명령어는 +깃헙의 first-contributions 저장소의 내용을 로컬 컴퓨터에 복사합니다. + +## 브랜치 생성하기 + +(아직 저장소 디렉토리가 아니라면) 아래의 명령어를 입력하여 좀전에 컴퓨터에 복사한 저장소 디렉토리로 이동합니다. + +``` +cd first-contributions +``` + +그리고 `git checkout` 명령어을 입력하여 브랜치를 생성합니다. + +``` +git checkout -b +``` + +예시: + +``` +git checkout -b add-alonzo-church +``` + +(브랜치의 이름에 꼭 *add*가 들어가지 않아도 됩니다. 하지만 이 브랜치의 목적은 당신의 이름을 리스트에 추가하는 것이기 때문에 이름에 *add*를 포함하는 것이 합리적입니다.) + +## 필요한 변경사항을 작성하고 커밋하기 + +이제 텍스트 편집기에서 `Contributors.md` 파일을 열고 본인의 이름을 아래와 같이 추가해주세요. 이때 맨 처음이나 맨 끝을 제외한 중간에 마음에 드는 곳에 추가하시면 됩니다. 그리고 파일을 저장하세요. + +git status + +프로젝트 디렉터리에서 `git status` 명령을 실행하면 변경사항을 볼 수 있습니다. + +변경사항을 아래 `git add` 명령어를 입력하여 추가합니다. + +``` +git add Contributors.md +``` + +이제 아래 `git commit` 명령어로 변경사항을 커밋합니다. + +``` +git commit -m "Add to Contributors list" +``` + +``을 본인 이름으로 바꾸세요. + +## 변경사항을 깃헙에 푸시하기 + +`git push` 명령어로 변경사항을 푸시합니다. + +``` +git push origin +``` + +위의 `` 부분을 좀전에 생성한 브랜치 이름으로 바꾸세요. + +## 검토를 위해 변경사항을 제출하기 + +이제 본인의 깃헙 저장소로 이동하면 `Compare & pull request` 버튼이 보일 것 입니다. 버튼을 클릭하세요. + +풀 요청 +생성하기 + +이제 풀 요청(Pull Request)을 제출합니다. + +풀 요청 제출하기 + +이제 여러분의 변경사항을 담당자가 확인한 후에 마스터 브랜치에 머지 하게 되면 알림 메일을 받으실겁니다. + +## 첫 기여, 그리고 그 후 + +축하합니다! 앞으로 기여자로써 자주 사용하게될 기본 워크플로우, _포크(fork) -> 클론(clone) -> 수정(edit) -> 풀 요청(pull request)_, 를 완수하셨습니다! + +첫 기여에 대한 소식을 친구들 및 팔로워에게 [웹 앱](https://roshanjossey.github.io/first-contributions/#social-share)을 통해 공유해보세요. + + +그리고 도움이 필요하거나 질문이 있다면 저희의 slack 에서 요청해보세요. → [slack 팀 가입하기](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) + +이제 다른 프로젝트에도 기여해보세요! 지금 바로 시작할 수 있는 난이도가 낮은 이슈들로 가득찬 목록이 있습니다. [웹앱의 프로젝트 목록](https://roshanjossey.github.io/first-contributions/#project-list)에서 확인해보세요. + + + +### [추가 정보](../additional-material/translations/Korean/additional-material.ko.md) + +## 다른 도구들에 관한 튜토리얼 + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| ------------------------------------------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ | +| [GitHub Desktop](../github-desktop-tutorial.md) | [Visual Studio 2017](../github-windows-vs2017-tutorial.md) | [GitKraken](../gitkraken-tutorial.md) | [Visual Studio Code](../github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../github-windows-intellij-tutorial.md) | diff --git a/translations/README.kws.md b/translations/README.kws.md new file mode 100644 index 00000000000..a4f885137a4 --- /dev/null +++ b/translations/README.kws.md @@ -0,0 +1,134 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + + +# Mchango wa Kwanza + + +Ni vigumu. Ni vigumu daima mara ya kwanza unafanya kitu. Hasa wakati unashirikiana, kufanya makosa sio jambo la kushangaza. Tulitaka kurahisisha njia mpya ya wafadhili wa kujifunza na kuchangia kwa mara ya kwanza. + +Kusoma makala na mafunzo ya kutazama yanaweza kusaidia, lakini ni nini bora zaidi kuliko kufanya mambo halisi katika mazingira ya mazoezi? Mradi huu unalenga kutoa mwongozo na kurahisisha wasanidi wa njia kufanya mchango wao wa kwanza. Ikiwa unatafuta kufanya mchango wako wa kwanza, fuata hatua zifuatazo. + +#### *Ikiwa huna urahisi na mstari wa amri, [hapa ni mafunzo kwa kutumia zana za GUI.](#Mafundisho-Kutumia-Zana-Zingine)* + + +fork this repository + + +## Futa hifadhi hii + +Futa repo hii kwa kubonyeza kifungo cha fakia juu ya ukurasa huu. Hii itaunda nakala ya hifadhi hii katika akaunti yako. + +## Weka chumba + +clone this repository + +Sasa fungia repo iliyofungwa kwa mashine yako. Nenda kwenye akaunti yako ya GitHub, kufungua repo iliyofungwa, bonyeza kitufe cha kamba na kisha bofya nakala kwenye clipboard. + + +Fungua terminal na uendesha amri yafuatayo: + +``` +git clone "url you just copied" +``` + +ambapo "url ulikosa tu" (bila alama za kupiga kura) ni url kwenye hifadhi hii (fomu yako ya mradi huu). Angalia hatua za awali ili kupata url. + +copy URL to clipboard + +Kwa mfano: + +``` +git clone https://github.com/this-is-you/first-contributions.git +``` + +wapi `this-is-you` jina lako la mtumiaji GitHub. Hapa unakili nakala ya maudhui ya kwanza ya michango kwenye GitHub kwenye kompyuta yako. + +## Unda tawi + +Badilisha kwenye saraka ya uhifadhi kwenye kompyuta yako (ikiwa huko tayari): + +``` +cd first-contributions +``` + +Sasa uunda tawi kwa kutumia git `checkout` amri: + + +``` +git checkout -b +``` + +Kwa mfano: + +``` +git checkout -b add-alonzo-church +``` + +(Jina la tawi haina haja ya kuwa neno liongeze ndani yake, lakini ni jambo la kuzingatia kwa sababu lengo la tawi hili ni kuongeza jina lako kwenye orodha.) + +## Fanya mabadiliko muhimu na ufanyie mabadiliko hayo + +Sasa fungua `Contributors.md` faili katika mhariri wa maandishi, uongeze jina lako. Usiongeze kwenye mwanzo au mwisho wa faili. Weka mahali popote katikati. Sasa, sahau faili. + +git status + +Ikiwa unakwenda kwenye saraka ya mradi na kutekeleza amri `git status`, utaona kuna mabadiliko. + + +Ongeza mabadiliko hayo kwenye tawi ulilojenga kwa kutumia `git add` amri: + +``` +git add Contributors.md +``` + +Sasa fanya mabadiliko hayo kwa kutumia amri `git commit`: + +``` +git push origin +``` + +kubadilisha `` jina lako. + +## Skuma mabadiliko kwenye GitHub + +Skuma mabadiliko yako kwa kutumia amri `git push`: + +``` +git push origin +``` + +kubadilisha `` na jina la tawi uliloumba hapo awali. + +## Tuma mabadiliko yako kwa ukaguzi + +Ikiwa unaenda kwenye hifadhi yako kwenye GitHub, utaona `Compare & pull request` kifungo. Bofya kwenye kifungo hicho. + +create a pull request + +Sasa weka ombi la kuvuta. + +submit pull request + +Hivi karibuni nitakuwa kuunganisha mabadiliko yako yote kwenye tawi la mradi huu. Utapata barua pepe ya arifa mara mabadiliko yameunganishwa. + +## Wapi kutoka hapa? + +Hongera! Wewe umekamilisha fomu ya kawaida *fork -> clone -> hariri -> pull request* ambayo unakutana mara nyingi kama mchangiaji! + +Sherehe mchango wako na uwashiriki na marafiki zako na wafuasi kwa kwenda kwenye [programu ya wavuti](https://roshanjossey.github.io/first-contributions/#social-share). + +Unaweza kujiunga na timu yetu ya slack ikiwa unahitaji msaada wowote au una maswali yoyote. [Jiunge na timu ya slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Sasa hebu tuanze uanze na kuchangia kwenye miradi mingine. Tumeandika orodha ya miradi na masuala rahisi unaweza kuanza. Angalia [orodha ya miradi katika programu ya wavuti](https://roshanjossey.github.io/first-contributions/#project-list). + +### [Nyenzo za ziada](../additional-material/git_workflow_scenarios/additional-material.md) + +## Mafundisho Kutumia Zana Zingine + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.kz.md b/translations/README.kz.md new file mode 100644 index 00000000000..0a55e58d155 --- /dev/null +++ b/translations/README.kz.md @@ -0,0 +1,109 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Жобаға алғашқы үлес қосу + +Бұл қиын. Бірдеңе істегенде бірінші кезекте әрқашан қиын. Қателіктер жасау өте жағымсыз, әсіресе топтық жұмыс істесеңіз. Барлық open source проекттер ынтымақтастық пен бірегей жұмыстан тұрады. Біз бастаушы әзірлеушілер үшін оқыту мен бірлесіп жұмыс істеудегі алғашқы қадамдарды жеңілдеткіміз келеді. + +Оқулықтарды және мақалаларды оқуға әрқашан болады, бірақ іс жүзінде тәжірибе ортасында жұмыс жасаудан гөрі не жақсы? Бұл жобаның мақсаты - жастарды дұрыс жолға қою, сондай-ақ оларға алғашқы үлес қосуға мүмкіндік беру. Егер сіз өзіңіздің алғашқы үлесіңізді жасау мүмкіндігін іздесеңіз, төмендегі қарапайым қадамдарды орындаңыз. Біз уәде етеміз, бұл қызықты болады. + +fork this repository + + +Егерде сіздің компьютеріңізде git қосылмаған болса, [ оны қосыңыз ]( https://help.github.com/articles/set-up-git/ ) + +## Тармақты (fork) жасаңыз + +Өзіңіздің тармағыңызды жасау үшін, беттің үстіңгі жағындағы `fork` түймесін басыңыз. Осылай сіз осы репозиторийдің өзіңіздің аккаутыңызда копиясын жасайсыз. + +## Репозиторийді клондаңыз + +clone this repository + +Енді бұл репозиторийді өз дербес компьютеріңізге клодаңыз. Сілтемені көшіру үшін `clone` батырмасын басыңыз, содан кейін `copy to clipboard` белгішесіне басыңыз. + +Терминалды ашып, келесі git пәрмендіні іске қосыңыз: + +``` +git clone "url you just copied" +``` +Бұл жерде "url you just copied" (тырнақшасыз) сіздің репозиторийңізге сілтеме. Бұл сілтемені алу үшін алдыңғы қадамдарды қараңыз. + +copy URL to clipboard + +Мысалы: +``` +git clone https://github.com/this-is-you/first-contributions.git +``` +Бұл жерде `this-is-you` сіздің github-тағы логин. Осылайша GitHub-тан сіздің компьютеріңізге 'first-contributions' репозиторийін көшіресіз. + +## Тармақ жасаңыз + +Егер сіз әлі сол жерде жоқ болсаңыз, компьютердегі репозиторий каталогына өтіңіз. + +``` +cd first-contributions +``` +Енді `git checkout` команданың көмегімен тармақты құрыңыз. + +``` +git checkout -b +``` + +Мысалы: +``` +git checkout -b add-alonzo-church +``` +(Синтаксистік түрде тармақта *add* сөзі болуы қажет емес, бірақ ол осы тармақтың мақсатына баса назар аударғандықтан негізделеді - атыңызды тізімге қосу.) + +## Керек өзгерістерді жасаңыз да, коммит істеңіз + +Енді мәтіндік редакторда `Contributors.md` файлын ашыңыз, атыңызды енгізіңіз және файлды сақтаңыз. Егер сіз жобалық каталогқа барып, `git status` орындасаңыз, өзгертулерді көресіз. Бұл өзгертулерді `git add` командасымен қосыңыз. + +``` +git add Contributors.md +``` + +Енді бұл өзгерістерды `git commit` командасымен коммиттаңыз. + +``` +git commit -m "Add to Contributors list" +``` +`` өзіңіздің атыңызға ауыстырыңыз + +## Өзгерістерді github'қа пуштаңыз + +Өзгерістерді `git push` командасымен пуштаңыз +``` +git push origin +``` +`` дегенді бұрын құрылған тармақ атына өзгертіңіз. + +## Өзгерістерді ревью үшін растаңыз + +Егер сіз GitHub-тағы репозиторийге кірсеңіз, `Compare & pull request` батырмасын көресіз. Оны басыңыз. + +create a pull request + +Енді пулл-реквестті растаңыз. + +submit pull request + +Көп ұзамай мен осы жобаның негізгі бөлімімен барлық өзгерістерді біріктіремін. Өзгерістер қабылданған кезде (мердж жасалғанда) электрондық хат аласыз. + +## Ары қарай не? + +Төменде сіз жаңадан келген тапсырмаларды таба алатын бірнеше танымал репозиторийлер бар. Қосымша ақпарат алу үшін репозиторийге барыңыз. + +| [![exercism](https://avatars2.githubusercontent.com/u/5624255?v=3&s=100)](https://github.com/exercism/exercism.io/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+patch%22) | [![fun-retro](https://avatars3.githubusercontent.com/u/15913975?v=3&s=100)](https://github.com/funretro/distributed/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly) | [](https://github.com/facebook/react/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+bug%22) | [![habitat](https://avatars1.githubusercontent.com/u/18171698?v=3&s=100)](https://github.com/habitat-sh/habitat/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [![scikit-learn](https://avatars0.githubusercontent.com/u/365630?v=3&s=100)](https://github.com/scikit-learn/scikit-learn/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [](https://github.com/technomancy/leiningen/issues?q=is%3Aopen+is%3Aissue+label%3ANewbie) | [](https://github.com/numpy/numpy/issues?q=is%3Aopen+is%3Aissue+label%3A%22Easy+Fix%22) | [![elasticsearch](https://avatars2.githubusercontent.com/u/6764390?v=3&s=100)](https://github.com/elastic/elasticsearch/issues?q=is%3Aopen+is%3Aissue+label%3A%22low+hanging+fruit%22) | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [exercism](https://github.com/exercism/exercism.io/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+patch%22) | [Fun Retros](https://github.com/funretro/distributed/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly) | [react](https://github.com/facebook/react/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+bug%22) | [habitat](https://github.com/habitat-sh/habitat/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [scikit-learn](https://github.com/scikit-learn/scikit-learn/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [Leiningen](https://github.com/technomancy/leiningen/issues?q=is%3Aopen+is%3Aissue+label%3ANewbie) | [numpy](https://github.com/numpy/numpy/issues?q=is%3Aopen+is%3Aissue+label%3A%22Easy+Fix%22) | [elasticsearch](https://github.com/elastic/elasticsearch/issues?q=is%3Aopen+is%3Aissue+label%3A%22low+hanging+fruit%22) | +| [![homebrew](https://avatars2.githubusercontent.com/u/1503512?v=3&s=100)](https://github.com/Homebrew/brew/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) | [![rust](https://avatars1.githubusercontent.com/u/5430905?v=3&s=100)](https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Aissue+label%3AE-easy) | [![vuejs](https://avatars1.githubusercontent.com/u/6128107?v=3&s=100)](https://github.com/vuejs/vue/issues?q=is%3Aopen+is%3Aissue+label%3A%22contribution+welcome%22) | [![Suave](https://avatars2.githubusercontent.com/u/5822862?v=3&s=100)](https://github.com/SuaveIO/suave/issues?q=is%3Aopen+is%3Aissue+label%3Ahardness-easy) | [![OpenRA](https://avatars3.githubusercontent.com/u/409046?v=3&s=100)](https://github.com/OpenRA/OpenRA/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [![PowerShell](https://avatars0.githubusercontent.com/u/11524380?v=3&s=100)](https://github.com/powershell/powershell/issues?q=is%3Aopen+is%3Aissue+label%3AUp-for-Grabs) | [![coala](https://avatars2.githubusercontent.com/u/10620750?v=3&s=100)](https://github.com/coala/coala/issues?q=is%3Aopen+is%3Aissue+label%3Adifficulty%2Flow+label%3Adifficulty%2Fnewcomer) | [![moment](https://avatars2.githubusercontent.com/u/4129662?v=3&s=100)](https://github.com/moment/moment/issues?q=is%3Aopen+is%3Aissue+label%3AUp-For-Grabs) | +| [homebrew](https://github.com/Homebrew/brew/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) | [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Aissue+label%3AE-easy) | [vuejs](https://github.com/vuejs/vue/issues?q=is%3Aopen+is%3Aissue+label%3A%22contribution+welcome%22) | [Suave](https://github.com/SuaveIO/suave/issues?q=is%3Aopen+is%3Aissue+label%3Ahardness-easy) | [OpenRA](https://github.com/OpenRA/OpenRA/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [PowerShell](https://github.com/powershell/powershell/issues?q=is%3Aopen+is%3Aissue+label%3AUp-for-Grabs) | [coala](https://github.com/coala/coala/issues?q=is%3Aopen+is%3Aissue+label%3Adifficulty%2Flow+label%3Adifficulty%2Fnewcomer) | [moment](https://github.com/moment/moment/issues?q=is%3Aopen+is%3Aissue+label%3AUp-For-Grabs) | +| [![ava](https://avatars0.githubusercontent.com/u/8527916?v=3&s=100)](https://github.com/avajs/ava/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+for+beginner%22) | [![freeCodeCamp](https://avatars0.githubusercontent.com/u/9892522?v=3&s=100)](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only) | [![webpack](https://avatars3.githubusercontent.com/u/2105791?v=3&s=100)](https://github.com/webpack/webpack/issues?q=is%3Aopen+is%3Aissue+label%3A%22D1%3A+Easy+%28Contrib.+Difficulty%29%22) | [![hoodie](https://avatars1.githubusercontent.com/u/1888826?v=3&s=100)](https://github.com/hoodiehq/hoodie/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only) | [![pouchdb](https://avatars3.githubusercontent.com/u/3406112?v=3&s=100)](https://github.com/pouchdb/pouchdb/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) | [![neovim](https://avatars0.githubusercontent.com/u/6471485?v=3&s=100)](https://github.com/neovim/neovim/issues?q=is%3Aopen+is%3Aissue+label%3Aentry-level) | [![babel](https://avatars2.githubusercontent.com/u/9637642?v=3&s=100)](https://github.com/babel/babel/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly) | [](https://github.com/adobe/brackets/labels/Starter%20bug) | +| [ava](https://github.com/avajs/ava/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+for+beginner%22) | [freeCodeCamp](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only) | [webpack](https://github.com/webpack/webpack/issues?q=is%3Aopen+is%3Aissue+label%3A%22D1%3A+Easy+%28Contrib.+Difficulty%29%22) | [hoodie](https://github.com/hoodiehq/hoodie/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only) | [pouchdb](https://github.com/pouchdb/pouchdb/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) | [neovim](https://github.com/neovim/neovim/issues?q=is%3Aopen+is%3Aissue+label%3Aentry-level) | [babel](https://github.com/babel/babel/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly) | [brackets](https://github.com/adobe/brackets/labels/Starter%20bug) | +| [![Node.js](https://avatars1.githubusercontent.com/u/9950313?v=3&s=100)](https://github.com/nodejs/node/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22) | [](https://github.com/Semantic-Org/Semantic-UI-React/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22) | +| [Node.js](https://github.com/nodejs/node/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22) | [Semantic-UI-React](https://github.com/Semantic-Org/Semantic-UI-React/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22) | + diff --git a/translations/README.la.md b/translations/README.la.md new file mode 100644 index 00000000000..00d297c8042 --- /dev/null +++ b/translations/README.la.md @@ -0,0 +1,119 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# "Contribute" ຜົນງານໃນ GitHub ຮ່ວມກັບຄົນອື່ນເປັນຄັ້ງທຳອິດແມ່ນບໍ່? + +ມັນເປັນເລື່ອງທີ່ຂ້ອງຂ້າງຍາກໜ້ອຍໜຶ່ງ, ແຕ່ກ້າວທຳອິດໃນການເລີ່ມຕົ້ນເຮັດຫຍັງບາງຢ່າງມັນກໍ່ຈະຍາກແບບນີ້ສະເໝີ ໂດຍສະເພາະເວລາທີ່ຕ້ອງຮ່ວມງານກັບຄົນອື່ນ ເພາະເມື່ອເຮົາໄດ້ເຮັດຫຍັງຜິດພາດມັນກໍ່ມັກຈະເຮັດໃຫ້ເຮົາບໍ່ສະບາຍໃຈ, ແຕ່ວ່າໃນໂລກຂອງໂອເພັນຊອສ (open source) ຄືໂລກທີ່ເຮົາຕ້ອງໄດ້ເຮັດວຽກຮ່ວມກັນ! ເຮົາຈຶ່ງຢາກໃຫ້ຜູ້ທີ່ເຂົ້າມາໃໝ່ໄດ້ຮຽນຮູ້ວິທີການ "ຄອນທຣິບິ້ວ" ຜົນງານຮ່ວມກັບຄົນອື່ນໃນ GitHub ແບບງ່າຍໆ. + +ການອ່ານບົດຄວາມ ແລະ ການທີ່ໄດ້ທົດລອງເຮັດຕົວຢ່າງຕ່າງໆກໍ່ອາດຈະຊ່ວຍໄດ້, ແຕ່ເຖິງຢ່າງໃດກໍ່ຕາມ ຄົງຈະບໍ່ມີສິ່ງໃດເໜືອໄປກວ່າການທີ່ເຮົາໄດ້ລົງມືເຮັດດ້ວຍຕົນເອງ!. ໃນໂປຣເຈັກນີ້ຈະສອນໃຫ້ມືໃໝ່ຮູ້ຈັກການສົ່ງ "contribution" ທຳອິດໄດ້ຢ່າງງ່າຍໆ. + +ໃຫ້ຈື່ໄວ້ວ່າ: ຄວາມພະຍາຍາມຢູ່ທີ່ໃດ ຄວາມພະຍາຍາມກໍ່ຢູ່ທີ່ນັ້ນເຊັ່ນກັນ! + +ຖ້າພ້ອມແລ້ວເຮົາມາລອງສົ່ງ contibution ທຳອິດກັນໄດ້ພຽງບໍ່ເທົ່າໃດຂັ້ນຕອນດ້ານລຸ່ມໄປພ້ອມໆກັນເລີຍ, ບອກເລີຍວ່າງ່າຍກວ່າປອກກ້ວຍ. + +fork this repository + +ຫາກໃຜຍັງບໍ່ໄດ້ຕິດຕັ້ງ git ລົງໃນເຄື່ອງ, ທ່ານສາມາດກົດລິ້ງ[ຕິດຕັ້ງໄດ້ທີ່ນີ້]( https://help.github.com/articles/set-up-git/ ) + +## ກົດ "Fork" ໂປຣເຈັກນີ້ + +ໂປຣເຈັກຫຼັກນີ້ມັກຈະເອີ້ນວ່າ ໂປຣເຈັກຕົ້ນນ້ຳ, ທ່ານສາມາດ fork ໂປຣເຈັກຕົ້ນນ້ຳນີ້ໄປຍັງ repo ຂອງ account ຂອງທ່ານເອງໄດ້ໂດຍການກົດປຸ່ມ "Fork" ທີ່ດ້ານເທິງຂອງໜ້ານີ້. + +ແລ້ວໂປຣເຈັກນີ້ກໍ່ຈະຖືກຄັດລອກໄປທີ່ account ຂອງທ່ານ. + +## ກົດປຸ່ມ "Clone" ໂປຣເຈັກນີ້ + +clone this repository + +ມາຮອດຂັ້ນຕອນນີ້ເຮົາກໍ່ Clone ໂປຣເຈັກລົງມາທີ່ຄອມພິວເຕີຂອງເຮົາໂດຍການກົດທີ່ປຸ່ມ "Clone" ແລ້ວເລືອກ *Copy to clipboard* (ຄຳສັ່ງຄັດລອກ) + +ເປີດ terminal ຂຶ້ນມາ (ຕົວຢ່າງ Terminal ໃນ MacOS ຫຼື cmd ໃນ Windows) ແລ້ວພິມຄຳສັ່ງ git ຕໍ່ໄປນີ້: + +``` +git clone "url ທີ່ຄັດລອກໄວ້" +``` +"url ທີ່ຄັດລອກໄວ້" (ບໍ່ຕ້ອງໃສ່ " ") ຄື url ຂອງໂປຣເຈັກຂອງທ່ານ ທ່ານສາມາດກັບໄປເບິ່ງວິທີການຄັດລອກ url ໄດ້ຈາກຫົວຂໍ້ກ່ອນໜ້ານີ້ + +copy URL to clipboard + +ຕົວຢ່າງ: +``` +git clone https://github.com/this-is-you/first-contributions.git +``` +`this-is-you` ຄືຊື່ username ຂອງທ່ານຢູ່ເທິງ GitHub, ມາຮອດບ່ອນນີ້ທ່ານໄດ້ "Clone" ໂປຣເຈັກ first-contributions ໄປໄວ້ທີ່ຄອມພິວເຕີຂອງທ່ານແລ້ວ. + +## ສ້າງ branch + +ໃນ terminal ປ່ຽນ directory ໄປບ່ອນທີ່ທ່ານ Clone ໂປຣເຈັກໄວ້: + +``` +cd first-contributions +``` +ບ່ອນນີ້ໃຫ້ສ້າງ branch (ແຕກສາຂາອອກມາໃໝ່) ດ້ວຍຄຳສັ່ງ `git checkout`: +``` +git checkout -b <ຊື່ branch> +``` + +ຕົວຢ່າງ: +``` +git checkout -b add-phongphat-khamphiew +``` +(ປົກກະຕິຊື່ຂອງ branch ບໍ່ຈຳເປັນຕ້ອງມີຄຳວ່າ *add* ແຕ່ໃນໂປຣເຈັກນີ້ຢາກໃຫ້ໃຊ້ add-ຊື່-ຂອງ-ທ່ານ ເພາະຊື່ຂອງທ່ານຈະໄປສະແດງຢູ່ທີ່ລາຍການ Contributors (ຜູ້ເຂົ້າຮ່ວມ) ຂອງໂປຣເຈັກນີ້ + +## ເພີ່ມຫຼືແກ້ໄຂ code ໄດ້ເລີຍ, ແຕ່ຢ່າລືມ "Commit" ບອກວ່າທ່ານໄດ້ເຮັດຫຍັງລົງໄປແລ້ວແນ່ + +ຕອນນີ້ໃຫ້ເປີດໄຟລ໌ `Contributors.md` ໃນໂປຣແກຣມ text editor ເພີ່ມຊື່ຂອງທ່ານລົງໄປ ຈາກນັ້ນບັນທຶກໄຟລ໌ + +git status + +ໃນ terminal ຖ້າທ່ານຢູ່ທີ່ directory ຂອງໂປຣເຈັກ ໃຫ້ລອງພິມຄຳສັ່ງ `git status` ຈະເຫັນວ່າທ່ານໄດ້ປ່ຽນແປງໄຟລ໌ໃດແນ່ແລ້ວ. + +ເພີ່ມການປ່ຽນແປງນັ້ນໆເຂົ້າໄປ branch ທີ່ຫາກໍ່ສ້າງດ້ວຍຄຳສັ່ງ `git add`: +``` +git add Contributors.md +``` + +ຕອນນີ້ "Commit" ການປ່ຽນແປງດັ່ງກ່າວດ້ວຍຄຳສັ່ງ `git commit`: +``` +git commit -m "Add <ຊື່ຂອງທ່ານ> to Contributors list" +``` +ແທນບ່ອນ `<ຊື່ຂອງທ່ານ>` ດ້ວຍຊື່ແທ້ຂອງທ່ານ. + +## "Push" code ທີ່ປ່ຽນແປງຂຶ້ນ GitHub + +"Push" ຜົນງານທີ່ທ່ານໄດ້ເຮັດໃນຂັ້ນຕອນກ່ອນໜ້ານີ້ຂຶ້ນ GitHub ດ້ວຍຄຳສັ່ງ `git push`: +``` +git push origin <ຊື່ branch ຂອງທ່ານ> +``` +ແທນບ່ອນ `<ຊື່ branch ຂອງທ່ານ>` ດ້ວຍຊື່ຂອງ branch ທີ່ທ່ານໄດ້ສ້າງໄວ້ໃນຫົວຂໍ້ກ່ອນໜ້ານີ້ (add-ຊື່-ຂອງ-ທ່ານ) + +## ສົ່ງຜົນງານ ແລະ ລໍຖ້າຣີວິວຈາກເຈົ້າຂອງໂປຣເຈັກ + +ໄປທີ່ repository ຂອງທ່ານເທິງ GitHub ກົດທີ່ `Compare & pull request` + +create a pull request + +ຕອນນີ້ກໍ່ສົ່ງ Pull Request ໄປທີ່ໂປຣເຈັກຫຼັກ ຫຼື ໂປຣເຈັກຕົ້ນນ້ຳໄດ້ເລີຍ + +submit pull request + +ເຮົາຈະທຳການ "Merge" ຫຼື ລວມຜົນງານທີ່ທ່ານໄດ້ປ່ຽນແປງ code ມາທີ່ master branch ຂອງໂປຣເຈັກນີ້, ທ່ານຈະໄດ້ຮັບອີເມວເມື່ອເຮົາໄດ້ທຳການ Merge ຜົນງານຂອງທ່ານສຳເລັດແລ້ວ. + +## ຈະເຮັດຫຍັງຕໍ່ຫຼັງຈາກນີ້? +ຍິນດີນຳ, ທ່ານໄດ້ປະຕິບັດຂັ້ນຕອນຂອງການເຮັດ contribute ຄື fork -> clone -> edit -> pull request ເຊິ່ງຂັ້ນຕອນຕ່າງໆເຫຼົ່ານີ້ເປັນສິ່ງທີ່ທ່ານຕອງໄດ້ພົບເມື່ອທ່ານເປັນ contributor +ສະເຫຼີມສະຫຼອງໃຫ້ແກ່ການມີສ່ວນຮ່ວມຂອງທ່ານ, ຢ່າລືມແບ່ງປະສົບການທີ່ທ່ານໄດ້ຮັບໃຫ້ແກ່ໝູ່ເພື່ອນຂອງທ່ານ ໂດຍໄປທີ່ [ເວັບໄຊນີ້](https://roshanjossey.github.io/first-contributions/#social-share) + +ຫຼືຈະມີສ່ວນຮ່ວມກັບເຮົາຜ່ານ Slack ໃນກໍລະນີທີ່ທ່ານຕ້ອງການຄວາມຊ່ວຍເຫຼືອ ຫຼື ມີຂໍ້ສົງໄສໃດໆ [ເຂົ້າຮ່ວມ slack ກັບພວກເຮົາ](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) + +ຈາກນີ້ທ່ານສາມາດ contribute ໃຫ້ໂປຣເຈັກອື່ນໆໄດ້, ໂດຍທາງເຮົາໄດ້ເຮັດລາຍການໂປຣເຈັກທີ່ງ່າຍຕໍ່ການເລີ່ມຕົ້ນບາງສ່ວນໄວ້ໃຫ້ [ລາຍຊື່ໂປຣເຈັກທີ່ໜ້າສົນໃຈ](https://roshanjossey.github.io/first-contributions/#project-list) + +### [ຂໍ້ມູນອື່ນໆເພີ່ມເຕີມ](../additional-material/git_workflow_scenarios/additional-material.md) + +## ເຝິກການ contribute ໂດຍໃຊ້ເຄື່ອງມືອື່ນໆ + +|GitHub Desktop|Visual Studio 2017|GitKraken| +|---|---|---| +|[GitHub Desktop](../github-desktop-tutorial.md)|[Visual Studio 2017](../github-windows-vs2017-tutorial.md)|[GitKraken](../gitkraken-tutorial.md)| + diff --git a/translations/README.lt.md b/translations/README.lt.md new file mode 100644 index 00000000000..feebe2c3225 --- /dev/null +++ b/translations/README.lt.md @@ -0,0 +1,110 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Pirmieji įnašai + +Sunku. Visada sunku ką nors padaryti pirmą kartą. Ypač bendradarbiaujant, klaidų darymas nėra malonus dalykas. Tačiau atviras kodas - tai bendravimas ir bendradarbiavimas. Mes norime paprasčiau paaiškinti naujiesiems atvirojo kodo kūrėjams, kaip jie gali prisidėti pirmą kartą. + +Galite pradėti skaityti straipsnius ir žiūrėti vadovus, bet kas gali būti geriau nei mokymasis darant be klaidų pirmą kartą? Šio projekto tikslas - suteikti patarimus ir supaprastinti tai, kaip naujokai daro pirmąjį indėlį. Prisiminkite: kuo labiau esate atsipalaidavęs, tuo geriau mokotės. Jei norite atlikti pirmąjį indėlį, atlikite toliau pateiktus paprastus veiksmus. Mes pažadame, tai bus smagu. + +fork this repository + +Jei neturite instaliuoto git, [ instaliuokite čia ]( https://help.github.com/articles/set-up-git/). + +## Kopijuokite (fork) šią saugyklą + +Kopijuokite saugyklą paspausdami šaknies simbolio mygtuką šio puslapio viršuje. +Tai sukurs šios saugyklos kopiją jūsų GitHub paskyroje. + +## Klonuokite saugyklą + +clone this repository + +Dabar klonuokite šią saugyklą į savo kompiuterį. Spustelėkite klonavimo mygtuką ir tada spustelėkite *copy to clipboard* piktogramą. + +Atidarykite terminalą ir paleiskite šią git komandą: + +``` +git clone "kopijuota nuoroda" +``` +kur "kopijuota nuoroda" (be citatos ženklų) yra url nuoroda jūsų saugyklai. Peržiūrėkite ankstesnius veiksmus, kad gautumėte url nuorodą. + +copy URL to clipboard + +Pavyzdžiui: +``` +git clone https://github.com/tai-jus/first-contributions.git +``` +kur `tai-jus` yra jūsų GitHub paskyros vartotojo vardas. Čia jūs kopijuojate first-contributions saugyklos turinį į "GitHub" aplanką savo kompiuteryje. + +## Sukurkite šaką (branch) + +Pakeiskite kompiuterio saugyklos katalogą (jei dar to nepadarėte anksčiau): + +``` +cd first-contributions +``` +Dabar sukurkite šaką naudodami komandą `git checkout`: +``` +git checkout -b +``` + +Pavyzdžiui: +``` +git checkout -b add-vardenis-pavardenis +``` +(Saugyklos pavadinime neturi būti žodžio *add*, bet tai yra reikalinga, kadangi šios šakos (branch) paskirtis yra įtraukti savo vardą į sąrašą.) + +## Atlikite reikiamus pakeitimus ir pridėkite (commit) šiuos pakeitimus + +Dabar atidarykite failą `Contributors.md` teksto redaktoriuje, pridėkite prie jo savo vardą ir išsaugokite failą. Jei eisite į projekto katalogą ir paleisite komandą `git status`, pamatysite, kad yra pakeitimų. Pridėkite šiuos pakeitimus į ką tik sukurtą šaką (branch) komandos `git add` pagalba: +``` +git add Contributors.md +``` + +Dabar atlikite šiuos pakeitimus naudodami komandą `git commit`: +``` +git commit -m "Add to Contributors list" +``` +pakeisdami `` savo vardu. + +## Išsiųskite pakeitimus į GitHub + +Išsiųskite pakeitimus komanda `git push`: +``` +git push origin +``` +pakeisdami `` anskčiau sukurtos šakos (branch) vardu. + +## Pateikite pakeitimus peržiūrai + +Eikite į savo saugyklą GitHub. Pamatysite mygtuką `Compare & pull request` (palyginti ir įtraukti užklausą). Spustelėkite šį mygtuką. + +create a pull request + +Dabar pateikite įtraukimo į pradinę saugyklą (pull) užklausą. + +submit pull request + +Netrukus projekto autorius sujungs visus jūsų šakos pakeitimus su šio projekto pagrindine šaka. Kai pakeitimai bus sujungti, gausite tai patvirtinantį el. laišką. + +## Kas toliau? + +Džiaukitės ir atkreipkite dėmesį į savo įnašą pasidalindami šia žinia su draugais [interneto aplikacijoje](https://roshanjossey.github.io/first-contributions/#social-share). + +Prisijunkite prie mūsų "slack" komandos, jei jums reikia pagalbos ar turite klausimų. [Prisijungti prie slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Pradėkite tobulinti kitus projektus. Mes sukūrėme projektų sąrašą, kuriuose yra lengvai išsprendžiamų problemų. Peržiūrėkite [projektų sąrašą interneto aplikacijoje](https://roshanjossey.github.io/first-contributions/#project-list). + +### [ Papildoma medžiaga ](../additional-material/git_workflow_scenarios/additional-material.md) + + +## Pamokos naudojant kitus įrankius + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + diff --git a/translations/README.lv.md b/translations/README.lv.md new file mode 100644 index 00000000000..9402a2b9b17 --- /dev/null +++ b/translations/README.lv.md @@ -0,0 +1,123 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Pirmais devums + +Kaut ko paveikt pirmo reizi vienmēr ir grūti. Turklāt pieļaut kļūdas, jo īpaši līdzdarbojoties ar citiem, nav patīkami. Mēs vēlamies vienkāršot veidu, kā jauni atvērtā koda līdzautori mācās un pievieno savu devumu pirmo reizi. + +Rakstu lasīšana un pamācību skatīšanās var palīdzēt, tomēr nekas nav labāks par īstu darbību mācību vidē. Šī projekta mērķis ir sniegt norādījumus un vienkāršot veidu, kā iesācēji pievieno savu pirmo devumu. Ja tu vēlies līdzdarboties, seko turpmāk norādītajiem soļiem. + +#### *Ja tu nejūties ērti ar komandrindu, [izmanto GUI rīku pamācības.]( #pamācības-citiem-rīkiem )* + + +fork this repository + +Ja tavā datorā nav git, [uzinstalē to]( https://help.github.com/articles/set-up-git/). + +## Izveido repozitorija atzarojumu + +Izveido savu repozitorija atzarojumu, nospiežot *fork* pogu šīs lapas augšpusē. +Tādējādi tavā profilā tiks izveidota šī repozitorija kopija. + +## Klonē repozitoriju + +clone this repository + +Tagad klonē nokopēto repozitoriju savā datorā. Ej uz savu GitHub profilu, atver nokopēto repozitoriju, nospied *clone* pogu un tad nospied uz *copy to clipboard* ikonas. + +Atver termināli un palaid šo git komandu: + +``` +git clone "tikko nokopētā saite" +``` +kur "tikko nokopētā saite" (bez pēdiņām) ir url uz šo repozitoriju (tavs projekta atzarojums). Apskaties iepriekšējos soļos, kā dabūt url. + +copy URL to clipboard + +Piemēram: +``` +git clone https://github.com/tavs-vārds/first-contributions.git +``` +kur `tavs-vārds` ir tavs GitHub lietotājvārds. Šādi tu kopē GitHub repozitorija *first-contributions* saturu savā datorā. + +## Izveido zaru + +Savā datorā nomaini repozitorija direktoriju (ja tu vēl neatrodies tajā): + +``` +cd first-contributions +``` +Tagad izveido zaru ar `git checkout` komandu: +``` +git checkout -b +``` + +Piemēram: +``` +git checkout -b add-alonzo-church +``` +(Zara nosaukumā nav obligāti jābūt vārdam *add*, bet būtu lietderīgi to iekļaut, jo šī zara mērķis ir tava vārda pievienošana sarakstam.) + +## Veic nepieciešamās izmaiņas un iesūti tās + +Tagad atver `Contributors.md` failu teksta redaktorā un pievieno tam savu vārdu. Nepievieno to faila sākumā vai beigās, bet ievieto to kaut kur pa vidu. Pēc tam saglabā failu. + +git status + + +Ja tu dosies uz projekta direktoriju un izpildīsi komandu `git status`, tu redzēsi, ka tajā ir izmaiņas. + + +Pievieno šīs izmaiņas zaram, kuru tu tikko izveidoji, ar `git add` komandu: + +``` +git add Contributors.md +``` + +Tagad iesūti šīs izmaiņas ar `git commit` komandu: +``` +git commit -m "Add to Contributors list" +``` +aizvietojot `` ar savu vārdu. + +## Pievieno izmaiņas GitHub + +Pievieno savas izmaiņas ar komandu `git push`: +``` +git push origin +``` +aizvietojot `` ar zara, kuru tu iepriekš izveidoji, nosaukumu. + +## Iesniedz izmaiņas pārskatīšanai + +Ja tu dosies uz savu GitHub repozitoriju, tu redzēsi `Compare & pull request` pogu. Nospied to. + +create a pull request + +Tagad iesniedz pievienotās izmaiņas. + +submit pull request + +Jau pavisam drīz es pievienošu visas tavas izmaiņas šī projekta galvenajam (master) zaram. Tu saņemsi paziņojumu e-pastā, tiklīdz izmaiņas būs pievienotas. + +## Un ko tagad? + +Apsveicam! Tu tikko pabeidzi standarta _fork -> clone -> edit -> PR_ darbplūsmu, ar kuru turpmāk bieži nāksies sastapties kā līdzautoram. + +Pastāsti par savu devumu saviem draugiem un sekotājiem, izmantojot [mūsu vietni](https://firstcontributions.github.io/#social-share). + +Tu vari pievienoties arī mūsu slack komandai, ja tev nepieciešama palīdzība vai ir kādi jautājumi. [Pievienojies slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Tagad tu vari līdzdarboties arī citos projektos. Mēs esam sastādījuši sarakstu ar projektiem, kuros ir vienkāršas problēmas, ar kurām tu varētu sākt. Izpēti [projektu sarakstu mūsu vietnē](https://firstcontributions.github.io/#project-list). + +### [Papildu materiāli](../additional-material/git_workflow_scenarios/additional-material.md) + + +## Pamācības citiem rīkiem + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.me.md b/translations/README.me.md new file mode 100644 index 00000000000..9b5ba3d804e --- /dev/null +++ b/translations/README.me.md @@ -0,0 +1,129 @@ +[![Open Source Love](https://firstcontributions.github.io/open-source-badges/badges/open-source-v1/open-source.svg)](https://github.com/firstcontributions/open-source-badges) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Prvi doprinos + +Ovaj projekat ima za cilj da pojednostavi i vodi početnike do njihovog prvog doprinosa. Ako želite da napravite vaš prvi doprinos, pratite korake ispod. + +_Ako nijeste navikli da koristite komandnu liniju, [evo tutorijala koji koristi GUI alatke.](#Tutorijali-koji-koriste-druge-alatke)_ + +napravite kopiju repozitorijuma + +#### Ako nemate git na svojoj mašini, [instalirajte ga ovdje](https://help.github.com/articles/set-up-git/). + +## Napravite kopiju repozitorijuma + +Napravite kopiju _(fork)_ ovog repozitorijuma tako što ćete kliknuti na dugme **fork** na vrhu stranice. + +Ovo će kreirati kopiju ovog repozitorijuma na vašem nalogu. + +## Klonirajte repozitorijum + +Klonirajte repozitorijum + +Sada klonirajte repozitorijum na vašu mašinu. Idite na vaš GitHub profil, otvorite kopiju repozitorijuma, kliknite na dugme **code** i kliknite ikonicu *copy to clipboard*. + +Otvorite terminal i unesite sledeću git komandu: + +``` +git clone "url koji ste upravo kopirali" +``` + +Umjesto "url koji ste upravo kopirali" (bez znaka navoda) unesite url repozitorijuma koji ste kopirali u prethodnom koraku. + +Kopirajte URL + +Na primjer: + +``` +git clone https://github.com/korisnicko-ime/first-contributions.git +``` + +Umjesto `korisnicko-ime` napišite korisničko ime za vaš GitHub nalog. Na ovaj način kopirate sadržaj repozitorijuma na vašu mašinu. + +## Kreiranje grane _(branch)_ + +Prebacite se u radni direktorijum na vašem računaru (ukoliko već nijeste tu): + +``` +cd first-contributions +``` + +Sada kreirajte granu koristeći komadu `git checkout`: + +``` +git checkout -b ime-vase-grane + +``` + +Na primjer: + +``` +git checkout -b add-nikola-popovic +``` + +(Ime grane ne mora sadržati riječ _add_, ali je to preporučljivo jer je poenta ove grane da se doda vaše ime na listu kontributora.) + +## Napravite potrebne promjene i potvrdite ih + +Sada otvorite fajl `Contributors.md` u tekst editoru i dodajte vaše ime. Nemojte dodati svoje ime na početku ili na kraju fajla. Stavite ga bilo gdje između. Sada, sačuvajte fajl. + +git status + +Ako se vratite na radni direktorijum i izvršite komandu `git status`, vidjećete da su prisutne promjene. + +Dodajte te promjene u granu koju ste kreirali u prethodnim koracima koristeći komandu `git add`: + +``` +git add Contributors.md +``` + +Sada potvrdite te izmjene koristeći komandu `git commit` : + +``` +git commit -m "Add to Contributors list" +``` + +Umjesto `` napišite vaše ime. + +## Pošaljite izmjene u repozitorijum + +Pošaljite izmjene koje ste napravili u repozitorijum na GitHub-u koristeći komandu `git push`: + +``` +git push origin +``` + +Umjesto `` napišite ime grane koju ste kreirali ranije. + +## Pošaljite vaše izmjene na provjeru + +Ako odete na repozitorijum na GitHub-u, vidjećete dugme **Compare / Pull Request**. Kliknite to dugme. + +Kreirajte pull request + +Sada pošaljite vaš pull request. + +Pošaljite pull request + +Uskoro, ja ću spojiti promjene koje ste napravili sa master granom repozitorijuma. Dobićete mejl potvrde kada se grane spoje. + +## Šta dalje? + +Čestitamo! Upravo ste izvršili standradni _fork -> clone -> edit -> pull request_ proces koji ćete često gledati dok doprinosite kodu. + +Proslavite vaš doprinos i podijelite ga sa prijateljima i pratiocima kroz [stranicu](https://firstcontributions.github.io/#social-share). + +Ukoliko vam je potrebna pomoć ili imate neka pitanja, možete da se priključite našem [Slack timu](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Sada možete početi da doprinosite i drugim projektima. Sastavili smo listu projekata sa jednostavim problemima na kojima možete početi da radite. Pogledajte [listu projekata na stranici](https://firstcontributions.github.io/#project-list). + +### [Dodatni materijali](additional-material/git_workflow_scenarios/additional-material.md) + +## Tutorijali koji koriste druge alatke + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.mk.md b/translations/README.mk.md new file mode 100644 index 00000000000..85ce622ca54 --- /dev/null +++ b/translations/README.mk.md @@ -0,0 +1,124 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Први чекори + +Тешко е. Секогаш е тешко кога нешто се прави за прв пат. Кога соработуваме со други луѓе, правењето грешки е непријатно. Затоа сакавме да го поедноставиме начинот на кој новите соработници на отворен код учат и допринесуваат за прв пат. + +Читањето на статии и гледањето на видеа помага до некаде, но нема подобар начин за учење од вежбањето. Целта на овој проект е да се обезбеди вежба и да се поедностави начинот по кој почетниците допринесуваат отворен код. Ако сакате да го направите својот прв придонес, тогаш следете ги долунаведените чекори. + +#### *Ако не сакате да користите command line (терминал), [овде имате упатства за GUI](#Вежби-за-користење-на-други-програми)* + + +fork this repository + +Ако немате git на вашиот компјутер, [инсталирајте го]( https://help.github.com/articles/set-up-git/). + +## Направете Разгранување (Fork) на ова складиште (repository) + +Направете разгранување на складиштето со притискање на копчето "Fork" кое се наоѓа на горниот дел на оваа страница. +Вака ќе направите копија на складиштето во вашиот GitHub профил. + +## Клонирајте го овоа складиште + +clone this repository + +Сега треба да го клонирате складиштето во вашиот компјутер. Отидете во вашиот GitHub профил, отворете го разгранетото складиште, +кликнете на копчето "Clone" и копирајте го линкот. Исто така може да притиснете на иконата за копирање (Copy to clipboard) + +Отворете го терминалот и воведете ја следната команда: + +``` +git clone "линкот кој го копиравте" +``` +На местото на "линкот кој го копиравте" (без наводници) поставете го линкот на складиштето (Вашето Разгранување на овој проект). Погледнете ги претходните чекори за да видете како да го добиете линкот. + +copy URL to clipboard + +На пример: +``` +git clone https://github.com/vashiot-username/first-contributions.git +``` +со преименување на `vashiot-username` во вашето корисничко име. Во овој чекор правите копија на складиштето first-contributions од GitHub кон вашиот компјутер. + +## Создавање на гранка (branch) + +Променете ја локацијата на складиштето во вашиот компјутер (Ако сеуште не сте ја промениле): + +``` +cd first-contributions +``` +Сега создајте гранка со помош на командата `git checkout`: +``` +git checkout -b +``` + +На пример: +``` +git checkout -b add-alonzo-church +``` +(Името на гранката не мора да го содржи зборот *add*, но се препорачува, затоа што целта на оваа гранка е да го додадете вашето име во списокот.) + +## Направете ги потребните промени и извршете (commit) ги + +Сега отворете го фајлот `Contributors.md` во уредник за текст и додадете го вашето име. Не додавајте го на почетокот или крајот на фајлот. Поставете го некаде на средината. Зачувајте ги промените. + +git status + + +Ако ја извршете командата `git status` во директоријата на складиштето, ќе забележите дека има промени. + + +Зачувајте ги промените на создадената гранката со помош на командата `git add`: + +``` +git add Contributors.md +``` + +Сега извршете ги промените со командата `git commit`: +``` +git commit -m "Add to Contributors list" +``` +со промена на `` со вашето име. + +## Поставете (Push) ги промените во GitHub + +Поставете ги вашите промени со командата `git push`: +``` +git push origin +``` +со промена на `` во името на вашата гранка, која ја создадовте претходно. + +## Поднесете ги вашите промени за преглед. + +Ако отидете во вашето складиште во GitHub, ќе го забележите копчето `Compare & pull request`. Притиснете го. + +create a pull request + +Сега поднесете ги вашите промени за преглед. + +submit pull request + +Наскоро ќе ги спојам (merge) сите ваши промени во главната гранка (мастер branch) на овој проект. Ќе бидете известени по пат на електронска пошта за спојот на вашите промени. + +## Што е следно? + +Честитки! Само што ги завршивте _fork -> clone -> edit -> PR_ операции, со кои ќе се соочувате често како соработник! + +Прославете ги вашите придонеси и споделете ги со пријатели и следители со посета на [веб-апликацијата](https://roshanjossey.github.io/first-contributions/#social-share). + +Можете да станете дел од нашиот slack team ако ви треба помош или имате прашања [Стани дел](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Сега е време да започнете да допринесувате кон други проекти. Ние имаме создадено список со лесни проекти за да започнете. [Види ја листата](https://roshanjossey.github.io/first-contributions/#project-list). + +### [Дополнителен материал](../additional-material/git_workflow_scenarios/additional-material.md) + + +## Вежби за користење на други програми + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.ml.md b/translations/README.ml.md new file mode 100644 index 00000000000..3dfcf77170d --- /dev/null +++ b/translations/README.ml.md @@ -0,0 +1,131 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# ആദ്യ സംഭാവനകൾ (First Contributions) + +ആദ്യമായി ഒരു കാര്യം ചെയ്യുക എന്നുള്ളത് വളരെ ബുദ്ധിമുട്ടാണ്. പ്രത്യേകിച്ച്, മറ്റു പലരുടെയും ഒപ്പം ജോലി ചെയ്യുമ്പോൾ തെറ്റ് വരുന്നത് അത്ര സുഖകരമായ കാര്യം അല്ല. സ്വതന്ത്ര സോഫ്റ്റ്‌വെയറിലേക്ക് ആദ്യമായി സംഭാവന ചെയ്യുന്നവർക്ക് അതിനെ പറ്റി പഠിക്കാനും പങ്കാളി ആകുവാനും വേണ്ടി കുറച്ച്‌ കൂടെ എളുപ്പമായ എന്തെങ്കിലും ഉണ്ടാക്കണമെന്നായിരുന്നു ഞങ്ങളുടെ ആഗ്രഹം. + +ലേഖനങ്ങൾ വായിക്കുന്നതും വീഡിയോ കാണുന്നതും ഒക്കെ സഹായകരമാണ്. പക്ഷേ ചെയ്ത് തന്നെ പഠിക്കുന്നതല്ലേ ഏറ്റവും നല്ലത്? ഈ പ്രൊജക്റ്റ് ഇതിനെ പറ്റി പരിചയം ഇല്ലാത്ത ഒരാൾക്ക് ആദ്യത്തെ സംഭാവന നല്കാൻ ഉള്ള ഒരു വഴികാട്ടി ആണ്. നിങ്ങളും നിങ്ങളുടെ ആദ്യ സംഭാവന നൽകാൻ ആഗ്രഹിക്കുന്നു എങ്കിൽ താഴെ പറയുന്നത് പോലെ ചെയ്യുക. + +#### *താങ്കൾക്ക് കമാൻഡ് ലൈൻ ഉപയോഗിച്ച്‌ പരിചയം ഇല്ലെങ്കിൽ, [GUI ഉപയോഗിച്ച് ചെയ്യാൻ ഉള്ള നിർദേശങ്ങൾ ഇവിടെ ലഭ്യമാണ്](#മറ്റു-ഉപകരണങ്ങൾ-ഉപയോഗിച്ച്-ചെയ്യുന്നതിനെ-പറ്റിയുള്ള-ലേഖനങ്ങൾ)*. + +fork this repository + +താങ്കളുടെ കമ്പ്യൂട്ടറിൽ ഗിറ്റ് (git) ഇല്ലെങ്കിൽ, [ഇൻസ്റ്റാൾ ചെയ്യുക](https://help.github.com/articles/set-up-git/). + +## ഈ റെപ്പോസിറ്ററി ഫോർക്ക് (fork) ചെയ്യുക + +ഈ പേജിന്റെ ഏറ്റവും മുകളിൽ ഉള്ള ഫോർക്ക് ബട്ടൺ ഉപയോഗിച്ച് ഈ റെപ്പോസിറ്ററി ഫോർക്ക് ചെയ്യുക. ഇങ്ങനെ ചെയ്യുമ്പോൾ നിങ്ങളുടെ അക്കൗണ്ടിൽ ഈ റെപ്പോസിറ്ററിയുടെ ഒരു പകർപ്പ് സൃഷ്ടിക്കപ്പെടുന്നു. + +## ഈ റെപ്പോസിറ്ററി ക്ലോൺ (clone) ചെയ്യുക + +clone this repository + +ഇനി ഫോർക്ക് ചെയ്ത റെപ്പോസിറ്ററി നിങ്ങളുടെ കമ്പ്യൂട്ടറിലേക്ക് ക്ലോൺ ചെയ്യുക. നിങ്ങളുടെ ഗിറ്റ്ഹബ് (GitHub) അക്കൗണ്ട് എടുത്ത് അതിൽ ഫോർക്ക് ചെയ്ത റെപ്പോസിറ്ററി തുറക്കുക. എന്നിട്ട് മുകളിൽ ക്ലോൺ ബട്ടണിലെ *കോപ്പി ടു ക്ലിപ്പ് ബോർഡ് (Copy to clipboard)* എന്ന ഐക്കൺ ക്ലിക്ക് ചെയ്യുക. + +എന്നിട്ട് ഒരു ടെർമിനൽ എടുത്ത് താഴെ പറയുന്ന ഗിറ്റ് കമാൻഡ് റൺ ചെയ്യുക: + +``` +git clone <നിങ്ങളുടെ-ലിങ്ക്> +``` + +ഇതിൽ `<നിങ്ങളുടെ-ലിങ്ക്>` എന്ന് പറയുന്നത് താങ്കളുടെ (ഫോർക്ക് ചെയ്ത) റെപ്പോസിറ്ററി ലിങ്ക് ആണ്. ലിങ്ക് എങ്ങനെ കോപ്പി ചെയ്യാം എന്നറിയാൻ ഇതിനു മുൻപ് ഉള്ള നിർദേശം നോക്കുക. + +copy URL to clipboard + +ഉദാഹരണം: + +``` +git clone https://github.com/താങ്കൾ/first-contributions.git +``` + +ഇതിൽ `താങ്കൾ` എന്നതിന് പകരം നിങ്ങളുടെ ഗിറ്റ്ഹബ് യൂസർനെയിം കൊടുക്കുക. ഇപ്പോൾ നിങ്ങൾ ചെയ്യുന്നത് നിങ്ങളുടെ ഗിറ്റ്ഹബിലെ ഫസ്റ്റ്-കോണ്ട്രിബൂഷൻസ് (first-contributions) റെപ്പോസിറ്ററിയിൽ ഉള്ളവ നിങ്ങളുടെ കമ്പ്യൂട്ടറിലേക്ക് കോപ്പി ചെയ്യുകയാണ്. + +## ഒരു ശാഖ (ബ്രാഞ്ച്, Branch) ഉണ്ടാക്കുക + +നിങ്ങളുടെ റെപ്പോസിറ്ററിയിലേക്ക് കടക്കുക: + +``` +cd first-contributions +``` + +എന്നിട്ട് `git checkout` എന്ന കമാൻഡ് ഉപയോഗിച്ച് ഒരു ബ്രാഞ്ച് ഉണ്ടാക്കുക: + +``` +git checkout -b <നിങ്ങളുടെ-പുതിയ-ബ്രാഞ്ചിന്റെ-പേര്> +``` + +ഉദാഹരണം: + +``` +git checkout -b add-alonzo-church +``` + +(ബ്രാഞ്ചിന്റെ പേരിൽ add എന്ന് ഉണ്ടാകണം എന്ന് നിർബന്ധം ഇല്ല. പക്ഷെ നിങ്ങളുടെ ഉദ്ദേശം നിങ്ങളുടെ പേര് ഇതിൽ ഉൾപ്പെടുത്തണം എന്നത് ആണെന്നതിനാൽ അത് കൊടുക്കുന്നതാണ് നല്ലത്.) + +## ആവശ്യത്തിനുള്ള വ്യത്യാസങ്ങൾ വരുത്തി അവ കമ്മിറ്റ് (commit) ചെയ്യുക + +ഇനി `Contributors.md` എന്ന ഫയൽ ഒരു എഡിറ്റർ ഉപയോഗിച്ച് തുറന്നതിനു ശേഷം താങ്കളുടെ പേര് അതിൽ ഉൾപ്പെടുത്തുക. അങ്ങനെ ചെയ്യുമ്പോൾ തുടക്കത്തിലോ അവസാനത്തിലോ അല്ലാതെ ഇടയിൽ എവിടെയെങ്കിലും ഉൾപെടുത്തുക. എന്നിട്ട് ആ ഫയൽ സേവ് ചെയ്യുക. + +git status + +താങ്കളുടെ പ്രൊജക്റ്റ് ഡയറക്ടറിയിൽ ചെന്ന് `git status` എന്ന കമാൻഡ് അടിച്ചു നോക്കിയാൽ താങ്കൾ വരുത്തിയ വ്യത്യാസങ്ങൾ കാണാൻ സാധിക്കും. + +ഈ വ്യത്യാസങ്ങൾ `git add` കമാൻഡ് ഉപയോഗിച്ച്‌ നിങ്ങളുടെ ബ്രാഞ്ചിലേക്ക് ചേർക്കുക: + +``` +git add Contributors.md +``` + +ഇനി നിങ്ങൾ ഉണ്ടാക്കിയ വ്യത്യാസങ്ങൾ `git commit` കമാൻഡ് ഉപയോഗിച്ച് കമ്മിറ്റ് ചെയ്യുക: + +``` +git commit -m "Add <താങ്കളുടെ-പേര്> to Contributors list" +``` + +ഇതിൽ `<താങ്കളുടെ-പേര്>` എന്ന സ്ഥാനത്ത് താങ്കളുടെ ശരിയായ പേര് കൊടുക്കുക. + +## വ്യത്യാസങ്ങൾ ഗിറ്റ്ഹബിലേക്ക് ചേർക്കുക (push) + +`git push` കമാൻഡ് ഉപയോഗിച്ച് വ്യത്യാസങ്ങൾ ഗിറ്റ്ഹബിലേക്ക് പുഷ് ചെയ്യുക: + + +``` +git push origin <താങ്കളുടെ-ബ്രാഞ്ചിന്റെ-പേര്> +``` + +ഇതിൽ <താങ്കളുടെ-ബ്രാഞ്ചിന്റെ-പേര്> എന്നതിന് പകരം താങ്കൾ നേരത്തെ ഉണ്ടാക്കിയ ബ്രാഞ്ചിന്റെ പേര് കൊടുക്കുക. + +## നിങ്ങളുടെ വ്യത്യാസങ്ങൾ പരിശോധനക്കായി (review) സമർപ്പിക്കുക + +നിങ്ങൾ ഇപ്പോൾ നിങ്ങളുടെ ഗിറ്റ്ഹബ് റെപ്പോസിറ്ററിയിൽ പോയി നോക്കിയാൽ അവിടെ `Compare & pull request` എന്ന ഒരു ബട്ടൺ കാണാം. അതിൽ അമർത്തുക. + +create a pull request + +ഇനി പുൾ റിക്വസ്റ്റ് (pull request) കൊടുക്കുക. + +submit pull request + +വൈകാതെ തന്നെ ഞാൻ താങ്കളുടെ വ്യത്യാസങ്ങൾ പ്രധാന ബ്രാഞ്ചിലേക്ക് ചേർക്കുന്നതായിരിക്കും. അപ്പോൾ താങ്കൾക്ക് ഒരു ഇമെയിൽ അറിയിപ്പ് ലഭിക്കും. + +## ഇവിടെ നിന്ന് ഇനി എങ്ങോട്ട്? + +അഭിനന്ദനങ്ങൾ! താങ്കൾ താങ്കളുടെ ആദ്യത്തെ _fork -> clone -> edit -> PR_ പടികൾ വിജയകരമായി പൂർത്തിയാക്കിയിരുന്നു. ഒരു സംഭാവകൻ എന്ന നിലക്ക് ഇത് താങ്കൾക്ക് ഇടയ്ക്കിടെ ചെയ്യേണ്ടി വരുന്ന ഒരു കാര്യം ആണ്! + +താങ്കളുടെ സംഭാവന സുഹൃത്തുക്കളും പിൻഗാമികളുമായി (followers) പങ്കിട്ട് ആഘോഷിക്കുവാനായി ഈ [വെബ് ആപ്പ് എടുക്കുക](https://firstcontributions.github.io/#social-share). + +താങ്കൾക്ക് എന്തെങ്കിലും സഹായം വേണമെങ്കിൽ, അല്ലെങ്കിൽ എന്തെങ്കിലും ചോദ്യങ്ങൾ ഉണ്ടെങ്കിൽ ഞങ്ങളുടെ [slack team-ൽ ചേരുവാനായി റിക്വസ്റ്റ് അയക്കുക](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +ഇനി താങ്കൾക്ക് മറ്റുള്ള പ്രൊജെക്ടുകളിൽ സംഭാവന ചെയ്യുവാൻ സാധിക്കും. താങ്കൾക്ക് വേഗം തുടങ്ങുവാൻ വേണ്ടി ഞങ്ങൾ എളുപ്പത്തിൽ തീർക്കാവുന്ന പ്രശ്നങ്ങൾ (issues) ഉള്ള പ്രോജക്ടുകളുടെ ഒരു ലിസ്റ്റ് ഉണ്ടാക്കിയിട്ടുണ്ട്. അത് ഇവിടെ കാണുക: [പ്രോജക്ടുകളുടെ ലിസ്റ്റ്](https://firstcontributions.github.io/#project-list). + +### [കൂടുതൽ വായിക്കുക](../additional-material/git_workflow_scenarios/additional-material.md) + + +## മറ്റു ഉപകരണങ്ങൾ ഉപയോഗിച്ച് ചെയ്യുന്നതിനെ പറ്റിയുള്ള ലേഖനങ്ങൾ + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.mm_unicode.md b/translations/README.mm_unicode.md new file mode 100644 index 00000000000..22ec1754f1d --- /dev/null +++ b/translations/README.mm_unicode.md @@ -0,0 +1,195 @@ +[![Open Source Love](https://firstcontributions.github.io/open-source-badges/badges/open-source-v1/open-source.svg)](https://github.com/firstcontributions/open-source-badges) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# + +#### _[တခြားဘာသာစကားများဖြင့်](translations/Translations.md) ဖတ်ရန်။_ + +[Shqip](translations/README.al.md) +[Azərbaycan dili](translations/README.aze.md) +[বাংলা](translations/README.bn.md) +[Bulgarian](translations/README.bg.md) +[Português](translations/README.pt_br.md) +[Català](translations/README.ca.md) +[中文 (Simplified)](translations/README.chs.md) +[Czech](translations/README.cs.md) +[Deutsch](translations/README.de.md) +[Dansk](translations/README.da.md) +[العربية](translations/README.eg.md) +[Española](translations/README.es.md) +[Française](translations/README.fr.md) +[Galego](translations/README.gl.md) +[Ελληνικά](translations/README.gr.md) +[ქართული](translations/README.ge.md) +[Magyar](translations/README.hu.md) +[Bahasa Indonesia](translations/README.id.md) +[עִברִית](translations/README.hb.md) +[हिंदी/ગુજરાતી/मराठी/മലയാളം/ಕನ್ನಡ/తెలుగు/छत्तीसगढ़ी/বাংলা/தமிழ்](translations/Translations.md) +[தமிழ்](translations/README.ta.md) +[فارسی](translations/README.fa.md) +[Italiano](translations/README.it.md) +[日本語](translations/README.ja.md) +[Kiswahili (Kenya)](translations/README.kws.md) +[한국어 한국어](translations/README.ko.md) +[Lietuvių kalba](translations/README.lt.md) +[Limba Română Limba Română](translations/README.ro.md) +[မြန်မာ](translations/README.mm_unicode.md) +[Македонски](translations/README.mk.md) +[Español de México](translations/README.mx.md) +[Bahasa Melayu / بهاس ملايو‎ / Malay](translations/README.my.md) +[Dutch](translations/README.nl.md) +[Norsk](translations/README.no.md) +[नेपाली](translations/README.np.md) +[Wikang Filipino](translations/README.tl.md) +[English (Pirate)](translations/README.en-pirate.md) +[اردو](translations/README.ur.md) +[Polski](translations/README.pl.md) +[Português (Portugal)](translations/README.pt-pt.md) +[Русский язык](translations/README.ru.md) +[عربى](translations/README.ar.md) +[Svenska](translations/README.se.md) +[Slovenčina](translations/README.slk.md) +[Slovenščina](translations/README.sl.md) +[ภาษาไทย](translations/README.th.md) +[Türkçe](translations/README.tr.md) +[中文(Traditional)](translations/README.cht.md) +[Українська](translations/README.ua.md) +[Tiếng Việt](translations/README.vn.md) +[Zulu (South Africa)](translations/README.zul.md) +[Afrikaans (South Africa)](translations/README.afk.md) +[Igbo (Nigeria)](translations/README.igb.md) +[Latvia](translations/README.lv.md) +[Suomeksi](translations/README.fi.md) +[Беларуская мова](translations/README.by.md) +[Српски](translations/README.sr.md) +[Қазақша](translations/README.kz.md) +[Bosanski](translations/README.bih.md) + +# + +# ပထမအကြိမ် ကူညီထောက်ပံ့ခြင်း + +ဘယ်အရာမဆို ပထမဦးဆုံးလုပ်ဆောင်အခါ အခက်အခဲတွေ့ကြုံရပါတယ်။ အထူးသဖြင့် လူအများနဲ့ ပေါင်းသင်းလုပ်ကိုင်ကြတဲ့ အခါ မထင်မှတ်ထားတဲ့ အမှားများတွေ့ရတတ်ပြီး အဆင်မပြေတာတွေဖြစ်တတ်ပါတယ်။ Open source software များကတော့ လူအများနဲ့ ပေါင်းသင်းဆက်ဆံလုပ်ကိုင် ကြရတာပါ။ ဒါကြောင့်မို့ ပထမဦးဆုံးအကြိမ် open-source project များကို ပါဝင် ကူညီထောက်ပံ့သူများကို ပထမဆုံးအကြိမ် ကူညီထောက်ပံ့နိုင်ဖို့နဲ့ လွယ်ကူ ရိုးရှင်းတဲ့ လေ့လာနည်းဖြစ်ဖို့ ရည်ရွယ်ပါတယ်။ + +လေ့ကျင်ခန်း စာစောင်တွေနဲ့ ဗီဒီယိုတွေက အကူအညီရနိုင်သော်လဲ တကယ်လက်တွေ့လုပ်ဆောင်တာထက် ပိုကောင်းတာမရှိပါဘူး။ ဒီ project က ပထမဆုံးအကြိမ် ကူညီထောက်ပံ့ပေးမဲ့ သူတွေအတွက် လွယ်ကူ ရှိးရှင်းပြီး အကူအညီအထောက်ပံ့ဖြစ်စေဖို့ ရည်ရွယ်ပါတယ်။ မှတ်ထားပါ : သင်ကသက်တောင်သက်သာရှိလေလေ သင်ကပိုကောင်းကောင်းသင်ယူနိုင်လေ ဖြစ်တယ်။ သင်သာ အောက်မှာရှိတဲ့ အဆင့်တိုင်းလုပ်သွားလျှင် သင့်ရဲ့ ပထမဆုံး ကူညီထောက်ပံခြင်းမှာ အဆင်ပြေစွာ ပြီးမြောက်သွားမှာဆိုတာ အာမခံပါတယ်။ + +_command line (သို့) terminal အသုံးပြုရတာ အဆင်မပြေပါက [GUI tools အသုံးပြုပုံများကို ဒီမှာကြည့်ရန်](#အခြား-Tools-များ-အသုံးပြုသည့်-tutorial)_ + +fork this repository + +#### သင့်ကွန်ပျူတာထဲမှာ Git မသွင်းရသေးလျှင် [ဒီမှာ သွင်းနည်းကြည့်ရန်](https://help.github.com/articles/set-up-git/). + +## ဒီ repository ကို fork လုပ်ပါ + +Fork လုပ်ဖို့အတွက် စာမျက်နှာအပေါ်နားမှရှိတဲ့ fork ခလုတ် ကိုနှိပ်ပါ။ +ဒီ repository က သင့် အကောင့်ကို ပုံစံတူပွားအနေနဲ့ ရောက်လာပါမယ်။ + +## ဒီ repository ကို clone လုပ်ပါ + +clone this repository + +ခုနက fork လုပ်ထားတဲ့ repository ကို သင့်ကွန်ပျူတာထဲ clone လုပ်ပါမယ်။ သင့် Github အကောင့်ကိုသွားပြီး fork လုပ်ထားတဲ့ repository ကို ဖွင့်ပါ။ Code ဆိုတဲ့ ခလုတ်လေးကို နှိပ်ပြီး _copy to clipboard_ icon လေးကို နှိပ်ပါ။ + +command line (သို့) terminal ကိုဖွင့်ပြီး အောက်က Git command ကို run ပါ။ + +``` +git clone "ခုနက copy ထားတဲ့ လင့်ခ်" +``` + +"ခုနက copy ထားတဲ့ လင့်ခ်" (quotation marks မထည့်ရပါ) ဆိုတာဟာ ဒီ repository(ဒီပရောဂျက်ရဲ့ သင့် fork)ရဲ့ လင့်ခ်ပဲ ဖြစ်ပါတယ်။ ဒီနေရာမှာ အဆင်မပြေဖြစ်ခဲ့ရင် အပေါ်က အဆင့်များကို ပြန်လုပ်ပါ။ + +copy URL to clipboard + +ဥပမာ: + +``` +git clone https://github.com/this-is-you/first-contributions.git +``` + +`this-is-you` ဆိုတာ သင့်ရဲ့ Github username ပဲ ဖြစ်ပါတယ်။ ဒီအဆင့်တွေက Github မှာရှိတဲ့ first-contributions repository ကို သင့်ကွန်ပျူတာထဲသို့ ကူးထည့်တာပဲ ဖြစ်ပါတယ်။ + +## Branch အသစ်လုပ်ခြင်း + +သင် copy လုပ်ထားတဲ့ repository directory ကို မရောက်သေးရင် အောက်က command ကို run ပြီး ရောက်အောင်သွားပါ။ + +``` +cd first-contributions +``` + +Branch အသစ်ကို `git checkout` command ကို run ပြီးလုပ်ပါ။ + +``` +git checkout -b your-new-branch-name +``` + +ဥပမာ: + +``` +git checkout -b add-alonzo-church +``` + +(Branch နာမည်ဘာဖြစ်ဖြစ်ရပါတယ် သို့သော်လဲ ဒီ project ကသင့် နာမည်ကိုထပ်ထည့်မှာဖြစ်လို့ _add_ သင့်နာမည်ကို အားလုံးနဲ့ အဆင်ပြေအောင်ထည့်ပေးပါ။) + +## ပြောင်းစရာရှိတာများ ပြောင်းပြီး ထိုပြောင်းလဲ့မှုများကို commit လုပ်ခြင်း + +သင့် text editor မှာ `Contributors.md` ကိုဖွင့်ပါ။ ထိပ်ဆုံးနှင့်နောက်ဆုံးမှလွဲ၍ သင့်ရဲ့ နာမည်ကို အဆင်ပြေတဲ့ နေရာမှာထည့်ပြီး save ပါ။ + +git status + +ပြီးရင် ဒီ folder ရှိတဲ့နေရာကိုသွားပြီး `git status` command ကို run ပါ။ သင်ဘာတွေပြောင်းထားလဲဆိုတာ မြင်ရပါလိမ့်မယ်။ + +ဒီပြောင်းလဲမှုတွေကို သင့်ရဲ့ branch ကိုထည့်ဖို့အတွက် `git add` command ကို run ပါ။ + +``` +git add Contributors.md +``` + +အခု commit လုပ်ဖို့ `git commit` command ကို run ပေးပါ။ + +``` +git commit -m "Add to Contributors list" +``` + +`` နေရာမှာ သင့်နာမည်ကို အစားထိုးပါ။ + +## သင့်ရဲ့ ပြောင်းလဲ ပြုပြင်မှုကိုများကို Github သို့တင်ပါ။ + +ပြောင်းလဲမှုများကို Github သို့တင်ဖို့အတွက် `git push` ကို run ပါ။ + +``` +git push origin +``` + +`` နေရာမှာ သင်အသစ်လုပ်ထားတဲ့ branch နာမည်ကိုထည့်ပါ။ + +## သင်ပြောင်းထားတာ တွေကို review လုပ်ဖို့ submit လုပ်ပါ။ + +သင့် GitHub က သင့် repository မှာ `Compare & pull request` ဆိုတဲ့ ခလုတ်မြင်နေရမှာပါ။ အဲ့ဒီ ခလုတ်ကို နှိပ်လိုက်ပါ။ + +create a pull request + +အခု pull request ကို submit လုပ်လိုက်ပါ။ + +submit pull request + +သင့်ရဲ့ပြောင်းလဲမှုတွေကို ဒီ project ရဲ့ master branch မှာ ထည့်သွင်းပေးမှာဖြစ်ပါတယ်။ ဒါကြောင့် ဒီ project ရဲ့ master branch မှာ ထည့်သွင်းပြီးရင် သင့်မှာ notification email ရောက်လာပါလိမ့်မယ်။ + +## ဒါပြီးရင် ဘာတွေဆက် လေ့လာမလဲ + +Congratulation! Open Source Project တွေမှာ အမြဲလုပ်ရလေ့ရှိတဲ့ _fork -> clone -> edit -> pull request_ လုပ်ငန်းစဥ်ကို သင် အောင်မြင်စွာ လုပ်နိုင်ခဲ့ပါပြီ။ + +အခု သင်ကူညီထောက်ပံ့ခဲ့တာကို သင့်သူငယ်ချင်းတွေကို share ချင်ရင် [ဒီ web app](https://firstcontributions.github.io/#social-share) ကို သွားပါ။ + +တခြားအကူအညီများနဲ့ မေးစရာများရှိပါက ကျွန်တော်တို့ရဲ့ Slack team ကို ဝင်ရောက် မေးမြန်းနိုင်ပါတယ်။[Join slack team သို့ ဝင်ရန်](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +နောက်ထပ် ပရောဂျက်များကိုလည်း ဝင်ရောက်ကူညီလိုပါက ကျွန်တော်တို့ ပြုစုထားတဲ့ ပရောဂျက်စာရင်းကို လေ့လာနိုင်ပါတယ်။ [web app ထဲမှ ပရောဂျက်စာရင်း](https://firstcontributions.github.io/#project-list). + +### [အခြား ထွေလီကာလီများ](additional-material/git_workflow_scenarios/additional-material.md) + +## အခြား Tools များ အသုံးပြုသည့် tutorial + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.mr.md b/translations/README.mr.md new file mode 100644 index 00000000000..85ea10b790b --- /dev/null +++ b/translations/README.mr.md @@ -0,0 +1,131 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# प्रथम योगदान + +सुरुवातीला कुठलीही गोष्ट करणे कठीण असते. विशेषत: आपण एकत्र काम करत असताना चुका होणे स्वाभाविक आहे. परंतु एकमेकांसोबत भेटणे आणि एकत्र कार्य करणे हेच तर मुक्त स्त्रोत (Open Source) चे गमक आहे. आम्ही आपले प्रथम मुक्त स्त्रोत योगदान (Contribution) सुलभ करण्यास मदत करू. + +लेख वाचणे आणि ट्यूटोरियल पाहण्याने आपणास मदत होऊ शकते परंतु प्रत्यक्षात सराव करण्यापेक्षा काय चांगले आहे? या प्रकल्पाचा हेतू नवशिक्यांना आपले प्रथम योगदान देण्यासंदर्भात सोप्या स्वरुपात मार्गदर्शन प्रदान करण्याचा आहे. आपण आपले प्रथम योगदान देत असल्यास, खालील पायऱ्यांचे अनुसरण करा. + +#### *जर आपल्याला कमांड लाईन (CLI) सोयीस्कर वाटत नसेल तर [GUI टूल्स वापरण्यासंदर्भात ट्यूटोरियल येथे आहेत.](#इतर-साधने-वापरण्याबाबतीत-ट्युटोरियल)* + + +[](translations/README.en-pirate.md) + +fork this repository + +आपण आपल्या मशीनवर Git नसेल तर, [येथुन इन्स्टॉल करा](https://help.github.com/articles/set-up-git/). + +## रिपॉझिटरी (Repository) ला फोर्क (Fork) करणे + +फोर्क बटण क्लिक करून या रिपोला फोर्क करा. +हे आपल्या खात्यात या रिपॉझिटरीची प्रत (कॉपी) तयार करेल. + +## रिपॉझिटरी (Repository) ला क्लोन (Clone) करणे + +clone this repository + +आता फोर्क केलेला रिपो आपल्या संगणकावर क्लोन (Clone) करा. यासाठी आपण आपल्या गिटहब (GitHub) खात्यावर जा. जो रिपो आपण फोर्क केलेला आहे, त्याला उघडा. उघडलेल्या रिपोत उजव्या बाजुला वर `Clone or download` बटण दिसेल, त्यावर क्लिक करा. नंतर तेथील `Copy to clipboard` या आयकॉनवर क्लिक करा. याद्वारे प्रस्तुत रिपोची लिंक (URL) कॉपी झालेली असेल. + +आता आपले टर्मिनल (Terminal) उघडा व त्यात खालील git आदेश (Command) चालवा. + +``` +git clone <कॉपी-केलेली-लिंक> +``` + +copy URL to clipboard + +येथे `<कॉपी-केलेली-लिंक>` (त्रिकोणी कंस वगळता) यास आपण आताच कॉपी केलेली URL लिंक असे ग्राह्य धरण्यात यावे. ही URL लिंक मिळवण्याकरता याआधीच्या पायरीचे अवलोकन करावे. + +उदाहरणार्थ: + +``` +git clone https://github.com/तुमचे-युझर-नाव/first-contributions.git +``` + +येथे `तुमचे-युझर-नाव` याचा अर्थ आहे, आपल्या गिटहब खात्याचे नाव (Username). + +आता एंटर (Enter/Return) बटण दाबा. याद्वारे प्रस्तुत रिपो `first-contributions` आपल्या संगणकावर कॉपी होईल. + +## ब्रांच (Branch) बनवणे. + +आपल्या टर्मिनल वरुन आपली रिपो फोल्डर/डायरेक्टरी (Folder/Directory) बदला (जर आपण अद्याप बदलले नसेल तर). + +``` +cd first-contributions +``` + +आता `git checkout` ही कमांड वापरुन नवीन ब्रांच तयार करा. + +``` +git checkout -b <आपल्या-ब्रांचचे-नाव-येथे-टाका> +``` + +उदा: + +``` +git checkout -b add-rahul-thakare +``` + +(प्रत्येक ब्रांचच्या नावात `add` हा शब्द असणे आवश्यक नाही, परंतु वरील उदाहरणात त्याचा समावेश असणे ही एक वाजवी गोष्ट आहे कारण ईथे आपले नाव सूचीमध्ये जोडणे हा या शाखेचा उद्देश आहे.) + +## आवश्यक बदल करणे आणि ते बदल कमिट (Commit) करणे. + +आता मजकूर संपादक मध्ये `Contributors.md` फाइल उघडा, व त्यात आपले नाव जोडा. फाइलच्या सुरवातीस किंवा समाप्तीमध्ये जोडू नका. त्यामध्ये कुठेही ठेवा. आता फाईल सेव्ह (Save) करा. + +git status +आता तुम्ही पुन्हा टर्मिनल कडे जाल आणि `git status` ही कमांड चालवाल तर तुम्हाला त्यात काही बदल झालेले दिसतील. + +`git add` कमांड वापरुन आपण तयार केलेल्या शाखेत ते बदल जोडा + +``` +git add Contributors.md +``` + +आता `git commit` ही कमांड वापरुन आपले बदल कमिट/सुरक्षित करा. + +``` +git commit -m "Add <तुमचे-नाव> to Contributors list" +``` + +`<तुमचे-नाव>` च्याऐवजी आपले नाव टाका. + +## गिटहब मध्ये आपले बदल पुश करणे. + +`git push` वापरून आपले बदल पुश करा + +``` +git push origin <आपल्या-शाखेचे-नाव> +``` + +`<आपल्या-शाखेचे-नाव>` च्या जागी आपल्या ब्रांचचे नाव टाका. + +## पुनरावलोकनासाठी आपले बदल सबमिट करणे. + +आपण आपल्या गिटहब प्रोफाइलवर आपल्या रिपो वर गेल्यास, आपल्याला `Compare & pull request` पाठविण्याचा पर्याय दिसेल, ते दाबा. +create a pull request + +आता आपल्या `Pull request` सबमिट करा. + +submit pull request + +लवकरच मी आपले बदल या प्रकल्पाच्या मुख्य शाखेत विलीन करेन. जेव्हा आपले बदल विलीन होतील तेव्हा आपल्याला ई-मेल मिळेल. + +## आता पुढे काय? + +अभिनंदन! आपण नुकतीच _fork -> clone -> edit -> PR_ ही कार्यपद्धती पूर्ण केली आहे ज्यास आपणास एक योगदानकर्ता (Contributor) म्हणून सदैवच तोंड द्यावे लागते! + +आपले योगदान साजरे करा आणि [येथे](https://roshanjossey.github.io/first-contributions/#social-share) जाऊन आपल्या मित्र आणि अनुयायांसह शेअर/सामायिक करा. + +आपल्याला कोणत्याही मदतीची आवश्यकता असल्यास किंवा काही प्रश्न असल्यास आपण आमच्या स्लॅक टीममध्ये सामील होऊ शकता. [स्लॅक टीममध्ये सामील व्हा](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +आता आपण इतर प्रकल्पांमध्येही आपले योगदान देऊ शकता. आपण प्रारंभ करू शकाल अशा सुलभ समस्यांसह (Issues) आम्ही काही प्रोजेक्टची सूची संकलित केली आहे. [येथे वेब अॅप मधील प्रकल्पांची यादी पहा.](https://roshanjossey.github.io/first-contributions/#project-list) + +## इतर साधने वापरण्याबाबतीत ट्युटोरियल + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.mx.md b/translations/README.mx.md new file mode 100644 index 00000000000..67b2714f0a7 --- /dev/null +++ b/translations/README.mx.md @@ -0,0 +1,124 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Primeras contribuciones + +Es complicado. Siempre resulta difícil la primera vez que haces algo. Principalmente cuando colaboras con otros, pues cometer errores no es agradable. Queremos simplificar la forma en la que los nuevos contribuyentes de _open source_ aprenden y contribuyen por primera vez. + +Leer artículos y ver tutoriales puede ayudar, pero ¿Qué mejor que hacer las cosas en un ambiente de prácticas? Este proyecto se enfoca en guiar y en simplificar la forma en la que los principiantes hacen su primera contribución. Si buscas hacer tu primera contribución, sigue los pasos que se muestran a continuación. + +#### *Si no estás cómodo con la línea de comandos, [aquí hay unos tutoriales usando herramientas gráficas.](#Tutoriales-con-otras-herramientas)* + + +fork de este repositorio + +Si no tienes git en tu equipo, aquí las instrucciones para instalarlo en el [enlace]( https://help.github.com/articles/set-up-git/ ) + +## Dale Fork al repositorio + +Dale "fork" a este repositorio dando clic en el botón "*Fork*" en la parte superior derecha de la página. +Esto creará una copia de este repositorio en tu cuenta. + +## Clona "Clone" el repositorio + +clonar este repositorio + +Ahora clona este repositorio en tu equipo. Ve a tu cuenta de Github, y da clic en el botón "*clone or download*" y luego da clic en el ícono para *copiar*. + +Abre tu consola o terminal y ejecuta el siguiente comando: + +``` +git clone "la url del repositorio que copiaste" +``` + +Donde "la url del repositorio que copiaste" (sin las comillas dobles) es la *url* a este repositorio (tu *fork* a este proyecto). Mira los pasos previos para obtener la *url*. + +copiar URL al portapapeles + +Por ejemplo: +``` +git clone https://github.com/usuarioGitHub/first-contributions.git +``` +Donde `usuarioGitHub` es tu usuario de GitHub. Aquí estás copiando los contenidos del repositorio *first-contributions* en GitHub a tu equipo. + +## Crea una rama (*Branch*) + +Cambia al directorio del repositorio en tu equipo (si es que no estás ahí ya). + +``` +cd first-contributions +``` + +Ahora crea una rama (*branch*) usando el comando `git checkout`: +``` +git checkout -b +``` + +Por ejemplo: +``` +git checkout -b add-juan-perez +``` +(El nombre de la rama no tiene porqué contener la palabra *add*, pero es razonable que lo tenga porque el objetivo de esta rama es añadir tu nombre a la lista.) + +## Haz los cambios necesarios y salva (*Commit*) esos cambios + +Abre el archivo `Contributors.md` en un editor de texto y añade tu nombre. No lo añadas ni al principio ni al final del archivo, hazlo en cualquier otro sitio. Guarda el archivo. + +git status + +Si vas al directorio del proyecto y ejecutas el comando `git status`, podrás ver los cambios ya reflejados. + +Agrega esos cambios a la rama (*branch*) que creaste antes usando el comando `git add`: + +``` +git add Contributors.md +``` + +Ahora puedes hacer un *commit* sobre estos cambios ejecutando el comando `git commit`: +``` +git commit -m "Add to Contributors list" +``` +reemplazando `` con tu nombre. + + +## Carga (*Push*) tus cambios a GitHub + +Mandar un *push* de tus cambios usando el comando `git push`: +``` +git push origin +``` +Reemplaza `` con el nombre de la rama que creaste anteriormente. + +## Envía (*Submit*) tus cambios para ser revisados + +Si vas a tu repositorio en GitHub, verás un botón `Compare & pull request`. Haz clic sobre este botón. + +crea una pull request + +Ahora envía el *pull request*. + +enviar la pull request + +Pronto estaré combinando tus cambios (haciendo *merge*) con la rama master de este proyecto. Recibirás una notificación por correo electrónico cuando los cambios hayan sido combinados. + +## ¿Cuáles son los siguientes pasos? + +¡Felicidades! ¡Has completado la línea de trabajo *_fork -> clone -> edit -> PR_* que encontrarás habitualmente como contribuidor! + +Festeja tu contribución y compártela con tus amigos y seguidores yendo a [web app](https://roshanjossey.github.io/first-contributions/#social-share). + +También podrías unirte a nuestro *equipo* de Slack en caso de que necesites ayuda o tengas alguna pregunta. [Únete a nuestro Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Ahora empieza a contribuir a otros proyectos. Hemos reunido una lista de proyectos con *issues* sencillas para que puedas empezar. Échale un ojo a la [lista de proyectos en la web app](https://roshanjossey.github.io/first-contributions/#project-list). + +### [Material adicional](../additional-material/git_workflow_scenarios/additional-material.md) + + +## Tutoriales con otras herramientas + +|GitHub Desktop|Visual Studio 2017|GitKraken|VS Code|Sourcetree App|IntelliJ IDEA| +|---|---|---|---|---|---| +|[GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md)|[Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md)|[GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md)|[Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md)| [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md)|[IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md)| diff --git a/translations/README.my.md b/translations/README.my.md new file mode 100644 index 00000000000..13e562aa27f --- /dev/null +++ b/translations/README.my.md @@ -0,0 +1,121 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Sumbangan Pertama + +Ia sukar. Ia sentiasa sukar buat kali pertama kamu melakukan sesuatu. Terutama apabila kamu berkolaborasi, membuat kesilapan bukan perkara yang selesa. Kami mahu menyederhanakan cara penyumbang sumber terbuka baru belajar & menyumbang buat kali pertama. + +Membaca artikel & menonton tutorial boleh membantu, tetapi apa yang lebih baik daripada melakukan perkara dalam persekitaran yang praktikal? Projek ini bertujuan memberi bimbingan & memudahkan seseorang yang baru bermula untuk membuat sumbangan pertama mereka. Jika kamu ingin membuat sumbangan pertama kamu, ikuti langkah-langkah di bawah. + +#### *Jika anda tidak selesa dengan 'command line', [sini adalah tutorial menggunakan alat GUI.](#Tutorial-Menggunakan-Alat-Lain)* + +fork this repository + +Jika anda tidak mempunyai git dalam mesin kamu, [pasang](https://help.github.com/articles/set-up-git/). + +## Fork repositori ini + +Fork repo ini dengan mengklik butang fork di atas halaman ini. +Ini akan membuat salinan repositori ini dalam akaun kamu. + +## Klon repositori + +clone this repository + +Sekarang klon repo yang bercabang ke mesin kamu. Pergi ke akaun GitHub anda, buka repo yang bercabang, klik pada butang klon dan kemudian klik ikon * copy to clipboard *. + +Buka terminal dan jalankan arahan git berikut: + +``` +git clone "url anda baru disalin" +``` +dimana "url anda baru disalin" (tanpa tanda petikan) adalah url ke repositori ini (fork projek anda). Lihat langkah-langkah sebelumnya untuk mendapatkan url. + +copy URL to clipboard + +Contoh: +``` +git clone https://github.com/this-is-you/first-contributions.git +``` +dimana `this-is-you` adalah nama pengguna GitHub kamu. Di sini kamu menyalin kandungan repositori sumbangan pertama dalam GitHub ke komputer kamu. + +## Membuat cawangan + +Tukar ke direktori repositori pada komputer kamu (jika kamu belum berada disana): + +``` +cd first-contributions +``` +Sekarang cipta cawangan menggunakan arahan `git checkout`: +``` +git checkout -b +``` + +Contoh: +``` +git checkout -b add-alonzo-church +``` +(Nama cawangan tidak perlu mempunyai perkataan * add * di dalamnya, tetapi ia adalah perkara yang munasabah untuk disertakan kerana tujuan cawangan ini adalah untuk menambah nama anda ke senarai.) + +## Buat perubahan yang diperlukan dan komit perubahan tersebut + +Sekarang buka fail `Contributors.md` dalam editor teks, tambahkan nama anda kepadanya. Jangan tambahkannya pada awal atau akhir fail. Letakkan di mana sahaja di antara. Sekarang, simpan fail itu. + +git status + + +Jika anda pergi ke direktori projek dan laksanakan arahan `git status`, kamu akan melihat perubahanya. + +Tambah perubahan tersebut ke cawangan yang baru kamu cipta menggunakan arahan `git add`: + +``` +git add Contributors.md +``` + +Sekarang komit perubahan tersebut menggunakan perintah `git commit`: +``` +git commit -m "Add to Contributors list" +``` +menggantikan `` dengan nama kamu. + +## Push changes to GitHub + +Tolak perubahan anda menggunakan arahan `push push`: +``` +git push origin +``` +menggantikan `` dengan nama cawangan yang kamu cipta sebelumnya. + +## Hantar perubahan anda untuk semakan + +Jika anda pergi ke repositori anda di GitHub, anda akan melihat butang `Compare & pull request`. Klik pada butang itu. + +create a pull request + +Sekarang hantar 'pull request' itu. + +submit pull request + +Tidak lama lagi saya akan menggabungkan semua perubahan anda ke cawangan 'master' projek ini. Anda akan mendapat e-mel pemberitahuan sebaik sahaja perubahan telah digabungkan. + +## Ke mana pergi dari sini? + +Tahniah! Anda baru saja selesai melaksanakan standard _fork -> clone -> edit -> PR_ aliran kerja yang sering kamu akan terserempak sebagai seorang penyumbang! + +Raikan sumbangan kamu dan kongsi dengan rakan dan pengikut kamu dengan pergi ke [aplikasi web](https://roshanjossey.github.io/first-contributions/#social-share). + +Anda boleh menyertai pasukan 'Slack' kami sekiranya anda memerlukan bantuan atau mempunyai sebarang soalan. [Sertai pasukan Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Sekarang mari kita mulakan dengan menyumbang kepada projek lain. Kami telah menyusun senarai projek dengan isu mudah yang boleh anda mulakan. Semak [senarai projek dalam aplikasi web](https://roshanjossey.github.io/first-contributions/#project-list). + +### [Bahan tambahan](../additional-material/git_workflow_scenarios/additional-material.md) + + +## Tutorial Menggunakan Alat Lain + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.nl.md b/translations/README.nl.md new file mode 100644 index 00000000000..8c8fafef5eb --- /dev/null +++ b/translations/README.nl.md @@ -0,0 +1,162 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Eerste bijdragen + +De eerste keer dat je iets nieuws probeert is altijd lastig, helemaal wanneer je samen werkt - kan het maken van fouten erg vervelend zijn. Maar in open-source ontkom je niet aan samenwerken. We willen het graag makkelijker maken om te leren en bij te dragen voor de eerste keer aan een open-source project. + +Het kan helpen om de artikelen te lezen en de video's te bekijken, maar niets is beter dan het gelijk te doen terwijl je leert en je niet de kans hebt om een fout te maken. Dit project richt zich op het begeleiden en het makkelijker maken voor beginners om hun eerste bijdrage te leveren aan een project. Onthoud: Hoe meer ontspannen je bent hoe beter je leert. Indien je op zoek bent om je eerste bijdrage te leveren aan open-source volg dan de onderstaande stappen. Wij beloven dat je het leuk zal vinden xxxx. + +fork deze repository + +Indien je git nog niet hebt op je systeem, [ installeer het dan eerst ](https://help.github.com/articles/set-up-git/) + +## Deze repository forken + +Fork deze repository door op de fork knop te klikken. Dit creëert een kopie van deze repository in jouw account. + +## De repository clonen + +kloon deze repository + +Kloon nu deze repository naar je systeem. Klik op de kloon knop en dan op het kopiëren naar klembord icoon. + +Open een terminal en voer het volgende git commando uit: + +``` +git clone "Gekopieerde repository" +``` + +Waar "Gekopieerde repository" (zonder aanhalingstekens) de url naar (jouw fork van) deze repository is. Zie de vorige stappen om de url te vinden. + +kopieer URL naar het klembord + +Bijvoorbeeld: + +``` +git clone https://github.com/this-is-you/first-contributions.git +``` + +Waar 'this-is-you' staat vul jij je GitHub gebruikersnaam is. Hiermee kopieer je de inhoud van de first-contributions repo op GitHub naar je systeem. + +## Een branch aanmaken + +Navigeer naar de map van de repository op je systeem (mocht je daar niet al zijn). + +``` +cd first-contributions +``` + +Maak nu een branch aan door middel van het `git checkout command` + +``` +git checkout -b +``` + +Bijvoorbeeld: + +``` +git checkout -b add-thibmaek +``` + +(De naam van de branch hoeft niet het woord _add_ te bevatten. In dit voorbeeld is het wel te adviseren aangezien het doel van deze branch hiermee duidelijk wordt gemaakt.) + +## Maak de benodigde wijzigingen en commit deze + +Open nu het `Contributors.md` bestand in een teksteditor en voeg je naam toe. Doe dit niet aan het begin of eind, maar ergens in het midden. Sla vervolgens het bestand op. + +Als je naar de projectmap gaat en `git status` doet, zul je zien dat er wijzigingen zijn. Voeg deze toe aan je branch met behulp van onderstaand `git add` commando. + +``` +git add Contributors.md +``` + +Commit nu deze wijzigingen door onderstaand `git commit` commando te gebruiken. + +``` +git commit -m "Add to Contributors list" +``` + +vervang `` met jouw naam + +## Push de wijzigingen naar GitHub + +Push je wijzigingen met `git push` + +``` +git push origin +``` + +Vervang `` met de naam van de branch die je eerder aanmaakte. + +## Verstuur je wijzigingen voor review + +Als je naar je repository gaat op GitHub, zal je zien dat er een `Compare & pull request` knop staat. Klik hierop. + +creëer een pull request + +Verstuur nu je pull request. + +verstuur je pull request + +Nu ga ik (de beheerder) al je wijzigingen mergen in de master branch van dit project. Als de veranderingen gemerged zijn, zul je hier een e-mailnotificatie over ontvangen. + +## Je fork in sync houden met de hoofd-repository + +Wanneer de pull request wordt geaccepteerd en gemerged, zal jouw fork de wijzigingen nog niet bevatten - hiervoor moet je nog een aantal extra stappen ondernemen. + +Om beide repo's met elkaar in sync te houden voeg je de hoofd repo (mijne) url in als `upstream remote url`. + +``` +git remote add upstream https://github.com/firstcontributions/first-contributions +``` + +Hiermee vertel je git dat er nog een andere versie van dit project bestaat op dit specifieke url punt en dat we het upstream zullen noemen. Wanneer de wijzigingen gemerged zijn, kun je de nieuwe versie ophalen (fetchen) van mijn repo. + +``` +git fetch upstream +``` + +Hiermee fetchen we alle wijzigingen in mijn fork (upstream remote). Nu zal je de nieuwe revisie/versie van mijn repo moeten mergen in jouw master branch. + +``` +git rebase upstream/master +``` + +Dit voegt alle wijzigingen toe die je net fetchte van de master branch. Als je nu probeert je master branch te pushen, zal je fork al deze wijzigingen ook bevatten. + +``` +git push origin master +``` + +Merk op dat je in dit geval pusht naar de remote met de naam origin. + +## Tutorials gebruiken Andere hulpmiddelen + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + +## Hoe nu verder? + +Gefeliciteerd! Je hebt zojuist de standaard _fork -> clone -> edit -> PR_ workflow doorlopen die je vaak zult tegenkomen als bijdrager! + +Vier je bijdrage en deel het met je vrienden en volgers via de [web app](https://roshanjossey.github.io/first-contributions/#social-share). + +Mocht je nog vragen of hulp nodig hebben dan kun je je aanmelden voor ons [Slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Laten we je nu op weg helpen met het bijdragen aan andere projecten. We hebben een lijst samengesteld met projecten die makkelijke issues bevatten waar je aan kunt werken. Bekijk [de lijst op de web app](https://roshanjossey.github.io/first-contributions/#project-list) + +Hier zijn enkele beginner-level issues in populaire repos die je kan proberen oplossen. Ga verder naar deze repos om meer te lezen. + +| [![exercism](https://avatars2.githubusercontent.com/u/5624255?v=3&s=100)](https://github.com/exercism/exercism.io/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+patch%22) | [![fun-retro](https://avatars3.githubusercontent.com/u/15913975?v=3&s=100)](https://github.com/funretro/distributed/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly) | [](https://github.com/facebook/react/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+bug%22) | [![habitat](https://avatars1.githubusercontent.com/u/18171698?v=3&s=100)](https://github.com/habitat-sh/habitat/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [![scikit-learn](https://avatars0.githubusercontent.com/u/365630?v=3&s=100)](https://github.com/scikit-learn/scikit-learn/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [](https://github.com/technomancy/leiningen/issues?q=is%3Aopen+is%3Aissue+label%3ANewbie) | [](https://github.com/numpy/numpy/issues?q=is%3Aopen+is%3Aissue+label%3A%22Easy+Fix%22) | [![elasticsearch](https://avatars2.githubusercontent.com/u/6764390?v=3&s=100)](https://github.com/elastic/elasticsearch/issues?q=is%3Aopen+is%3Aissue+label%3A%22low+hanging+fruit%22) | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [exercism](https://github.com/exercism/exercism.io/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+patch%22) | [Fun Retros](https://github.com/funretro/distributed/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly) | [react](https://github.com/facebook/react/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+bug%22) | [habitat](https://github.com/habitat-sh/habitat/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [scikit-learn](https://github.com/scikit-learn/scikit-learn/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [Leiningen](https://github.com/technomancy/leiningen/issues?q=is%3Aopen+is%3Aissue+label%3ANewbie) | [numpy](https://github.com/numpy/numpy/issues?q=is%3Aopen+is%3Aissue+label%3A%22Easy+Fix%22) | [elasticsearch](https://github.com/elastic/elasticsearch/issues?q=is%3Aopen+is%3Aissue+label%3A%22low+hanging+fruit%22) | +| [![homebrew](https://avatars2.githubusercontent.com/u/1503512?v=3&s=100)](https://github.com/Homebrew/brew/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) | [![rust](https://avatars1.githubusercontent.com/u/5430905?v=3&s=100)](https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Aissue+label%3AE-easy) | [![vuejs](https://avatars1.githubusercontent.com/u/6128107?v=3&s=100)](https://github.com/vuejs/vue/issues?q=is%3Aopen+is%3Aissue+label%3A%22contribution+welcome%22) | [![Suave](https://avatars2.githubusercontent.com/u/5822862?v=3&s=100)](https://github.com/SuaveIO/suave/issues?q=is%3Aopen+is%3Aissue+label%3Ahardness-easy) | [![OpenRA](https://avatars3.githubusercontent.com/u/409046?v=3&s=100)](https://github.com/OpenRA/OpenRA/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [![PowerShell](https://avatars0.githubusercontent.com/u/11524380?v=3&s=100)](https://github.com/powershell/powershell/issues?q=is%3Aopen+is%3Aissue+label%3AUp-for-Grabs) | [![coala](https://avatars2.githubusercontent.com/u/10620750?v=3&s=100)](https://github.com/coala/coala/issues?q=is%3Aopen+is%3Aissue+label%3Adifficulty%2Flow+label%3Adifficulty%2Fnewcomer) | [![moment](https://avatars2.githubusercontent.com/u/4129662?v=3&s=100)](https://github.com/moment/moment/issues?q=is%3Aopen+is%3Aissue+label%3AUp-For-Grabs) | +| [homebrew](https://github.com/Homebrew/brew/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) | [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Aissue+label%3AE-easy) | [vuejs](https://github.com/vuejs/vue/issues?q=is%3Aopen+is%3Aissue+label%3A%22contribution+welcome%22) | [Suave](https://github.com/SuaveIO/suave/issues?q=is%3Aopen+is%3Aissue+label%3Ahardness-easy) | [OpenRA](https://github.com/OpenRA/OpenRA/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [PowerShell](https://github.com/powershell/powershell/issues?q=is%3Aopen+is%3Aissue+label%3AUp-for-Grabs) | [coala](https://github.com/coala/coala/issues?q=is%3Aopen+is%3Aissue+label%3Adifficulty%2Flow+label%3Adifficulty%2Fnewcomer) | [moment](https://github.com/moment/moment/issues?q=is%3Aopen+is%3Aissue+label%3AUp-For-Grabs) | +| [![ava](https://avatars0.githubusercontent.com/u/8527916?v=3&s=100)](https://github.com/avajs/ava/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+for+beginner%22) | [![freeCodeCamp](https://avatars0.githubusercontent.com/u/9892522?v=3&s=100)](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only) | [![webpack](https://avatars3.githubusercontent.com/u/2105791?v=3&s=100)](https://github.com/webpack/webpack/issues?q=is%3Aopen+is%3Aissue+label%3A%22D1%3A+Easy+%28Contrib.+Difficulty%29%22) | [![hoodie](https://avatars1.githubusercontent.com/u/1888826?v=3&s=100)](https://github.com/hoodiehq/hoodie/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only) | [![pouchdb](https://avatars3.githubusercontent.com/u/3406112?v=3&s=100)](https://github.com/pouchdb/pouchdb/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) | [![neovim](https://avatars0.githubusercontent.com/u/6471485?v=3&s=100)](https://github.com/neovim/neovim/issues?q=is%3Aopen+is%3Aissue+label%3Aentry-level) | [![babel](https://avatars2.githubusercontent.com/u/9637642?v=3&s=100)](https://github.com/babel/babel/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly) | [](https://github.com/adobe/brackets/labels/Starter%20bug) | +| [ava](https://github.com/avajs/ava/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+for+beginner%22) | [freeCodeCamp](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only) | [webpack](https://github.com/webpack/webpack/issues?q=is%3Aopen+is%3Aissue+label%3A%22D1%3A+Easy+%28Contrib.+Difficulty%29%22) | [hoodie](https://github.com/hoodiehq/hoodie/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only) | [pouchdb](https://github.com/pouchdb/pouchdb/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) | [neovim](https://github.com/neovim/neovim/issues?q=is%3Aopen+is%3Aissue+label%3Aentry-level) | [babel](https://github.com/babel/babel/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly) | [brackets](https://github.com/adobe/brackets/labels/Starter%20bug) | +| [![Node.js](https://avatars1.githubusercontent.com/u/9950313?v=3&s=100)](https://github.com/nodejs/node/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22) | [](https://github.com/Semantic-Org/Semantic-UI-React/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22) | +| [Node.js](https://github.com/nodejs/node/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22) | [Semantic-UI-React](https://github.com/Semantic-Org/Semantic-UI-React/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22) | diff --git a/translations/README.no.md b/translations/README.no.md new file mode 100644 index 00000000000..eaf59befcc9 --- /dev/null +++ b/translations/README.no.md @@ -0,0 +1,129 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Første bidrag + +Det er alltid vanskelig å gjøre noe for første gang. Spesielt når man samarbeider med andre kan det være tungt å gjøre feil. Vi ønsker å gjøre det lettere for nybegynnere å bidra til open-source. + +Å lese artikler og se videoer kan hjelpe, men hva kan vel være bedre enn å gjøre det i praksis? Dette prosjektet håper å kunne tilby en enkel veiledning og gjøre det lett for nybegynnere å gi sitt første bidrag. Følg trinnene nedenfor hvis du ønsker å gi ditt første bidrag til dette prosjektet. + +#### _Hvis du ikke er komfortabel med terminal, [så finnes det andre metoder](#Veiledning-for-andre-verktøy)._ + + +fork this repository + +Om du ikke har git installert på din maskin, [følg denne veiledningen](https://help.github.com/articles/set-up-git/). + +## Fork dette prosjektet + +Fork prosjektet ved å klikke på "fork" knappen på toppen av denne siden. Dette vil legge til en kopi av dette prosjektet til din GitHub konto (prosjekter kalles repository på GitHub). + +## Clone prosjektet + +clone this repository + +Nå skal vi klone prosjektet fra GitHub til din maskin. Gå til din GitHub konto og åpne din nye fork, deretter klikk på "clone" knappen og kopier linken. + +Åpne en terminal/kommandolinje og kjør følgende git kommando: + +``` +git clone +``` + +Erstatt `` med linken du kopierte i forrige trinn. + +
copy URL to clipboard + +Eksempel: + +``` +git clone https://github.com/ditt-brukernavn/first-contributions.git +``` + +hvor `ditt-brukernavn` er ditt GitHub brukernavn. Her kopierer vi innholdet i first-contributions prosjektet fra din GitHub konto til din lokale maskin. + +## Opprett en branch + +Naviger terminalen inn i prosjektet (hvis du ikke er der allerede): + +``` +cd first-contributions +``` + +Opprett en branch med `git checkout` kommandoen: + +``` +git checkout -b +``` + +Eksempel: + +``` +git checkout -b add-alonzo-church +``` + +Navnet på din branch behøver ikke å inneholde ordet _add_, men det gir mening å inkludere det i denne sammenhengen. Endre "alonzo-church" til ditt navn. + +## Lag endringer og commit dem + +Åpne filen `Contributors.md` i et program for å redigere tekst og legg til ditt navn i listen. Ikke legg det til i begynnelsen eller slutten av filen, legg det til hvor som helst i mellom. Når du har gjort dette kan du lagre filen. + +git status + +Hvis du åpner terminalen igjen og kjører kommandoen `git status`, vil du se dine endringer. + +Legg endringene til i din nye branch med kommandoen `git add`: + +``` +git add Contributors.md +``` + +Commit endringene med kommandoen `git commit`: + +``` +git commit -m "Add to Contributors list" +``` + +Erstatt `` med ditt navn. + +## Push endringene til GitHub + +Push til GitHub med kommandoen `git push`: + +``` +git push origin +``` + +Erstatt `` med navnet på branch som du opprettet tidligere. + +## Send inn endringene for gjennomgang + +Hvis du går til ditt prosjekt på GitHub, vil du se en `Compare & pull request` knapp. Klikk på den for å opprette en pull request. + +create a pull request + +Send inn din pull request når du er klar. + +submit pull request + +Snart vil jeg merge dine endringer inn i master branch av mitt prosjekt. Du vil motta en notifikasjon på epost når dine endringer er lagt til. + +## Hva nå? + +Gratulerer! Du har gjennomført standardprosessen for _fork -> clone -> edit -> PR_, en prosess du vil møte på ofte! + +Feir ditt bidrag og del det med dine venner og følgere ved å gå til [web app](https://firstcontributions.github.io/#social-share). + +Behøver du hjelp eller vil stille spørsmål så kan du bli med i vår slack-gruppe. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Nå kan du gå videre og bidra til andre open-source prosjekter. Vi har satt sammen en liste med enkle og overkommelige problemer du kan starte med. Sjekk den ut her: [the list of projects in the web app](https://firstcontributions.github.io/#project-list). + +### [Ekstramateriale](../additional-material/git_workflow_scenarios/additional-material.md) + +## Veiledning for andre verktøy + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.np.md b/translations/README.np.md new file mode 100644 index 00000000000..a740635d52c --- /dev/null +++ b/translations/README.np.md @@ -0,0 +1,117 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# पहिलो योगदान +यस प्रोजेक्टले शुरुवातकर्ताहरूले आफ्नो पहिलो योगदान गर्ने तरिकालाई सरल बनाउने र मार्गदर्शन गर्ने लक्ष्य राखेको छ। यदि तपाईं आफ्नो पहिलो योगदान गर्न खोज्दै हुनुहुन्छ भने, तलका चरणहरू पालना गर्नुहोस्। + +यदि तपाईं कमाण्ड कमांड लाइन (command line) सँग सहज हुनुहुन्न भने, [यहाँ GUI तूल्सहरू प्रयोग गरेर सेकैएको ट्यूटोरियलहरू छन्।](#ट्यूटोरियलहरू-अन्य-उपकरणहरू-प्रयोग-गर्दै) + +यो अन्य [भाषाहरूमा](Translations.md) पढ्नुहोस्। + +यो भण्डार फोर्क गर्नुहोस। + +यदि तपाईंसँग तपाइँको कम्प्यूटरमा Git छैन, [यसलाई इन्स्टल गर्नुहोस्।]( https://help.github.com/articles/set-up-git/) + +## यो रिपो फोर्क गर्नुहोस +यस पृष्ठको शीर्षमा फोर्क बटनमा क्लिक गरेर यो रिपो फोर्क गर्नुहोस। यसले तपाईंको GitHub खातामा यस रिपोको प्रतिलिपि सिर्जना गर्नेछ। + +## रिपो क्लोन गर्नुहोस् + +यो भण्डारलाई क्लोन गर्नुहोस् + +अब तपाइँको कम्प्यूटरमा फोर्क गरिएको रिपो क्लोन गर्नुहोस। तपाईंको GitHub खातामा जानुहोस्, फोर्क गरिएको रिपो खोल्नुहोस्, क्लोन बटनमा क्लिक गर्नुहोस् र त्यसपछि *copy to clipboard* आइकनमा क्लिक गर्नुहोस्। + +टर्मिनल खोल्नुहोस् र निम्न Git कमाण्ड चलाउनुहोस्: + +``` +git clone "तपाईंले भर्खरै प्रतिलिपि गर्नुभएको URL" +``` +जहाँ "तपाईंले भर्खरै प्रतिलिपि गर्नुभएको URL" (" चिन्हहरू बिना) छ, त्यो यस रिपोको url हो (यस प्रोजेक्टको लागी तपाईंको फोर्क)। Url प्राप्त गर्न अघिल्लो चरण हेर्नुहोस्। + +URL लाई क्लिपबोर्डमा प्रतिलिपि बनाउनुहोस् + +उदाहरणका लागि: +``` +git clone https://github.com/this-is-you/first-contributions.git +``` +जहाँ `this-is-you` छ, त्यहाँ तपाईंको GitHub प्रयोगकर्ता नाम (GitHub username) लेख्नुहोस् । यहाँ तपाइँले GitHub बाट तपाईंको कम्प्युटरमा first-contributions रिपोको सामग्री प्रतिलिपि गर्दै हुनुहुन्छ। + +## एउटा ब्रांच बनाउनुहोस् + +तपाईंको कम्प्यूटरमा रिपोको डाइरेक्टरी खोल्नुहोस् (यदि तपाईं पहिले नै हुनुहुन्न भने): + +``` +cd first-contributions +``` +अब `git checkout` कमाण्ड प्रयोग गरेर एउटा ब्रन्च सिर्जना गर्नुहोस्: +``` +git checkout -b <ब्रन्चको-नाम> +``` +उदाहरणको लागि: +``` +git checkout -b add-alonzo-church +``` +(ब्रन्च को नाममा *add* शब्द को आवश्यकता छैन, तर यसमा add समावेश गर्न उचित छ किनभने यस ब्रन्चको उद्देश्य तपाईंको नामलाई सूचीमा थप्ने हो।) + +## आवश्यक परिवर्तनहरू गर्नुहोस् र ती परिवर्तनहरू कोम्मित गर्नुहोस् + +अब टेक्स्ट एडिटओरमा (text editor) `Contributors.md` फाइल खोल्नुहोस्, यसमा तपाईंको नाम थप्नुहोस्। फाइलको सुरुवात वा अन्त्यमा तपाईंको नाम नथप्नुहोस्। तपाईंको नामलाई बीचमा राख्नुहोस्। अब फाईल save गर्नुहोस्। + +git status + + +यदि तपाईं प्रोजेक्ट डाइरेक्टरीमा जानुभयो र `git status` कमाण्डलाई रन (run) गर्नुभयो भने,तपाइँले त्यहाँ परिवर्तन भएका फाइलहरुको सुची देख्नुहुनेछ। + +तपाईँले भर्खरै बनाउनु भएको ब्रन्चमा `git add` कमाण्ड प्रयोग गरी ती परिवर्तनहरू थप्नुहोस्: + +``` +git add Contributors.md +``` + +अब `git commit` कमाण्ड प्रयोग गरेर ती परिवर्तनहरू कोम्मित (commit) गर्नुहोस्: +``` +git commit -m "योगदान सूचीमा <तपाइको-नाम> थप गर्नुहोस्" +``` + +`<तपाईंको-नाम>` को साटोमा तपाईंको आफ्नो नाम लेख्नुहोस्। + +## GitHub मा परिवर्तन पुश गर्नुहोस + +`git push` कमाण्डको प्रयोग गरेर आफ्नो परिवर्तन पुश (push) गर्नुहोस्: +``` +git push origin <ब्रांचको-नाम> +``` +`<ब्रांचको-नाम>` को साटोमा तपाईले पहिले सिर्जना गर्नुभएको ब्रांचको नामको लेख्नुहोस्। + +## रिभ्युको लागि तपाईंको परिवर्तनहरू पेश गर्नुहोस् + +यदि तपाईं GitHub मा तपाईंको रेपोसितोरीमा (repository) जानुहुन्छ भने, तपाइँले `compare & pull request` बटन देख्नुहुनेछ। त्यस बटनमा क्लिक गर्नुहोस्। + +एउटा पुल अनुरोध सिर्जना गर्नुहोस् + +अब pull request सब्मित गर्नुहोस्। + +submit pull request + +चाँडै म यस प्रोजेक्टको मास्टर ब्रन्चमा तपाईका सबै परिवर्तनहरू मर्ज गर्नेछु। परिवर्तनहरू मर्ज भएपछि एक अधिसूचना (notification) इमेल प्राप्त गर्नुहुनेछ। + +## यहाँबाट कहाँ जाने? + +बधाई छ! तपाईले फोर्क -> क्लोन -> एडिट -> पुल्ल रिक्वेस्ट कार्यनोयन पूरा गर्नुभयो, जुन तपाई प्राय: एक योगदानकर्ताको रूपमा गर्नुहुनेछ! + +तपाईंले योगदान दिनु भएकोमा खुशी मनाउनुहोस् र आफ्नो साथी र फोल्लोवेरहरू माझ शेयर गर्नुहोस्। [वेब अनुप्रयोग](https://roshanjossey.github.io/first-contributions/#social-share) + +तपाइँलाई कुनै पनि मद्दत चाहिन्छ वा कुनै प्रश्न छ भने तपाइँ हाम्रो स्लाक टीममा (slack team) सामेल हुन सक्नुहुनेछ। [स्लाक टोलीमा सामेल हुनुहोस्](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +अब तपाईले अन्य प्रोजेक्टहरूमा योगदान दिन सुरु गर्नुहोस्। हामीले तपाईंले गर्न सक्नुहुने सजिलो समस्याहरूको साथमा प्रोजेक्टहरूको सूची संकलन गरेका छौ। हेर्नुहोस् [वेब अनुप्रयोगमा परियोजनाहरूको सूची](https://roshanjossey.github.io/first-contributions/#project-list)। + +### [थप सामग्री](../additional-material/git_workflow_scenarios/additional-material.md) + +## ट्यूटोरियलहरू अन्य उपकरणहरू प्रयोग गर्दै + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + diff --git a/translations/README.pb.md b/translations/README.pb.md new file mode 100644 index 00000000000..f2bcec33de7 --- /dev/null +++ b/translations/README.pb.md @@ -0,0 +1,117 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) + +# ਪਹਿਲਾ ਯੋਗਦਾਨ + +ਇਸ ਪ੍ਰੋਜੈਕਟ ਦਾ ਉਦੇਸ਼ ਸ਼ੁਰੂਆਤੀ ਲੋਕਾਂ ਦਾ ਆਪਣਾ ਪਹਿਲਾ ਯੋਗਦਾਨ ਪਾਉਣ ਦੇ ਕਮ ਨੂੰ ਸਰਲ ਬਣਾਉਣ ਅਤੇ ਮਾਰਗਦਰਸ਼ਨ ਕਰਨਾ ਹੈ। ਜੇ ਤੁਸੀਂ ਆਪਣਾ ਪਹਿਲਾ ਯੋਗਦਾਨ ਪਾਉਣ ਦੀ ਕੋਸ਼ਿਸ਼ ਕਰ ਰਹੇ ਹੋ, ਤਾਂ ਹੇਠਾਂ ਦਿੱਤੇ ਕਦਮਾਂ ਦੀ ਪਾਲਣਾ ਕਰੋ। +ਜੇ ਤੁਸੀਂ ਕਮਾਂਡ ਲਾਈਨ ਨਾਲ ਸੁਖੀ ਨਹੀਂ ਹੋ, [ਇੱਥੇ ਜੀ.ਯੁ.ਆੀ ਟੂਲਸ ਦੀ ਵਰਤੋਂ ਕਰਨ ਦਿਆਂ ਟੁਟੋਰਿਅਲਸ ਹਨ.](#ਹੋਰ-ਟੂਲਜ-ਦੀ-ਵਰਤੋਂ-ਕਰਦਿਆਂ-ਟੁਟੋਰਿਅਲ) + +fork this repository + +#### ਜੇ ਤੁਹਾਡੀ ਮਸ਼ੀਨ ਤੇ ਗਿੱਟ ਨਹੀਂ ਹੈ, [ਇਸ ਨੂੰ ਇੰਸਟਾਲ ਕਰੋ](https://help.github.com/articles/set-up-git/)। + +## ਇਸ ਰਿਪੋਜ਼ਟਰੀ ਨੂੰ ਫੋਰਕ ਕਰੋ +ਇਸ ਪੰਨੇ ਦੇ ਸਿਖਰ ਤੇ 'ਫੋਰਕ ਬਟਨ' ਤੇ ਕਲਿੱਕ ਕਰਕੇ ਇਸ ਰਿਪੋਜ਼ਟਰੀ ਨੂੰ ਫੋਰਕ ਕਰੋ. ਇਹ ਤੁਹਾਡੇ ਖਾਤੇ ਵਿੱਚ ਇਸ ਰਿਪੋਜ਼ਟਰੀ ਦੀ ਇੱਕ ਕਾਪੀ ਬਣਾਏਗਾ. + +## ਰਿਪੋਜ਼ਟਰੀ ਨੂੰ ਕਲੋਨ ਕਰੋ +clone this repository + +ਹੁਣ ਆਪਣੀ ਮਸ਼ੀਨ ਤੇ ਫੋਰਕਡ ਰਿਪੋਜ਼ਟਰੀ ਦਾ ਕਲੋਨ ਕਰੋ। ਆਪਣੇ ਗਿਟ-ਹਬ ਅਕਾਉਂਟ ਤੇ ਜਾਓ, ਫੋਰਕਡ ਰਿਪੋਜ਼ਟਰੀ ਖੋਲ੍ਹੋ, ਕੋਡ ਬਟਨ ਤੇ ਕਲਿਕ ਕਰੋ ਅਤੇ ਫਿਰ ਕਲਿੱਪਬੋਰਡ ਆਈਕਨ ਤੇ ਕਾਪੀ ਕਲਿੱਕ ਕਰੋ. +ਇੱਕ ਟਰਮੀਨਲ ਖੋਲ੍ਹੋ ਅਤੇ ਹੇਠਲੀ ਗਿਟ ਕਮਾਂਡ ਚਲਾਓ: + +``` +git clone "ਯੂ.ਆਰ.ਐਲ ਜੇੈਕਰ ਤੁਸੀਂ ਹੁਣੇ ਨਕਲ ਕੀਤੀ" +``` + +ਜਿੱਥੇ “ਯੂ.ਆਰ.ਐਲ ਜੇੈਕਰ ਤੁਸੀਂ ਹੁਣੇ ਨਕਲ ਕੀਤੀ” (ਹਵਾਲਾ ਨਿਸ਼ਾਨਾਂ ਤੋਂ ਬਿਨਾਂ) ਇਸ ਰਿਪੋਜ਼ਟਰੀ ਦਾ ਯੂ.ਆਰ.ਐਲ ਹੈ (ਇਸ ਪ੍ਰੋਜੈਕਟ ਦਾ ਤੁਹਾਡਾ ਫੋਰਕ)। ਯੂ.ਆਰ.ਐਲ ਪ੍ਰਾਪਤ ਕਰਨ ਲਈ ਪਿਛਲੇ ਕਦਮ ਵੇਖੋ। +copy URL to clipboard + +ਉਦਾਹਰਣ ਲਈ: +``` +git clone https://github.com/this-is-you/first-contributions.git +``` + +ਜਿੱਥੇ `this-is-you` ਤੁਹਾਡਾ ਗਿਟ-ਹਬ ਉਪਯੋਗਕਰਤਾ ਨਾਮ ਹੈ। ਇੱਥੇ ਤੁਸੀਂ ਆਪਣੇ ਕੰਪਿਊਟਰ ਤੇ ਗਿਟ-ਹਬ ਉੱਤੇ ਪਹਿਲੇ-ਯੋਗਦਾਨ ਰਿਪੋਜ਼ਟਰੀ ਦੇ ਭਾਗਾਂ ਦੀ ਨਕਲ ਕਰ ਰਹੇ ਹੋ. + +## ਇੱਕ ਸ਼ਾਖਾ ਬਣਾਓ +ਆਪਣੇ ਕੰਪਿਊਟਰ ਉੱਤੇ ਰਿਪੋਜ਼ਟਰੀ ਡਾਇਰੈਕਟਰੀ ਵਿੱਚ ਬਦਲੋ (ਜੇ ਤੁਸੀਂ ਪਹਿਲਾਂ ਤੋਂ ਨਹੀਂ ਹੋ): + +``` +cd first-contributions +``` + +ਹੁਣ `git checkout` ਕਮਾਂਡ ਦੀ ਵਰਤੋਂ ਕਰਕੇ ਸ਼ਾਖਾ ਬਣਾਓ: + +``` +git checkout -b ਤੁਹਾਡਾ-ਨਵੀਂ-ਸ਼ਾਖਾ-ਦਾ-ਨਾਮ +``` + +ਉਦਾਹਰਣ ਲਈ: + +``` +git checkout -b add-alonzo-church +``` + +(ਸ਼ਾਖਾ ਦੇ ਨਾਮ ਨੂੰ ਇਸ ਵਿਚ _add_ ਸ਼ਬਦ ਦੀ ਜ਼ਰੂਰਤ ਨਹੀਂ ਹੈ, ਪਰ ਇਹ ਸ਼ਾਮਲ ਕਰਨਾ ਇਕ ਵਾਜਬ ਚੀਜ਼ ਹੈ ਕਿਉਂਕਿ ਇਸ ਸ਼ਾਖਾ ਦਾ ਉਦੇਸ਼ ਤੁਹਾਡੇ ਨਾਮ ਨੂੰ ਇਕ ਸੂਚੀ ਵਿਚ ਸ਼ਾਮਲ ਕਰਨਾ ਹੈ.) + +## ਜ਼ਰੂਰੀ ਤਬਦੀਲੀਆਂ ਕਰੋ ਅਤੇ ਉਨ੍ਹਾਂ ਬਦਲਾਵਾਂ ਨੂੰ ਪ੍ਰਤੀਬੱਧ ਕਰੋ +ਹੁਣ ਟੈਕਸਟ ਐਡੀਟਰ ਵਿੱਚ `Contributors.md` ਫਾਈਲ ਖੋਲ੍ਹੋ, ਇਸ ਵਿੱਚ ਆਪਣਾ ਨਾਮ ਸ਼ਾਮਲ ਕਰੋ. ਇਸ ਨੂੰ ਫਾਈਲ ਦੇ ਸ਼ੁਰੂ ਜਾਂ ਅੰਤ 'ਤੇ ਨਾ ਸ਼ਾਮਲ ਕਰੋ. ਇਸ ਨੂੰ ਕਿਤੇ ਵੀ ਵਿਚਕਾਰ ਰੱਖੋ। ਹੁਣ, ਫਾਈਲ ਸੇਵ ਕਰੋ। + +git status + +ਜੇ ਤੁਸੀਂ ਪ੍ਰੋਜੈਕਟ ਡਾਇਰੈਕਟਰੀ ਤੇ ਜਾਂਦੇ ਹੋ ਅਤੇ `git status` ਕਮਾਂਡ ਚਲਾਉਂਦੇ ਹੋ, ਤਾਂ ਤੁਸੀਂ ਦੇਖੋਗੇ ਕਿ ਬਦਲਾਅ ਹਨ। + +ਸ਼ਾਖਾ ਵਿੱਚ ਉਹ ਬਦਲਾਵ ਸ਼ਾਮਲ ਕਰੋ ਜੋ ਤੁਸੀਂ ਹੁਣੇ ਬਣਾਇਆ `git add` ਕਮਾਂਡ ਦੀ ਵਰਤੋਂ ਕਰਕੇ ਬਣਾਈ ਹੈ: + +``` +git add Contributors.md +``` + +ਹੁਣ ਉਹ ਤਬਦੀਲੀਆਂ `git ਕਮਿ`` ਕਮਾਂਡ ਦੀ ਵਰਤੋਂ ਨਾਲ ਕਰੋ: + +``` +git commit -m "Add to Contributors list" +``` + +ਤੁਹਾਡੇ ਨਾਮ ਨਾਲ `<ਤੁਹਾਡੇ ਆਪਣੇ ਨਾਮ> rep ਨੂੰ ਬਦਲਣਾ. + +## GitHub ਵਿੱਚ ਬਦਲੋ ਧੱਕੋ + +ਕਮਾਂਡ `git push` ਦੀ ਵਰਤੋਂ ਕਰਕੇ ਆਪਣੀਆਂ ਤਬਦੀਲੀਆਂ ਧੱਕੋ: + +``` +git push origin +``` + +ਉਸ ਬ੍ਰਾਂਚ ਦੇ ਨਾਮ ਨਾਲ ` la ਨੂੰ ਬਦਲਣਾ ਜੋ ਤੁਸੀਂ ਪਹਿਲਾਂ ਬਣਾਈ ਸੀ. + +## ਆਪਣੀਆਂ ਤਬਦੀਲੀਆਂ ਨੂੰ ਸਮੀਖਿਆ ਲਈ ਦਰਜ ਕਰੋ + +ਜੇ ਤੁਸੀਂ ਗਿੱਟਹੱਬ 'ਤੇ ਆਪਣੀ ਰਿਪੋਜ਼ਟਰੀ' ਤੇ ਜਾਂਦੇ ਹੋ, ਤਾਂ ਤੁਸੀਂ `ਤੁਲਨਾ ਕਰੋ ਅਤੇ ਖਿੱਚੋ ਬੇਨਤੀ` ਬਟਨ ਨੂੰ ਵੇਖੋਗੇ. ਉਸ ਬਟਨ 'ਤੇ ਕਲਿੱਕ ਕਰੋ. + +create a pull request + +ਹੁਣ ਪੁਲੀ ਬੇਨਤੀ ਨੂੰ ਜਮ੍ਹਾ ਕਰੋ. + +submit pull request + +ਜਲਦੀ ਹੀ ਮੈਂ ਤੁਹਾਡੀਆਂ ਸਾਰੀਆਂ ਤਬਦੀਲੀਆਂ ਨੂੰ ਇਸ ਪ੍ਰੋਜੈਕਟ ਦੀ ਮਾਸਟਰ ਬ੍ਰਾਂਚ ਵਿੱਚ ਮਿਲਾ ਦੇਵਾਂਗਾ. ਇਕ ਵਾਰ ਤਬਦੀਲੀਆਂ ਨੂੰ ਮਿਲਾਉਣ ਤੋਂ ਬਾਅਦ ਤੁਹਾਨੂੰ ਇਕ ਸੂਚਨਾ ਈਮੇਲ ਮਿਲੇਗੀ. + +## ਇਥੋਂ ਕਿੱਥੇ ਜਾਣਾ ਹੈ? + +ਵਧਾਈਆਂ! ਤੁਸੀਂ ਹੁਣੇ ਹੀ ਸਟੈਂਡਰਡ _ਫੋਰਕ -> ਕਲੋਨ -> ਐਡਿਟ -> ਖਿੱਚ ਬੇਨਤੀ_ ਵਰਕਫਲੋ ਪੂਰਾ ਕੀਤਾ ਹੈ ਜਿਸਦਾ ਤੁਸੀਂ ਅਕਸਰ ਇੱਕ ਯੋਗਦਾਨ ਪਾਉਣ ਵਾਲੇ ਦੇ ਰੂਪ ਵਿੱਚ ਸਾਹਮਣਾ ਕਰੋਗੇ! + +ਆਪਣੇ ਯੋਗਦਾਨ ਦਾ ਜਸ਼ਨ ਮਨਾਓ ਅਤੇ ਜਾ ਕੇ ਇਸ ਨੂੰ ਆਪਣੇ ਦੋਸਤਾਂ ਅਤੇ ਪੈਰੋਕਾਰਾਂ ਨਾਲ ਸਾਂਝਾ ਕਰੋ। [ਵੈੱਬ ਐਪ](https://firstcontributions.github.io/#social-share). + +ਤੁਹਾਨੂੰ ਸਾਡੀ ਸਲੈਕ ਟੀਮ ਵਿਚ ਸ਼ਾਮਲ ਹੋ ਸਕਦਾ ਹੈ ਜੇ ਤੁਹਾਨੂੰ ਕਿਸੇ ਮਦਦ ਦੀ ਜ਼ਰੂਰਤ ਹੈ ਜਾਂ ਕੋਈ ਪ੍ਰਸ਼ਨ ਹੈ। [ਟੀਮ ਵਿਚ ਸ਼ਾਮਲ ਹੋ](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +ਆਓ ਹੁਣ ਤੁਹਾਨੂੰ ਹੋਰ ਪ੍ਰੋਜੈਕਟਾਂ ਵਿੱਚ ਯੋਗਦਾਨ ਪਾਉਣ ਲਈ ਸ਼ੁਰੂਆਤ ਕਰੀਏ. ਅਸੀਂ ਪ੍ਰੋਜੈਕਟਾਂ ਦੀ ਇੱਕ ਸੂਚੀ ਤਿਆਰ ਕੀਤੀ ਹੈ ਜਿਸ ਨਾਲ ਤੁਸੀਂ ਅਸਾਨ ਮੁੱਦਿਆਂ ਨੂੰ ਸ਼ੁਰੂ ਕਰ ਸਕਦੇ ਹੋ। [ਪ੍ਰੋਜੈਕਟਾਂ ਦੀ ਸੂਚੀ](https://firstcontributions.github.io/#project-list). + +### [ਵਾਧੂ ਸਮੱਗਰੀ](additional-material/git_workflow_scenarios/additional-material.md) + +## ਹੋਰ ਟੂਲਜ ਦੀ ਵਰਤੋਂ ਕਰਦਿਆਂ ਟੁਟੋਰਿਅਲ + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.pl.md b/translations/README.pl.md new file mode 100644 index 00000000000..918cc8a2977 --- /dev/null +++ b/translations/README.pl.md @@ -0,0 +1,124 @@ +[![Open Source Love](https://firstcontributions.github.io/open-source-badges/badges/open-source-v1/open-source.svg)](https://github.com/firstcontributions/open-source-badges) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Pierwsze kontrybucje + +Zawsze jest ciężko, kiedy robisz coś po raz pierwszy. Szczególnie gdy współpracujesz z innymi ludźmi, ponieważ popełnianie błędów nie jest niczym przyjemnym. Jednak właśnie na współpracy opiera się idea otwartego oprogramowania. Chcemy nauczyć w prosty sposób nowych programistów jak wgrać swoją pierwszą zmianę w obcym projekcie. + +Czytanie artykułów i oglądanie poradników może pomóc, ale czy jest coś lepszego niż spróbowanie czegoś samemu bez obaw, że się coś zepsuje? Ten projekt ma na celu dostarczyć nowicjuszom wskazówek i uprościć proces wgrania pierwszej zmiany. Pamiętaj: im bardziej jesteś zrelaksowany, tym lepiej się uczysz. Jeśli chcesz wgrać swoją pierwszą kontrybucję wykonaj kilka prostych kroków poniżej. Będzie fajnie, obiecujemy. + +fork this repository + +Jeśli nie masz Gita na swoim komputerze, [ zainstaluj go ]( https://help.github.com/articles/set-up-git/ ). + +## Utwórz fork repozytorium (`fork`) + +Utwórz fork tego repozytorium klikając przycisk `Fork` na górze tej strony. Stworzysz tym samym kopię tego repozytorium na swoim koncie. + +## Sklonuj repozytorium (`clone`) + +clone this repository + +Teraz sklonuj repozytorium na swój komputer. Przejdź do swojego konta GitHub, otwórz skopiowane repozytorium, kliknij przycisk `Code`, a później ikonkę *skopiuj do schowka*. + +Otwórz konsolę i uruchom komendę git: + +``` +git clone +``` +Gdzie `` to adres tego repozytorium (twojej kopii tego projektu). Zobacz poprzedni krok aby skopiować adres. + +copy URL to clipboard + +Przykład: +``` +git clone https://github.com/to-ty/first-contributions.git +``` + +W miejscu `to-ty` to twój login na GitHubie. W tym kroku ściągasz zawartość twojej kopii repozytorium `first-contributions` z githuba na swój komputer. + +## Stwórz gałąź (`branch`) + +Wejdź do folderu ze swoim repozytorium (jeżeli jeszcze tam nie jesteś): + +``` +cd first-contributions +``` +Teraz utwórz nową gałąź wykonując polecenie `git checkout`: + +``` +git checkout -b +``` + +Przykład +``` +git checkout -b add-adam-kowalski +``` +(Nazwa gałęzi nie musi zawierać słowa *add*, ale dobrze jest je dodać z racji tego, że celem tej gałęzi jest dodanie twojego imienia do listy.) + +## Wprowadź zmiany i wgraj je + +Otwórz plik `Contributors.md` w edytorze tekstu. Musisz znać Markdown, lekki język znaczników. Tu masz ściągawkę gdzie znajdziesz informację jak go używać. + +Dodaj następującą linię na końcu `Contributors.md` + +``` +[Twoje imię](https://github.com/Twoja-nazwa-użytkownika) +``` +Przykład: +``` +[John Doe](https://github.com/johndoe) +``` + +Upewnij się że nie ma spacji pomiędzy `](`. Zapisz plik i następnie go zamknij. + +Jeżeli wejdziesz do folderu ze swoim repozytorium i wykonasz komendę `git status`, zobaczysz, że są tam zmiany. Dodaj te zmiany do gałęzi którą właśnie utworzyłeś używając komendy `git add`: +``` +git add Contributors.md +``` + +Teraz zapisz te zmiany wykonując komendę `git commit`: +``` +git commit -m "Add to Contributors list" +``` +Zastąp `` swoim imieniem i nazwiskiem. + +## Wyślij zmiany na GitHub + +Wyślij swoje zmiany komendą `git push`: +``` +git push origin +``` +Zastąp `` nazwą gałęzi, którą wcześniej utworzyłeś. + +## Wyślij swoje zmiany do zatwierdzenia + +W swoim repozytorium na GitHubie znajdziesz przycisk `Compare & pull request`. Kliknij go. + +create a pull request + +Teraz wyślij prośbę o scalenie. + +submit pull request + +Niedługo dodam proponowane przez ciebie zmiany do głównej gałęzi projektu. Zostaniesz powiadomiony mailowo kiedy zmiany zostaną scalone. + +## Co dalej? + +Brawo! Właśnie ukończyłeś standardowy workflow _fork -> clone -> edit -> pull request_, który często będziesz napotykać jako współtwórca! + +Świętuj swoją pierwszą zmianę i podziel się nią z przyjaciółmi i obserwującymi poprzez aplikację. + +Możesz dołączyć do naszego kanału slack w przypadku kiedy będziesz potrzebował pomocy albo miał jakieś pytania. Dołącz do slacka. + +Możesz teraz zacząć uczestniczyć w innych projektach. Przygotowaliśmy listę projektów z prostymi zadaniami które będą dobre na początek. Sprawdź listę projektów. + +### [Materiały dodatkowe](../additional-material/git_workflow_scenarios/additional-material.md) + +## Ćwiczenia przy użyciu innych narzędzi + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.ps.md b/translations/README.ps.md new file mode 100644 index 00000000000..47924cecdab --- /dev/null +++ b/translations/README.ps.md @@ -0,0 +1,142 @@ +
+Open Source Love Open Source Helpers +
+ +#
لومړی ګډون
+*** +
+د دې پروژې موخه دا ده ترڅو نویو پېل کوونکو ته په خلاصو سرچینو پروژو (Open Source Projects) کې د ګډون لاره وښئ که چېرې تاسو غواړی خپل لومړی ګډون پیل کړئ لاندې قدمونه پر مخ یوسئ. + +که د کمانډ لاین سره راحت نه یاست [ کولای شی تصویر بڼه دلته پرمخ یوسئ](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools) + +که چېرې مو git نه وي انسټال کړی [له دغه ځایه یې درښکته او انسټال یې کړئ](https://help.github.com/articles/set-up-git/) + +
+ +fork this repository + +###
دا ذخیره (repository) فورک کړئ:
+*** +

+د دې پاڼې په سر کې د فورک تڼئ پر کلیک سره تاسو کولای شئ دا repository فورک کړئ، فورک به د دې repository یوه کاپي ستاسو د کیټ هب په اکونټ کې جوړه کړي. +

+ +###
دا ذخیره (repository) کلون کړئ:
+*** +clone this repository + +

اوس فورک کړل شوې ریپوزیټوري کلون یعنې ښکته کړئ د دې کار د ترسره کولو لپاره خپل اکونټ ته لاړ شی د کوډ پر تڼۍ کلیک وکړئ او د ریپوزیټوري لینک کاپي کړئ.

+ +

ترمینل یا CMD خلاص کړئ او لاندې د کیټ کمنډ رن کړئ

+```git +git clone "د ریپوزیټوري کاپي کړل شوی لینک" +``` +

د بیلکې په توګه

+ +```git +git clone https://github.com/MasihKarimi/first-contributions.git +``` +

په پورته لینک کې د MasihKarimi پرځای باید ستاسو د کیټ هب د اکونټ نوم وي

+ +

د پورته قدمونو په اخیستلو سره تاسو د “first-contributions” ذخیره یا ریپوزیټوري خپل کمپیوټر ته ښکته کوۍ.

+ +###
نوې څانګه یا برانچ جوړ کړئ:
+*** +

‌اوس د first-contributions پروژه په خپل کوډ ایډیټر کې پرانيزی او په ترمینل کې د لاندې کیټ کمنډ په رن کولو سره نوی برانچ یا څانګه جوړه کړئ.

+ +```git +git switch -c د څانګې نوم +``` +

د بیلکې په توګه

+```git +git switch -c add-Masih-Karimi +``` + +

add-Masih-Karimi زما د څانګې نوم دی تاسو کولائ شئ خپل نوم غوره کړئ

+ +###
اړین بدلونونه راوړئ او دا بدلونونه ترسره یا commit کړئ:
+*** + +

اوس د contributors.md فایل راخلاص کړئ او خپل نوم مو وراضافه کړئ نوم مو د فایل په شروغ یا اخر کې مه اضافه کوئ په منځ کې یې اضافه کړئ او فایل ذخیره کړئ

+ +git status +

اوس که چېرې ټرمینل ته ولاړ شئ او د git status کمنډ رن کړئ تاسو کولائ شئ وګورئ چې په کوم فایل کې مو بدلونونه راوستي دي

+ +

په دې برخه کې د git add کمنډ په مرسته خپل بدلونونه خپل نوي جوړې کړل شوې څانګې ته اضافه کړئ:

+ +```git +git add contributors.md +``` +

اوس اضافه کړل شوي بدلونونه د لاندې کمنډ په مرسته ترسره یا commit کړئ:

+ +```git +git commit -m “Add Masih Karimi to Contributors List” +``` +

د Masih Karimi پر ځای مو خپل نوم ولیکئ

+ +###
بدلونونه کیټ هب ته پورته یا push کړئ:
+*** +

په دې برخه کې د git push کمنډ په مرسته خپل بدلونونه کیټ هب ته پورته کړئ

+

د بېلګې په توګه

+ +```git +git push origin -u add-Masih-Karimi +``` +

هېر نه کړئ چې د add-Masih-Karimi پر ځای د خپلې څانګې نوم ورکړئ

+ +
+ که چېرې په دې لړ کې د کومې ستونزې سره مخ شوئ دا ځاې کېکاږئ + +- ### د تصدیق کولو تېروتنه + 
remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead.
+  remote: Please see https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ for more information.
+  fatal: Authentication failed for 'https://github.com//first-contributions.git/'
+ [په دې کیټ هب ښونه کې زده کړئ چې څنګه پورته ستونزه حل کړئ](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account) + +
+ + + +###
خپل بدلونونه د بیاکتنې لپاره وسپارئ
+*** + +

اوس که چېرې دې ریپوزیټوري ته په خپل کیټ هب اکونټ کې ورشئ تاسو به یو یوه تنۍ د Compare & pull request متن سره ووینۍ. دا تنۍ کیکاږئ

+create a pull request + +

اوس د pull غوښتنه وسپارئ

+ +submit pull request + +

له دې ورسته به زه ستاسو راوستي بدلونه د اصلي یا main څانګې سره یوځای کړم او ستاسو نوم به د ګډون کوونکو لیست ته اضافه کړل شي.

+ +###
له دې ځایه وروسته چېرته ولاړ شئ:
+*** +

+

+بریا!! !! تاسو په بریالیتوب سره د فورک، کلون ، ایډټ او پول غوښتنې چارې ترسره کړې ، د دې چارو سره به مو د یو ګډون کوونکي په توګه همیش سر او کار وي. +

+ +

+خپل لومړئ ګډون مو ولمانځئ او له خپلو ملګرو سره یې شریک کړئ + +

+ +

که چېرې کومه ستونزه او پوښتنه لرئ کولائ شئ زموږ د سلک slack ټیم سره یوځائ شئ

+ +

+اوس راځئ په نورو پروژو کې ګډون وکړئ موږ د هغو پروژو لیست جمتو کړئ دئ چې تاسو کولائ شئ په آسانی ګډون پکې وکړئ د پروژو لیست دلته وګورئ + +

+ + + +### + + +###
د نورو وسیلو په کارولو سره درسونه
+*** + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [GitHub Desktop](gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](gui-tool-tutorials/github-windows-intellij-tutorial.md) | \ No newline at end of file diff --git a/translations/README.pt-pt.md b/translations/README.pt-pt.md new file mode 100644 index 00000000000..45d6f9273e1 --- /dev/null +++ b/translations/README.pt-pt.md @@ -0,0 +1,105 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Primeiras Contribuições + +É difícil. É sempre difícil fazer algo pela primeira vez. Especialmente quando se está a colaborar, errar não é algo agradável. Mas *open source* (código aberto) trata-se de colaboração e de trabalharmos juntos. Queremos simplificar a forma com que novos colaboradores *open source* aprendem e contribuem pela primeira vez. + +Ler artigos e ver tutoriais pode ajudar, mas nada melhor do que realmente "pôr a mão na massa" sem estragar nada. Este projeto visa simplificar a forma com que os novatos fazem a sua primeira contribuição. Lembra-te: quanto mais relaxado(a) estiveres, melhor aprenderás. Se quiseres fazer a tua primeira contribuição, segue os passos abaixo. Nós prometemos, será divertido. + +Se ainda não tens o git na tua máquina, [instala-o aqui]( https://help.github.com/articles/set-up-git/ ). + +## Faz um Fork deste repositório +fork deste repositorio + +Faz um Fork ao clicares no botão "Fork" no topo desta página. Isto vai criar uma cópia deste repositório na tua conta. +



+## Clone o repositório + +clonar este repositório + +Agora clone este repositório para a tua máquina. Carrega no botão "Clone or download" e, em seguida, clica no ícone "Copy to clipboard" para copiar a URL. + +Abre o teu terminal e executa o comando seguinte: +``` +git clone "url que copiou" +``` +onde "url que copiou" (sem as aspas) é a URL deste repositório. Consulta as etapas anteriores para obter a URL. + +copiar URL + +Por exemplo: +``` +git clone https://github.com/este-eh-voce/first-contributions.git +``` +onde "este-eh-voce" é o seu usuário do GitHub. Aqui estas a copiar o conteúdo do repositório first-contributions para o teu computador. + +## Cria um Branch + +Vá para o diretório do repositório no teu computador (caso ainda não estejas lá): +``` +cd first-contributions +``` + +Agora cria um Branch usando o comando `git checkout`: +``` +git checkout -b +``` + +Por exemplo: +``` +git checkout -b add-alonzo-church +``` +Obs.: O nome do Branch não precisa de ter a sigla "add", mas neste caso é recomendável, porque a finalidade deste Branch é a de adicionar o teu nome a uma lista. + +## Efetua as alterações necessárias e faz um Commit + +Agora abre o ficheiro `Contributors.md` no teu editor de código, adiciona o teu nome nele e guarda o ficheiro. Se fores para o diretório do projeto e executar o comando `git status`, verás que há alterações. Adiciona essas alterações ao Branch que acabaste de criar utilizando o comando `git add`: +``` +git add Contributors.md +``` +Agora faz um Commit dessas alterações utilizando o comando `git commit`: +``` +git commit -m "Add to Contributors list" +``` +preenche `` com o teu nome ou nickname. + +## Faz um Push das alterações para o GitHub + +Faz um Push utilizando o comando `git push`: +``` +git push origin +``` +substitui `` pelo nome do Branch que criaste anteriormente. + +## Envia as tuas alterações para serem revistas + +Se fores para o teu repositório no GitHub, verás um botão `Compare & pull request`. Clica nesse botão. + +Cria um Pull Request + +Agora envia um Pull Request. + +Envia um pull request + +Logo estarei a incorporar as tuas mudanças no Branch principal (master) deste projeto. Vais receber um e-mail de notificação quando as alterações forem incorporadas. + +## Para onde ir a partir daqui? + +Celebra as tuas contribuições e partilha-as com amigos e seguidores através da [web app](https://roshanjossey.github.io/first-contributions/#social-share). + + Podes também juntar-te à nossa equipa no Slack caso precises de alguma ajuda ou tenhas alguma dúvida. [Junta-te à nossa equipa no Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Aqui estão alguns repositórios com Issues a nível de principiante em que tu podes ajudar a resolver. Vai em frente e clica nos repositórios para saber mais. + +### [ Material adicional ](../additional-material/translations/Portuguese/additional-material.pt_br.md) + +## Tutoriais com outras ferramentas + + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + diff --git a/translations/README.pt_br.md b/translations/README.pt_br.md new file mode 100644 index 00000000000..510eaacae56 --- /dev/null +++ b/translations/README.pt_br.md @@ -0,0 +1,124 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[Junte-se à nós no Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Primeiras Contribuições + +Este projeto visa facilitar o caminho e guiar os iniciantes em suas primeiras contribuições. Se você deseja fazer a sua primeira contribuição, siga os passos abaixo. + +#### _Se não se sente confortável com a linha de comando, [aqui estão alguns tutoriais de ferramentas gráficas.](#Tutoriais-usando-outras-ferramentas)_ + +fork deste repositório + +Se não possui o git em sua máquina, [instale-o aqui](https://help.github.com/articles/set-up-git/). + +## Faça um _Fork_ deste repositório + +Faça um _Fork_ clicando no botão "_Fork_" no topo desta página, uma cópia deste repositório será criada em sua conta. + +## Clone o repositório + +clonar este repositório + +Agora clone este repositório para a sua máquina. Clique no botão "_Clone or download_" e, em seguida, clique no ícone "_Copy to clipboard_" para copiar a URL. + +Abra um terminal e execute o seguinte comando do git: + +``` +git clone "url que copiou" +``` + +onde "url que copiou" (sem as aspas) é a URL deste repositório (seu fork deste projeto). Consulte as etapas anteriores para obter a URL. + +copiar URL + +Por exemplo: + +``` +git clone https://github.com/seu-usuario/first-contributions.git +``` + +onde "seu-usuário" é o seu usuário do _GitHub_. Aqui você estará copiando o conteúdo do repositório _first-contributions_ para o seu computador. + +## Crie um Branch + +Acesse o diretório do repositório no seu computador (caso você não esteja nele): + +``` +cd first-contributions +``` + +Agora crie um _Branch_ usando o comando `git checkout`: + +``` +git switch -c +``` + +Por exemplo: + +``` +git switch -c add-andre-oliveira +``` + +Obs.: O nome do _Branch_ não precisa ter a sigla "add", mas nesse caso é recomendável, porque a finalidade deste _Branch_ é a de adicionar o seu nome à uma lista. + +## Efetue as alterações necessárias e faça um _Commit_ + +Agora, abra o arquivo `Contributors.md` em seu editor de código e adicione o seu nome a ele. Não o adicione no início ou no final do arquivo. Coloque-o em qualquer lugar no meio. Agora, salve o arquivo. + +git status + +Se você for para o diretório do projeto e executar o comando `git status`, verá que há alterações. Adicione essas alterações ao _Branch_ que você acabou de criar utilizando o comando `git add`: + +``` +git add Contributors.md +``` + +Agora, confirme essas alterações usando o comando git commit `git commit`: + +``` +git commit -m "Add to Contributors list" +``` + +substituindo `` pelo seu nome. + +## Faça um Push das alterações para o _GitHub_ + +Envie suas alterações usando o comando `git push`: + +``` +git push origin +``` + +substituindo `` pelo nome do _Branch_ que você criou anteriormente. + +## Envie suas alterações para serem revisadas + +Se você for para o seu repositório no _GitHub_, verá um botão `Compare & pull request`. Clique nesse botão. + +Crie um Pull Request + +Agora envie um _Pull Request_. + +Envie o Pull Request + +Logo estará mesclando ('mergeando') as suas mudanças no _Branch_ principal (master) deste projeto. Você receberá um e-mail de notificação quando as alterações forem mescladas. + +## Para onde ir a partir daqui? + +Parabéns! Você completou o fluxo de trabalho básico _fork -> clone -> edit -> PR_ que você encontrará frequentemente como contribuidor! + +Celebre sua contribuição e compartilhe com seus amigos e seguidores no [app web](https://roshanjossey.github.io/first-contributions/#social-share). + +Você também pode se juntar à nossa equipe no _Slack_ caso precise de alguma ajuda ou tenha alguma dúvida. [Junte-se à nossa equipe no Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Agora você pode colaborar com outros projetos. Nós compilamos uma lista de projetos com problemas simples que você pode começar. Verifique em [a lista de projetos no web app](https://roshanjossey.github.io/first-contributions/#project-list). + +### [ Material adicional ](../additional-material/translations/Portuguese/additional-material.pt_br.md) + +## Tutoriais usando outras ferramentas + +|GitHub Desktop | Visual Studio 2017 | IntelliJ IDEA | +| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +|[GitHub Desktop](../gui-tool-tutorials/translations/github-desktop-tutorial.pt_br.md) | [Visual Studio 2017](../gui-tool-tutorials/translations/github-windows-vs2017-tutorial.pt_br.md) |[IntelliJ IDEA](../gui-tool-tutorials/translations/github-windows-intellij-tutorial.pt_br.md) | diff --git a/translations/README.pus.md b/translations/README.pus.md new file mode 100644 index 00000000000..8ffcf668d60 --- /dev/null +++ b/translations/README.pus.md @@ -0,0 +1,109 @@ +[![Open Source Love](https://firstcontributions.github.io/open-source-badges/badges/open-source-v1/open-source.svg)](https://github.com/firstcontributions/open-source-badges) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-vchl8cde-S0KstI_jyCcGEEj7rSTQiA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +

+ +# لومړنۍ مرستې +د دې پروژې موخه دا ده چې د پیل کونکو لپاره د دوی لومړنۍ مرسته کولو لاره ساده او لارښود کړي. که تاسو د خپلې لومړۍ مرستې په لټه کې یاست، لاندې مرحلې تعقیب کړئ. + +_که تاسو د کمانډ لاین (CLI) سره راحته نه یاست ، [دا لارښوونې وکاروئ ترڅو پوه شئ چې د GUI وسیلو کارولو څرنګوالی](#د-نورو-وسیلو-کارولو-لارښوونې)._ + +fork this repository + +#### که تاسو git نصب نلرئ [له دې ځایه نصب کړئ](https://help.github.com/articles/set-up-git/). + +## د دې ریپوزیتوری فورک کړئ +د دې پاڼې په سر کې د Fork تڼۍ په کلیک کولو سره دا ذخیره فورک کړئ. +دا به ستاسو په حساب کې د دې ذخیره کاپي رامینځته کړي. + +## فورک شوی ریپازیتوری کلون Clone کړئ + +clone this repository + +اوس خپل ماشین ته د فورک شوي ذخیره کلون کړئ. خپل GitHub حساب ته لاړ شئ، د فورک شوي ریپازیتوری خلاص کړئ، د Code تڼۍ باندې کلیک وکړئ او بیا د کلپ بورډ ته د Copy To Clipboard باندې کلیک وکړئ. + +بیا یو ټرمینل خلاص کړئ او لاندې کمانډ چل کړئ: +``` +git clone "url you just copied" +``` +چیرته چې "url you just copied" (پرته د نرخ نښه) د دې ریپازیتوری url دی (ستاسو د دې پروژې فورک). د url ترلاسه کولو لپاره مخکیني ګامونه وګورئ. + +copy URL to clipboard + +د مثال په توګه: +``` +git clone https://github.com/this-is-you/first-contributions.git +``` +چیرته چې 'this-is-you' ستاسو د GitHub کاربری نوم دی. دلته تاسو خپل کمپیوټر ته په GitHub کې د لومړۍ مرستې ذخیره مینځپانګې کاپي کوئ. + +### یوه څانګه جوړه کړئ +په خپل کمپیوټر کې د ریپوزیتوری لارښود ته بدل کړئ (که تاسو دمخه نه لرئ): +``` +cd first-contributions +``` +اوس د `git switch` کمانډ په کارولو سره څانګه جوړه کړئ: +``` +git checkout -b your-new-branch-name +``` +د مثال په توګه: +``` +git checkout -b add-alonzo-church +``` + +### اړین بدلونونه وکړئ او دا بدلونونه Commit کړئ +اوس د `Contributors.md` فایل په متن ایډیټر کې خلاص کړئ، خپل نوم پکې اضافه کړئ. دا د فایل په پیل یا پای کې مه اضافه کړئ. په منځ کې هر ځای کېږدئ. اوس، فایل ذخیره کړئ. + +git status + +که تاسو د پروژې موقعیت ته لاړ شئ او د `git status` کمانډ اجرا کړئ ، نو تاسو به وګورئ چې بدلونونه شتون لري. + +د `git add` کمانډ په کارولو سره دا بدلونونه په هغه څانګه کې اضافه کړئ چې تاسو یې رامینځته کړی: +``` +git add Contributors.md +``` + +اوس دا بدلونونه د `git commit` کمانډ په کارولو سره ترسره کړئ: +``` +git commit -m "Add to Contributors list" +``` + د خپل نوم سره بدل کړئ. + +## GitHub ته بدلونونه فشار (Push) وکړئ +د 'git push' کمانډ په کارولو سره خپل بدلونونه فشار (Push) وکړئ: +``` +git push origin +``` +د `your-branch-name` بدلول د هغه څانګې نوم سره چې تاسو مخکې جوړ کړی: + +## خپل بدلونونه د بیاکتنې لپاره وسپارئ +که تاسو په GitHub کې خپل ریپازیتوری ته لاړ شئ، نو تاسو به د `Compare & pull request` تڼۍ وګورئ. په هغه تڼۍ کلیک وکړئ. + +create a pull request + +اوس د پلولو غوښتنه (Pull Request) وسپارئ. + +submit pull request + +ډیر ژر به زه ستاسو ټول بدلونونه د دې پروژې په اصلي څانګه کې یوځای کړم. تاسو به د خبرتیا بریښنالیک ترلاسه کړئ کله چې بدلونونه یوځای شي. + +## راتلونکی څه شی دی +مبارک شه! تاسو یوازې د معیاري فورک(Fork)، کلون(Clone)، ایډیټ(Edit)، او پلولو غوښتنې (Pull Request) کاري فلو بشپړ کړی چې تاسو به ډیری وختونه د مرسته کونکي په توګه ورسره مخ شئ! + +خپله ونډه ولمانځئ او له خپلو ملګرو او پیروانو سره یې شریک کړئ [دلته](https://firstcontributions.github.io/#social-share) لاړ شئ. + +همدارنګه، تاسو کولی شئ زموږ د Slack ټیم سره یوځای شئ که تاسو کومې مرستې ته اړتیا لرئ یا کومه پوښتنه لرئ. [دلته کلیک وکړی](https://join.slack.com/t/firstcontributors/shared_invite/zt-vchl8cde-S0KstI_jyCcGEEj7rSTQiA) + +اوس راځئ چې تاسو په نورو پروژو کې د مرستې سره پیل وکړو. موږ د اسانه مسلو سره د پروژو لیست ترتیب کړی چې تاسو یې پیل کولی شئ. [بشپړ ی وګوره](https://firstcontributions.github.io/#project-list) + +### [نور معلومات](additional-material/git_workflow_scenarios/additional-material.md) + +## د-نورو-وسیلو-کارولو-لارښوونې +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [GitHub Desktop](gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](gui-tool-tutorials/github-windows-intellij-tutorial.md) | +| | | | | | | +

+ + diff --git a/translations/README.ro.md b/translations/README.ro.md new file mode 100644 index 00000000000..90bd588d560 --- /dev/null +++ b/translations/README.ro.md @@ -0,0 +1,112 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Primele Contribuții + +Este greu. Este întotdeauna greu când faci ceva pentru prima dată. Mai ales când colaborezi. A face greșeli nu este un lucru confortabil. Dar cel mai important în open source este colaborarea și lucrul în echipă. Noi am vrut să simplificăm modul în care noii contribuabili în open source învață și contribuie pentru prima dată. + +Citirea articolelor și vizionarea tutorialelor poate ajuta, dar ce este mai bine decât să faci lucrurile fără a strica ceva? Acest proiect își propune să ofere îndrumare și simplificarea modului în care începătorii își fac prima contribuție. Amintește-ți: cu cât ești mai relaxat, cu atât mai bine înveți. Dacă dorești să faci prima ta contribuție, simplu urmați pașii de mai jos. Vă promit că va fi distractiv. + +#### *Citește în [alte limbi](Translations.md).* + +fork this repository + +Dacă nu ai git instalat, [ instalează-l ]( https://help.github.com/articles/set-up-git/ ). + +## Ramifică repozitoriul(depozit) + +Ramifică acest repo(depozit) făcând clic pe butonul fork locat pe partea de sus a paginii. +Acesta va creea o copie a repozitoriului în contul tău. + +## Clonează repozitoriul(depozit) + +clone this repository + +Acum clonează acest repo pe computerul tău. Fă clic pe butonul clone apoi clic pe *copiați în clipboard*. + +Deschideți un terminal și executați următoarea comanda git: + +``` +git clone "adresa copiată" +``` +Unde "adresa copiată" (Fără de ghilimele) este adresa repozitoriului. Vezi pașii anteriori pentru a obține adresa. + +copy URL to clipboard + +De exemplu: +``` +git clone https://github.com/acesta-ești-tu/prima-contribuție.git +``` +Unde `acesta-ești-tu` este numele tău GitHub. Aici tu copiezi conținutul repozitorului GitHub "prima-contribuție" pe computerul tău. + +## Creează o Ramură + +Schimbați directorul în repozitoriu pe computer (dacă nu sunteți deja acolo): + +``` +cd prima-contribuție +``` +Acum creați o ramură cu ajutorul comenzii `git checkout`: +``` +git checkout -b +``` + +De exemplu: +``` +git checkout -b adaug-alonzo-church +``` +(Numele ramurii nu e obligatoriu să fie *adaug*, dar e un lucru rezonabil pentru a include deoarece scopul acestei ramure este de a adăuga numele tău în lista!) + +## Fă schimbările necesare si comite aceste schimbări + +Acum deschide fișierul `Contributors.md` într-un editor de text (ca NotePad, Vim, nano, emacs, etc.), adaugă numele tău în el, apoi salvează fișierul. Dacă accesezi directorul de proiect și execuți comanda `git status`, vei vedea schimbări. Adaugă acele schimbări la ramura creată de tine cu comanda `git add`: +``` +git add Contributors.md +``` + +Acum comite acele schimbări cu comanda `git commit`: +``` +git commit -m "Adaug la lista de contribuitori" +``` +Schimbând `` cu numele tău. + +## Împinge Schimbările pe GitHub + +Împinge schimbările tale cu comanda `git push`: +``` +git push origin +``` +Schimbând `` cu numele ramurii create de tine anterior. + +## Trimite modificările pentru examinare + +Dacă pleci la repozitoriul tău de pe GitHub, vei vedea butonul `Compare & pull request`(Compară & trage cererea). Fă clic pe el. + +create a pull request + +Acum trimiteți solicitarea de tragere. + +submit pull request + +Curând eu voi îmbina toate schimbările în ramura principală a acestui proiect. Veți primi un e-mail de notificare odată ce schimbările au fost fuzionate. + +## De unde să mergi de aici? + +Sărbătoriți-vă contribuția și împărtășiți-o cu prietenii și adepții dvs. accesând [aplicația web](https://roshanjossey.github.io/first-contributions/#social-share). + +Ați putea să vă alăturați echipei noastre în cazul în care aveți nevoie de ajutor sau aveți întrebări. [Alătură-te echipei Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Acum, să începem să contribuiți la alte proiecte. Am compilat o listă de proiecte cu probleme ușoare pe care le puteți începe. Verifică [lista de proiecte in aplicația web](https://roshanjossey.github.io/first-contributions/#project-list). + +### [ Materiale adiționale ](../additional-material/git_workflow_scenarios/additional-material.md) + + +## Tutoriale Folosind Alte Unelte + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + diff --git a/translations/README.ru.md b/translations/README.ru.md new file mode 100644 index 00000000000..6fc82676d47 --- /dev/null +++ b/translations/README.ru.md @@ -0,0 +1,174 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Первый вклад в проект + +Сложно. Всегда сложно начинать что-то с самого начала. Довольно неприятно совершать ошибки, особенно если вы работаете в команде. Весь open source состоит из сотрудничества и совместной работы. Мы хотим облегчить первые шаги в обучении и сотрудничестве начинающим разработчикам. + +Чтение статей и учебников может помочь, но что может быть лучше, чем настоящий практический опыт, без риска что-либо испортить. Цель этого проекта - должным образом направить молодых новобранцев, а также предоставить им возможность сделать их первый вклад. Помните: чем меньше вы напряжены, тем лучше вы учитесь. Если вы ищете возможность осуществить свой первый вклад, просто следуйте простым шагам, расположенным ниже. Обещаем, будет интересно. + +Если вам нужна помощь с командной строкой, [это руководство использует инструменты графической операционной системы (GUI).](#Использование-других-инструментов) + +сделать ответвление + +Если у вас не установлен git на компьютере, [ установите его. ](https://help.github.com/articles/set-up-git/) + +## Создайте ответвление + +Создайте собственное ответвление, нажав на кнопку `fork` сверху этой страницы. Таким образом вы создадите копию этого репозитория в своем аккаунте. + +## Клонируйте репозиторий + +клонировать репозиторий + +Теперь клонируйте ваш репозиторий на ПК. Нажмите на кнопку `clone`, а затем на иконку `copy to clipboard`, чтобы скопировать ссылку. + +Откройте терминал и запустите следующую git команду: + +``` +git clone "ссылка на репозиторий" +``` + +Где "ссылка на репозиторий" (без кавычек) это ссылка на ваш репозиторий. Посмотрите предыдущие шаги, чтобы получить эту ссылку. + +скопируйте ссылку в буфер обмена + +Например: + +``` +git clone https://github.com/ваш-логин/first-contributions.git +``` + +Где `ваш логин` ваш логин на github'e. Таким образом вы копируете репозиторий 'first-contributions' с GitHub на ваш ПК. + +## Создайте ветвь + +Перейдите в каталог репозитория на вашем компьютере, если вы еще не там. + +``` +cd first-contributions +``` + +Теперь создайте ветвь, с помощью команды `git checkout` + +``` +git checkout -b +``` + +Например: + +``` +git checkout -b add-alonzo-church +``` + +(Синтаксически не требуется, чтобы название ветви содержало слово _add_, но это оправдано, поскольку подчеркивает назначение этой ветви - добавить ваше имя в список.) + +## Внесите необходимые изменения и создайте коммит + +Теперь откройте файл `Contributors.md` в вашем текстовом редакторе, впишите ваше имя и сохраните файл. Если вы перейдете в директорию проекта и выполните `git status`, вы увидите изменения. Добавьте эти изменения с помощью команды `git add`. + +``` +git add Contributors.md +``` + +Теперь закоммитьте данные изменения с помощью команды `git commit`. + +``` +git commit -m "Add to Contributors list" +``` + +Измените `` на ваше имя + +## Запушьте изменения на github + +Запушьте ваши изменения с помощью `git push` + +``` +git push origin +``` + +Измените `` на имя ветви, которую вы создали ранее. + +## Подтвердите изменения для ревью + +Если вы зайдете в свой репозиторий на GitHub, вы увидите кнопку `Compare & pull request`. Нажмите на нее. + +create a pull request + +Теперь подтвердите пулл-реквест. + +submit pull request + +Скоро я произведу объединение всех ваших изменений с основной ветвью данного проекта. Вы получите сообщение по электронной почте, когда изменения будут приняты (смержены). + +Основная ветвь вашего репозитория не будет изменена. Для синхронизации выполните шаги, расположенные ниже. + +## Синхронизируйте ваше ответвление с данным репозиторием + +Прежде всего перейдите в основную ветвь: + +``` +git checkout master +``` + +Затем добавьте url моего репозитория в поле `upstream remote url`: + +``` +git remote add upstream https://github.com/Roshanjossey/first-contributions +``` + +Таким образом мы сообщим git'у, что существует другая версия данного проекта по определенной ссылке, и мы ее считаем мастером. Как только изменения смержены, подгрузите новую версию моего репозитория. + +``` +git fetch upstream +``` + +Таким образом мы забрали все изменения в моем ответвлении (upstream remote). После, вам нужно смержить новую версию моего репозитория с вашей мастер-ветвью. + +``` +git rebase upstream/master +``` + +Так вы применяете все изменения, которые вы подтянули к вашей мастер-ветви. Если вы запушите сейчас мастер-ветвь, ваше ответвление тоже будет содержать изменения. + +``` +git push origin master +``` + +Обратите внимание, что вы пушите в удаленной репозиторий origin. + +На этом этапе я объединил вашу ветвь `` со своей мастер-ветвью, а вы объединили свою мастер-ветвь с моей. Ваша ветвь больше не нужна, вы можете удалить ее: + +``` +git branch -d +``` + +Так же можете удалить ее версию в удаленном репозитории: + +``` +git push origin --delete +``` + +Это совершенно не обязательно, но название этой ветви отражает ее довольно специфическое назначение. И продолжительность ее жизни может быть соответствующе короткой. + +## Использование других инструментов + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + +## Что дальше? + +Ниже несколько популярных репозиториев, где вы можете найти задания для новичков. Вперед, перейдите в репозитории, чтобы узнать больше. + +| [![exercism](https://avatars2.githubusercontent.com/u/5624255?v=3&s=100)](https://github.com/exercism/exercism.io/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+patch%22) | [![fun-retro](https://avatars3.githubusercontent.com/u/15913975?v=3&s=100)](https://github.com/funretro/distributed/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly) | [](https://github.com/facebook/react/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+bug%22) | [![habitat](https://avatars1.githubusercontent.com/u/18171698?v=3&s=100)](https://github.com/habitat-sh/habitat/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [![scikit-learn](https://avatars0.githubusercontent.com/u/365630?v=3&s=100)](https://github.com/scikit-learn/scikit-learn/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [](https://github.com/technomancy/leiningen/issues?q=is%3Aopen+is%3Aissue+label%3ANewbie) | [](https://github.com/numpy/numpy/issues?q=is%3Aopen+is%3Aissue+label%3A%22Easy+Fix%22) | [![elasticsearch](https://avatars2.githubusercontent.com/u/6764390?v=3&s=100)](https://github.com/elastic/elasticsearch/issues?q=is%3Aopen+is%3Aissue+label%3A%22low+hanging+fruit%22) | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [exercism](https://github.com/exercism/exercism.io/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+patch%22) | [Fun Retros](https://github.com/funretro/distributed/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly) | [react](https://github.com/facebook/react/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+bug%22) | [habitat](https://github.com/habitat-sh/habitat/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [scikit-learn](https://github.com/scikit-learn/scikit-learn/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [Leiningen](https://github.com/technomancy/leiningen/issues?q=is%3Aopen+is%3Aissue+label%3ANewbie) | [numpy](https://github.com/numpy/numpy/issues?q=is%3Aopen+is%3Aissue+label%3A%22Easy+Fix%22) | [elasticsearch](https://github.com/elastic/elasticsearch/issues?q=is%3Aopen+is%3Aissue+label%3A%22low+hanging+fruit%22) | +| [![homebrew](https://avatars2.githubusercontent.com/u/1503512?v=3&s=100)](https://github.com/Homebrew/brew/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) | [![rust](https://avatars1.githubusercontent.com/u/5430905?v=3&s=100)](https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Aissue+label%3AE-easy) | [![vuejs](https://avatars1.githubusercontent.com/u/6128107?v=3&s=100)](https://github.com/vuejs/vue/issues?q=is%3Aopen+is%3Aissue+label%3A%22contribution+welcome%22) | [![Suave](https://avatars2.githubusercontent.com/u/5822862?v=3&s=100)](https://github.com/SuaveIO/suave/issues?q=is%3Aopen+is%3Aissue+label%3Ahardness-easy) | [![OpenRA](https://avatars3.githubusercontent.com/u/409046?v=3&s=100)](https://github.com/OpenRA/OpenRA/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [![PowerShell](https://avatars0.githubusercontent.com/u/11524380?v=3&s=100)](https://github.com/powershell/powershell/issues?q=is%3Aopen+is%3Aissue+label%3AUp-for-Grabs) | [![coala](https://avatars2.githubusercontent.com/u/10620750?v=3&s=100)](https://github.com/coala/coala/issues?q=is%3Aopen+is%3Aissue+label%3Adifficulty%2Flow+label%3Adifficulty%2Fnewcomer) | [![moment](https://avatars2.githubusercontent.com/u/4129662?v=3&s=100)](https://github.com/moment/moment/issues?q=is%3Aopen+is%3Aissue+label%3AUp-For-Grabs) | +| [homebrew](https://github.com/Homebrew/brew/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) | [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Aissue+label%3AE-easy) | [vuejs](https://github.com/vuejs/vue/issues?q=is%3Aopen+is%3Aissue+label%3A%22contribution+welcome%22) | [Suave](https://github.com/SuaveIO/suave/issues?q=is%3Aopen+is%3Aissue+label%3Ahardness-easy) | [OpenRA](https://github.com/OpenRA/OpenRA/issues?q=is%3Aopen+is%3Aissue+label%3AEasy) | [PowerShell](https://github.com/powershell/powershell/issues?q=is%3Aopen+is%3Aissue+label%3AUp-for-Grabs) | [coala](https://github.com/coala/coala/issues?q=is%3Aopen+is%3Aissue+label%3Adifficulty%2Flow+label%3Adifficulty%2Fnewcomer) | [moment](https://github.com/moment/moment/issues?q=is%3Aopen+is%3Aissue+label%3AUp-For-Grabs) | +| [![ava](https://avatars0.githubusercontent.com/u/8527916?v=3&s=100)](https://github.com/avajs/ava/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+for+beginner%22) | [![freeCodeCamp](https://avatars0.githubusercontent.com/u/9892522?v=3&s=100)](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only) | [![webpack](https://avatars3.githubusercontent.com/u/2105791?v=3&s=100)](https://github.com/webpack/webpack/issues?q=is%3Aopen+is%3Aissue+label%3A%22D1%3A+Easy+%28Contrib.+Difficulty%29%22) | [![hoodie](https://avatars1.githubusercontent.com/u/1888826?v=3&s=100)](https://github.com/hoodiehq/hoodie/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only) | [![pouchdb](https://avatars3.githubusercontent.com/u/3406112?v=3&s=100)](https://github.com/pouchdb/pouchdb/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) | [![neovim](https://avatars0.githubusercontent.com/u/6471485?v=3&s=100)](https://github.com/neovim/neovim/issues?q=is%3Aopen+is%3Aissue+label%3Aentry-level) | [![babel](https://avatars2.githubusercontent.com/u/9637642?v=3&s=100)](https://github.com/babel/babel/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly) | [](https://github.com/adobe/brackets/labels/Starter%20bug) | +| [ava](https://github.com/avajs/ava/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+for+beginner%22) | [freeCodeCamp](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only) | [webpack](https://github.com/webpack/webpack/issues?q=is%3Aopen+is%3Aissue+label%3A%22D1%3A+Easy+%28Contrib.+Difficulty%29%22) | [hoodie](https://github.com/hoodiehq/hoodie/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only) | [pouchdb](https://github.com/pouchdb/pouchdb/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) | [neovim](https://github.com/neovim/neovim/issues?q=is%3Aopen+is%3Aissue+label%3Aentry-level) | [babel](https://github.com/babel/babel/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly) | [brackets](https://github.com/adobe/brackets/labels/Starter%20bug) | +| [![Node.js](https://avatars1.githubusercontent.com/u/9950313?v=3&s=100)](https://github.com/nodejs/node/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22) | [](https://github.com/Semantic-Org/Semantic-UI-React/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22) | +| [Node.js](https://github.com/nodejs/node/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22) | [Semantic-UI-React](https://github.com/Semantic-Org/Semantic-UI-React/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22) | diff --git a/translations/README.se.md b/translations/README.se.md new file mode 100644 index 00000000000..4077a569dfe --- /dev/null +++ b/translations/README.se.md @@ -0,0 +1,123 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# First Contributions + +Det är alltid svårt första gången man gör något och speciellt när du samarbetar med andra kan det vara extra känsligt att göra misstag. Vi vill förenkla för dig att lära sig hur man bidrar till ett öppet källkods-projekt. + +Att läsa artiklar och titta på handledningar kan så klart hjälpa men det är alltid bättre att göra det på riktigt. Detta projeket har som syfte att tillhandahålla en guide och göra det enkelt för nybörjare att göra sina första bidrag. Om du är ute efter att göra ditt första bidrag kan du följa stegen nedan. + + +#### *Om du inte känner dig bekväm med kommandoraden, [så finns en vägledning här.](#Handledningar-för-andra-verktyg)* + + +fork this repository + +Om du inte har git installerat [så installera det]( https://help.github.com/articles/set-up-git/ ) + +## Gör en Fork på detta repository + +Forka repot genom att klicka på fork-knappen överst på denna sida. +Detta kommer att skapa en kopia av repot i ditt GitHub-konto. + +## Klona repository + +clone this repository + +Klona repot till din dator. Gå till ditt GitHub-konto och klicka på clone-knappen och klicka sedan på *copy to clipboard*-ikonen. + +Öppna en terminal och kör följande kommando: + +``` +git clone "url you just copied" +``` +där "url you just copied" (utan citat-tecken) är URL:en för detta repo (din fork för detta projekt). Se föregående steg för att hitta URL:en. + +copy URL to clipboard + +Till exempel: +``` +git clone https://github.com/this-is-you/first-contributions.git +``` +där `this-is-you` är ditt användarnamn på GitHub. På detta sätt kopierar du innehållet i repot till din dator. + +## Skapa en branch + +Gå till repo-katalogen på din dator (om du inte redan står i den katalogen): + +``` +cd first-contributions +``` + +Nu skapar du en branch genom att använda `git checkout`-kommandot: +``` +git checkout -b +``` + +Till exempel: +``` +git checkout -b mitt-tillag +``` + +## Gör de ändringar du vill göra och commita dem + +Nu öppnar du `Contributors.md` i en text-editor och lägger till ditt namn. Lägg inte till något i början eller slutet av dokumentet utan lägg till någonstans mitt emellan. Spara filen. + +git status + +Ge kommando `git status` i projektkatalogen för att se de ändringar du gjort. + + +Lägg till dina ändringar genom att använda kommando `git add -A`: + +``` +git add Contributors.md +``` + +Commita dina ändringar genom att använda `git commit`: +``` +git commit -m "Add to Contributors list" +``` +ersätt `` med ditt namn. + +## Pusha ändringar till GitHub + +Pusha dina ändringar genom att använda kommando `git push`: +``` +git push origin +``` +ersätt `` med det branch-namn du använt tidigare. + +## Skicka iväg dina ändringar för granskning + +Om du navigerar till ditt repo på GitHub kan du se en knapp med texten `Compare & pull request`. Klicka på den. + +create a pull request + +Skicka iväg din s.k. pull request. + +submit pull request + +Snart kommer jag införa dina ändringar i huvudprojektet. Du kommer att få ett e-mail så fort dina ändringar blivit införda. + +## Hur går man vidare? + +Gratulerar! Du har just genomfört standardprocessen för _fork -> clone -> edit -> PR_, en process du kommer att stöta på ofta! + +Fira genom att dela med dina vänner och följare genom att gå till [web app](https://roshanjossey.github.io/first-contributions/#social-share). + +Behöver du hjälp eller vill ställa frågor kan du gå med i vår slack-grupp. [Gå med i slack-gruppen](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Nu kan du gå vidare genom att bidra i andra projekt. Vi har sammanställt en lista med enkla uppgifter som du kan starta med. Kolla in [projektlistan i webbapplikationen](https://roshanjossey.github.io/first-contributions/#project-list). + +### [Ytterligare material](../additional-material/git_workflow_scenarios/additional-material.md) + + +## Handledningar för andra verktyg + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.si.md b/translations/README.si.md new file mode 100644 index 00000000000..a1d784cbfa0 --- /dev/null +++ b/translations/README.si.md @@ -0,0 +1,130 @@ +[![Open Source Love](https://firstcontributions.github.io/open-source-badges/badges/open-source-v1/open-source.svg)](https://github.com/firstcontributions/open-source-badges) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# පළමු දායකත්වය + +ආරම්භකයින්ගේ පළමු දායකත්වය ලබා දෙන ආකාරය සරල කිරීම සහ මඟ පෙන්වීම මෙම ව්‍යාපෘතියේ අරමුණයි. ඔබ ඔබේ පළමු දායකත්වය ලබා දීමට බලාපොරොත්තු වන්නේ නම්, පහත පියවර අනුගමනය කරන්න. + +#### *ඔබ විධාන රේඛාව (command line) සමඟ අපහසු නම්, [GUI මෙවලම් භාවිතා කරන නිබන්ධන මෙන්න.](#tutorials-using-other-tools)* + +මෙම ගබඩාව fork කරන්න + +ඔබේ පරිගණකයේ git නොමැති නම්, [ස්ථාපනය කරන්න](https://help.github.com/articles/set-up-git/). + +## මෙම ගබඩාව fork කිරීම + +පිටුවේ ඉහළින් ඇති fork බොත්තම ක්ලික් කිරීමෙන් මෙය කළ හැකිය. මෙය ඔබගේ ගිණුමේ +පිටපතක් සාදනු ඇත. + +## මෙම ගබඩාව clone කරන්න + +මෙම ගබඩාව clone කරන්න + +දැන් ඔබේ පරිගණකට fork කරපු repository ය ක්ලෝන කරන්න. ඔබට ඔබගේ GitHub ගිණුමට ගොස් fork කරපු repository විවෘත කර clone බොත්තම ක්ලික් කර එය පසුරු පුවරුවට (clipboard) පිටපත් කිරීමෙන් මෙය කළ හැක. + +*terminal* හෝ *command prompt* විවෘත කර පහත git විධානය ක්‍රියාත්මක කරන්න: + +``` +git clone "ඔබ පිටපත් කළ url එක" +``` + +මෙහි "ඔබ පිටපත් කළ url එක" (උපුටා දැක්වීම් ලකුණු නොමැතිව) මෙම ගබඩාවේ url එක වේ (මෙම ව්යාපෘතියේ ඔබේ දෙබල (fork) ). url එක ලබා ගැනීමට පෙර පියවර බලන්න. + +copy URL to clipboard + + +උදාහරණ වශයෙන්: + +``` +git clone https://github.com/මෙය-ඔබයි/first-contributions.git +``` + +මෙහි `මෙය ඔබයි` යනු GitHub පරිශීලක නාමයයි. මෙය ඔබගේ GitHub ගිණුමේ first-contributions repository පිටපතක් සෑදීමට ඔබට ඉඩ සලසයි. + +## ශාඛාවක් නිර්මාණය කිරීම + +ඔබේ පරිගණකයේ ගබඩා නාමාවලියට වෙනස් කරන්න (ඔබ දැනටමත් එහි නොමැති නම්): + +``` +cd first-contributions +``` + + +දැන් `git checkout` විධානය භාවිතා කරමින් ශාඛාවක් සාදන්න: + +``` +git checkout -b <ඔබගේ-නව-ශාඛාවේ-නම> +``` + +උදාහරණ වශයෙන්: + +``` +git checkout -b add-luke-oliff +``` + +(ශාඛාවේ නමට *add* එකතු කිරීම අවශ්‍ය නොවේ, නමුත් එය සාධාරණ දෙයකි, මන්ද මෙම ශාඛාවේ අරමුණ ඔබේ නම ලැයිස්තුවකට එකතු කිරීමයි.) + +## අවශ්‍ය වෙනස්කම් සිදු කර commit කරන්න + +දැන් Contributors.md ගොනුව පෙළ සංස්කාරකයක විවෘත කරන්න, එයට ඔබේ නම එක් කරන්න. ගොනුවේ ආරම්භයේ හෝ අවසානයේ එය එකතු නොකරන්න. එය අතර මැද ඕනෑම තැනකට එකතු කරන්න. දැන්, ගොනුව save කරන්න. + +git status + +ඔබ ව්‍යාපෘති නාමාවලිය වෙත ගොස් git status විධානය ක්‍රියාත්මක කළහොත්, වෙනස්කම් ඇති බව ඔබට පෙනෙනු ඇත. + +`git add` විධානය භාවිතයෙන් ඔබ දැන් නිර්මාණය කළ ශාඛාවට එම වෙනස්කම් එක් කරන්න: + +``` +git add Contributors.md +``` + +දැන් `git commit` විධානය භාවිතා කර එම වෙනස්කම් සිදු කරන්න: + +``` +git commit -m "Add <ඔයාගේ_නම> to Contributors list" +``` + +`<ඔබේ_නම>` වෙනුවට ඔබේ නම ඇතුල් කරන්න. + +## GitHub වෙත වෙනස්කම් තල්ලු කරන්න + +`git push` විධානය භාවිතයෙන් ඔබගේ වෙනස්කම් තල්ලු කරන්න: +``` +git push origin -u <ඔබගේ-නව-ශාඛාවේ-නම> +``` + +`<ඔබගේ-නව-ශාඛාවේ-නම>` ඔබ කලින් නිර්මාණය කළ නම සමඟ ශාඛාව ප්රතිස්ථාපනය කරන්න. + +## සමාලෝචනය සඳහා ඔබේ වෙනස්කම් ඉදිරිපත් කරන්න + + +ඔබ GitHub හි ඔබගේ ගබඩාවට ගියහොත්, ඔබට `Compare & pull request` බොත්තමක් පෙනෙනු ඇත. එම බොත්තම මත ක්ලික් කරන්න. + +create a pull request + +දැන් pull request ඉදිරිපත් කරන්න. + +submit pull request + +මම ළඟදීම ඔබේ සියලු වෙනස්කම් මෙම ව්‍යාපෘතියේ ප්‍රධාන ශාඛාවට ඒකාබද්ධ කරමි. වෙනස්කම් ඒකාබද්ධ කළ පසු ඔබට දැනුම්දීමේ Email පණිවිඩයක් ලැබෙනු ඇත. + +## මෙතැන් සිට කොහේ යන්නද? + +සුභ පැතුම්! ඔබ දායකයෙකු ලෙස සම්මත 'fork -> clone -> edit -> pull request' කාර්ය ප්‍රවාහය ඔබ සම්පුර්ණ කර ඇත! + +ඔබේ දායකත්වය සහ ඔබේ මිතුරන් සහ අනුගාමිකයින් සමඟ සමරන්න [web app](https://firstcontributions.github.io/#social-share) ගිහින් share කරන්න. + +ඔබට කිසියම් උදව්වක් අවශ්‍ය නම් හෝ කිසියම් ප්‍රශ්නයක් ඇත්නම් ඔබට අපගේ slack කණ්ඩායමට සම්බන්ධ විය හැකිය. [අපගේ slack කණ්ඩායමට එක්වන්න](https://join.slack.com/t/firstcontributors/shared_invite/zt-kpbyrmkk-JDkRtchcvRvQ0qK4iPmyvA).. + +දැන් අපි ඔබට වෙනත් ව්‍යාපෘති සඳහා දායක වීම ආරම්භ කරමු. ඔබට ආරම්භ කළ හැකි පහසු ගැටළු සහිත ව්‍යාපෘති ලැයිස්තුවක් අපි සම්පාදනය කර ඇත්තෙමු. පරීක්ෂා කරන්න [web app ව්‍යාපෘති ලැයිස්තුව](https://firstcontributions.github.io/#project-list). + +### [අතිරේක සම්පත්](../additional-material/git_workflow_scenarios/additional-material.md) + +## වෙනත් මෙවලම් භාවිතා කරන නිබන්ධන + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + diff --git a/translations/README.sindhi.md b/translations/README.sindhi.md new file mode 100644 index 00000000000..26f01f435bd --- /dev/null +++ b/translations/README.sindhi.md @@ -0,0 +1,132 @@ +[![Open Source Love](https://firstcontributions.github.io/open-source-badges/badges/open-source-v1/open-source.svg)](https://github.com/firstcontributions/open-source-badges) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# پهريون تعاون + +اهو ڏکيو آهي. اهو هميشه مشڪل آهي پهريون دفعو توهان ڪجهه ڪيو خاص طور تي جڏهن توهان تعاون ڪري رهيا آهيو ، غلطيون ڪرڻ هڪ آرام واري شيءِ نه آهي. اسان پهريون طريقو کولڻ چاهيون ٿا نئون کليل ذريعو مددگار سکن ٿا ۽ پهريون ڀيرو حصو وٺن ٿا. + +پڙهائي آرٽيڪل ۽ ڏسڻ وارا سبق مدد ڪري سگھن ٿا ، پر اصل ۾ عملي ماحول ۾ شيون ڪرڻ سان سٺو ڇا آهي؟ ھن پروجيڪٽ جو مقصد مقصد مهيا ڪرڻ ۽ آسانيون جوڙيندڙن کي پنھنجي ابتدائي مدد ڪرڻ جو طريقو آھي. جيڪڏھن توھان پنھنجو پھريون حصو بڻائڻ جي ڪوشش ڪري رھيا آھيو ، ھيٺين قدمن تي عمل ڪريو. + +### جيڪڏهن توهان ڪمانڊ لائن سان مطمئن نه آهيو ، [هتي GUI ٽولز استعمال ڪرڻ وارا سبق آهن.] (# سبق استعمال ڪندڙ-ٻئي اوزار) _ + + +#### _ ھن [ٻين ٻولين ۾] پڙھو (ترجما / ترجما. ايم ڊي) ._ + +fork this repository + +#### جيڪڏهن توهان کي پنهنجي مشين تي گٽ نه آهي ، ته [انسٽال ڪريو] (https://help.github.com/articles/set-up-git/). + +## هن مخزن کي سنڀاليو + +هن صفحي جي مٿئين حصي تي فورڪ بٽن تي ڪلڪ ڪري هن مخزن کي دٻايو. +اهو توهان جي اڪائونٽ ۾ هن مخزن جي ڪاپي ٺاهي ڏيندو. + +## مخزن کي کلون + +clone this repository + +هاڻي ڪلون محفوظ ڪيل مخزن کي توهان جي مشين ڏانهن پهچايو. پنھنجي GitHub اڪائونٽ ڏانھن وڃو ، فورڪ ٿيل مخزن کي کوليو ، ڪوڊ واري بٽڻ تي ڪلڪ ڪريو ۽ پوءِ _ ڪپي ڪلپ بورڊ جي آئڪن تي ڪلڪ ڪريو. + +هڪ ٽرمينل کوليو ۽ هيٺيان گٽ ڪمانڊ هلايو. + +" +گٽ کلون ”يو آر ايل توهان ڪاپي ئي ڪئي آهي“ +" + +جتي "صرف توهان يوپي ايل ڪاپي ڪئي آهي" (ڪڻڪ جي نشانين کانسواءِ) هن ريزنزوري ڏانهن يو آر ايل (هن پراجيڪٽ جي ڪانٽ). يو آر ايل حاصل ڪرڻ لاءِ پوئين قدم ڏسو. + +copy URL to clipboard + +مثال طور: + +" +گٽ کلون https://github.com/this-is-you/first-contactions.git +" + +جتي-هي-تون-توهان جو آهي توهان جو GitHub صارف نالو هتي توهان پنهنجي ڪمپيوٽر ڏانهن GitHub تي سڀ کان پهرين شراڪت جي مخزن جو مواد نقل ڪري رهيا آهيو. + +## هڪ شاخ ٺاهيو + +توهان جي ڪمپيوٽر تي مخزن ڊاريڪٽري ۾ تبديل ڪريو (جيڪڏهن توهان پهريان ئي نه آهيو) + +" +سي ڊي پهرين تعاون +" + +ھاڻي شاخ ٺاھيو حڪم "گٽ چيڪ آئوٽ" استعمال ڪندي. + +" +ڏسي چڪاس ڪريو -آب نئون-شاخ-نالو +" + +مثال طور: + +" +گٽ چيڪ آئوٽ -b شامل الونزو-چرچ +" + +(شاخ جو نالو _add_ لفظ شامل ڪرڻ جي ضرورت ناهي ، پر ان ۾ شامل ٿيڻ مناسب ڳالهه آهي ڇاڪاڻ ته هن برانچ جو مقصد توهان جي نالي کي لسٽ ۾ شامل ڪرڻ آهي.) + +## ضروري تبديليون ڪيو ۽ انهن تبديلين کي انجام ڏيو + +ھاڻي ٽيڪسٽ ايڊيٽر ۾ Contributors.md فائل کوليو ، پنھنجو نالو ان ۾ شامل ڪريو. فائل جي شروعات يا آخر ۾ ان کي شامل نه ڪريو. ان کي وچ ۾ ڪٿي به وجھو. ھاڻي ، فائل کي بچايو. + +git status + +جيڪڏهن توهان پروجيڪٽ ڊاريڪٽري ڏانهن وڃو ۽ حڪم کي ختم ڪريو گٽ اسٽيٽس ، توهان ڏسندا ته هتي تبديليون آهن. + +جن شاخن کي توھان ٺاھيو آھي انھن کي شامل ڪريو جيڪي تبديلي آڻي سگھوٿا + +" +git شامل ڪريو Contributors.md +" + +ھاڻي انھن تبديلين کي انجام ڏيو "گٽ ڪمٽ" حڪم استعمال ڪندي: + +" +git commit -m "شرڪت ڪندڙن جي لسٽ ۾ <توھان جو نالو شامل ڪريو" +" + +توهان جي نالي سان "توهان جو نالو" بدلجي ٿو. + +## گٽ هب ۾ پش تبديلين + +پنھنجن تبديلين کي ھٿ سان ڌڪايو "گشت پش": + +" +گٽ پش اصل +" + +توهان جي ٺاهي ڪيل شاخ جي نالي سان "کي تبديل ڪرڻ + +## پنھنجون تبديليون راءِ لاءِ پيش ڪريو + +جيڪڏهن توهان GitHub تي پنهنجي مخزن ڏانهن ويندا آهيو ، توهان ڏسندا "تقابلي ۽ پلڻ واري درخواست" بٽڻ. انهي بٽڻ تي ڪلڪ ڪيو. + +create a pull request + +هاڻي پل جي درخواست جمع ڪر. + +submit pull request + +جلد ئي آئون توهان جي سڀني تبديلين کي ان منصوبي جي ماسٽر برانچ ۾ ضم ڪري ڇڏيندس. توهان جون هڪ ڀيرو اطلاع ملڻ واري اي ميل حاصل ٿيندي هڪ ڀيرو تبديليون ضم ٿي ويون آهن. + +## ڪيڏانهن وڃڻو آهي؟ + +مبارڪون هجن! توهان صرف معياري _فورڪ -> ڪلون -> ايڊٽ ڪيو -> پل درخواست_ ڪم جي وهڪري کي مڪمل ڪيو جنهن سان توهان اڪثر منهن ڏيڻ ۾ مدد ڪندا! + +پنهنجي حصي جو جشن ملهايو ۽ ان کي [ويب ايپ] تي وڃڻ سان پنهنجن دوستن ۽ پوئلڳن سان حصيداري ڪريو (https://firstcontactions.github.io/#social-share). + +جيڪڏهن توهان ڪنهن مدد جي گهرج ۾ يا ڪنهن سوال جي صورت ۾ توهان اسان جي سستي ٽيم ۾ شامل ٿي ويا [سليڪ ٽيم ۾ شامل ٿيو] (https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +هاڻي اچو ته توهان شروع ڪيو ٻين منصوبن ۾ ڀاڙي سان حصو وٺي اسان منصوبن جي هڪ فهرست مرتب ڪئي آهي توهان کي آسان مسئلن تي جيڪي توهان شروع ڪري سگهو ٿا. [ويب ائپ ۾ منصوبن جي فهرست] چيڪ ڪريو (https://firstcontactions.github.io/#project-list). + +### [اضافي مواد] (additional-material/git_workflow_scenarios/extra-material.md) + +## ٻين اوزارن کي استعمال ڪندي سبق + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.sk.md b/translations/README.sk.md new file mode 100644 index 00000000000..77e8bb5cf0f --- /dev/null +++ b/translations/README.sk.md @@ -0,0 +1,125 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Prvý príspevok + +Život je ťažký. Obzvlášť keď niečo robíte prvýkrát. V prípade, že na niečom spolupracujete, nie je robenie chýb niečo, čo by vám robilo radosť. My by sme radi zjednodušili cestu novým prispievateľom do open-source pri ich učení sa ako na to. + +Čítanie článkov alebo zhliadnutie video návodov sú tiež cesty, ale čo je lepšie ako si danú vec priamo ohmatať na vlastnej koži v reálnom prostredí? Tento projekt je zameraný na poskytnutie pomoci začiatočníkom s ich prvým prispením do open-source. Ak ste ním práve vy, nasledujte kroky popísané nižšie. + +#### *Ak nemáte radi príkazový riadok, [tu nájdete návody na použitie nástrojov s GUI (grafické užívateľské rozhranie)](#Návod-za-použitie-ďalších-nástrojov)* + +forknite tento repozitár + +Ak máte nainštalovaný git, [nainštalujte si ho]( https://help.github.com/articles/set-up-git/). + +## Forknite tento repozitár + +Forknite (vytvorenie kópie z originálu, z anglického *fork* - *vidlička*, ako vytvorenie novej odnože) tento repozitár kliknutím na tlačidlo **Fork** hore na tejto stránke. Tým vytvoríte kópiu tohto repozitára na svojom vlastnom GitHib účte. + +## Naklonujte repozitár + +naklonujte tento repozitár + +Teraz naklonujte (anglicky *clone*) forknutý repozitár na váš počítač, naklonovanie nie je nič iné ako stiahnutie obrazu repozitára k vám na počítač. Na vašom GitHub účte si otvoríte forknutý repozitár, kliknite na tlačidlo **Clone or download** a následne v okienku, ktoré sa objaví, kliknite na tlačidlo s ikonkou **copy to clipboard** vedľa URL adresy, čím si ju skopírujete do schránky. + +Teraz otvorte terminál a spustite nasledujúci príkaz: + +```` +git clone "url ktoré ste práve skopírovali" + +```` + +skopírujte adresu do schránky + +Napríklad: + +```` +git clone https://github.com/vas-username/first-contributions.git +```` + +Týmto na svojom počítači vytvoríte priečinok so súbormi daného repozitára. + +## Vytvorte vetvu + +V príkazovom riadku sa prepnite do zložky s repozitárom (ak v nej už nie ste) + +```` +cd first-contributions +```` + +Teraz vytvorte novú vetvu (anglicky *branch*) za použitia príkazu `git checkout`: + +```` +git checkout -b +```` + +Napríklad: +```` +git checkout -b pridanie-mojho-mena +```` + +Meno vetvy by malo vypovedať o tom, čo kód alebo čokoľvek iné do nej pridané bude robiť/vykonávať, prípadne prečo sa daná vec deje. + +## Urobte zmeny a zaznamenajte ich + +Otvorte súbor `Contributors.md` v textovom editore a pridajte do neho svoje meno. Napíšte ho niekam doprostred a súbor uložte. + +git status + +Pokiaľ teraz v príkazovom riadku spustíte príkaz `git status`, uvidíte aké zmeny boli v repozitári vykonané. + +Tieto zmeny do danej vetvy pridáte príkazom `git add`: + +```` +git add Contributors.md +```` + +Zostáva už len potvrdiť (anglicky *commit*) zmeny príkazom `git commit`: + +```` +git commit -m "Add to Contributors list" +```` + +Za prepínač `-m` sa píše čo dané zmeny predstavujú, popis by mal byť jednoduchý ale výstižný. + +## Pretlačte zmeny na GitHub + +Teraz zmeny vykonané lokálne na počítači pretlačíme (anglicky *push*) na GitHub príkazom `git push`: + +```` +git push origin +```` + +## Predložte svoje zmeny na posúdenie + +Pokiaľ sa teraz pozriete do svojho GitHub repozitára, uvidíte tlačidlo **Compare & pull request**. Kliknite naň. + +vytvorte pull request + +Teraz vytvorte žiadosť o pretiahnutie vašej vetvy do originálneho repozitára (anglicky *pull request*). + +potvrďte pull request + +Čoskoro budú správcovia vykonávať zapracovanie vašich zmien do hlavnej (anglicky *master*) vetvy tohto projektu. Až sa do nej vaše zmeny dostanú, dostanete emailové upozornenie. + +## Kam ďalej? + +Blahoželáme! Práve ste dokončili štandardný _fork -> clone -> edit ->_ priebeh práce (anglicky *workflow), s ktorým sa ako prispievateľ do projektov stretnete dennodenne. + +Oslávte svoj prvý príspevok so svojimi priateľmi a nasledovníkmi cez [webovú aplikáciu](https://roshanjossey.github.io/first-contributions/#social-share). + +V prípade, ak by ste mali akékoľvek otázky alebo potrebovali pomoc, môžete sa [pridat k našemu Slack teamu](https://join.slack.com/t/firstcontributors/shared_invite/enQtMzE1MTYwNzI3ODQ0LTZiMDA2OGI2NTYyNjM1MTFiNTc4YTRhZTg4OWZjMzA0ZWZmY2UxYzVkMzI1ZmVmOWI4ODdkZWQwNTM2NDVmNjY). + +Teraz vám už nič nebráni v prispievaní do ostatných projektov. Pripravili sme pre vás zoznam projektov, ktoré majú jednoduché záležitosti na vyriešenie/naprogramovanie, s ktorými môžete začať. Pozrite sa [tu](https://roshanjossey.github.io/first-contributions/#project-list). + +### [Ďalšie materiály](../additional-material/git_workflow_scenarios/additional-material.md) + + +## Návod za použitia ďalších nástrojov + +|GitHub Desktop|Visual Studio 2017|GitKraken|VS Code| +|---|---|---|---| +|[GitHub Desktop](../github-desktop-tutorial.md)|[Visual Studio 2017](../github-windows-vs2017-tutorial.md)|[GitKraken](../gitkraken-tutorial.md )|[Visual Studio Code](../github-windows-vs-code-tutorial.md)| \ No newline at end of file diff --git a/translations/README.sl.md b/translations/README.sl.md new file mode 100644 index 00000000000..1dfd1f90c74 --- /dev/null +++ b/translations/README.sl.md @@ -0,0 +1,121 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Prvi prispevek + +Vsak začetek je težak. Ko sodeluješ z drugimi, so napake še veliko bolj neprijetne. Zato smo se odločili, da novincem olajšamo prispevanje k odprti kodi (ang. Open source). + +Branje člankov in sledenje vodičem lahko pomaga, vendar je še vedno najbolje da nove veščine vadimo sami v varnem okolju. Namen tega projekta je da novince vodi in jim olajša prvi prispevek k odprti kodi. Če želite narediti prvi prispevek, sledite spodnjim korakom. + +Angleški izrazi so v oklepajih, da dodajo kontekst vsebini. + +#### *Če se ne počutite dobro v ukazni vrstici (ang. command line), so tukaj [navodila za uporabo orodij z grafičnim vmesnikom.]( #vodiči-za-uporabo-drugih-orodij )* + + +fork this repository + +Če na svojem računalniku še nimaš "git", si ga [naloži]( https://help.github.com/articles/set-up-git/). + +## Ustvari svojo različico repository-ja ( Fork this repository ) + +S pritiskom na gumb "Fork" na vrhu te strani, ustvari svojo različico repositorya ( pogosto skrajšano v "repo" ) v svojem GitHub računu. + +## Kloniraj ta repository ( Clone the repository ) + +clone this repository + +Sedaj kloniraj ta repository na svoj računalnik. Pojdi v svoj GitHub račun in poišči svojo različico tega repositorya, klikni na gumb "Clone or download" in si kopiraj povezavo. Lahko uporabiš "Ctrl+C" ali pa klikni na ikono na desni strani povezave *copy to clipboard*. + +Odpri terminal in se postavi v direktorij, v katerem želiš imeti svojo kopijo repositorya. Nato zaženi naslednji ukaz: + +``` +git clone "url naslov, ki si ga ravno skopiral" +``` +"url naslov, ki si ga ravno skopiral" (brez navednic) je naslov, ki si ga skopiral na Githubu ( naslov tvoje različice projekta ). Glej prejšne korake da dobiš url naslov. + +copy URL to clipboard + +Primer: +``` +git clone https://github.com/this-is-you/first-contributions.git +``` +`this-is-you` je tvoje GitHub uporabniško ime. Ta ukaz skopira vsebino repositorya "first-contributions" z GitHuba v tvoj računalnik. + +## Ustvari vejo ( Create a branch ) + +Prestavi se v direktorij repositorya na svojem računalniku (če še nisi v njem): + +``` +cd first-contributions +``` +Sedaj ustvari vejo z uporabo ukaza `git checkout`: +``` +git checkout -b +``` + +Primer: +``` +git checkout -b add-janez-novak +``` +(Ni potrebno da je v imenu veje *add*, vendar je v tem primeru smiselno, ker je namen veje da dodaš svoje ime na seznam.) + +## Naredi spremembe in izvedi commmit teh sprememb ( Make necessary changes and commit those changes ) + +Odpri datoteko `Contributors.md` v urejevalniku besedila in dodaj svoje ime. Ne dodajaj ga na začetek ali konec datoteke, dodaj ga nekje vmes. Shrani datoteko. + +git status + +Če se postaviš v direktorij projekta in izvedeš ukaz `git status`, vidiš da obstajajo spremembe v projektu. + + +Dodaj te spremembe veji, ki si jo ravno ustvaril, z ukazom `git add`: + +``` +git add Contributors.md +``` + +Sedaj izvedi commit teh sprememb z ukazom `git commit`: +``` +git commit -m "Add to Contributors list" +``` +Zamenjaj `` s svojim imenom. Tekst med navednicami je komentar spremembe, ki se shrani s spremembo. + +## Pošlji spremembe na GitHub ( Push changes to GitHub ) + +Pošlji svoje spremembe z ukazom `git push`: +``` +git push origin +``` +Zamenjaj `` z imenom veje, ki si jo ustvaril. + +## Vloži svoje spremembe v pregled ( Submit your changes for review ) + +Če preveriš svoj repository na GitHubu, vidiš gumb `Compare & pull request`. Klikni na ta gumb. + +create a pull request + +Sedaj izvedi submit svojega pull requesta. + +submit pull request + +Kmalu bom združil tvoje spremembe v master vejo tega projekta. V svoj e-poštni nabiralnik boš dobil sporočilo, da so bile spremembe združene. + +## Kako nadaljevati? ( Where to go from here? ) + +Čestitke! Pravkar si končal običajni _fork -> clone -> edit -> PR_ potek dela, ki ga boš srečal kot sodelavec v odprto kodnih projektih! + +Lahko se pridružiš naši slack ekipi, če rabiš pomoč ali imaš vprašanja. [Pridruži se slack ekipi](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Sedaj lahko začneš prispevati drugim projektom. Sestavili smo seznam projektov z enostavnimi problemi (issues), ki jih lahko začneš reševati. Preveri [seznam projektov v spletni aplikaciji](https://roshanjossey.github.io/first-contributions/#project-list). + +### [Dodatne informacije](../additional-material/translations/Slovenian/additional-material.sl.md) + + +## Vodiči za uporabo drugih orodij + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.slk.md b/translations/README.slk.md new file mode 100644 index 00000000000..8e62a1f44dc --- /dev/null +++ b/translations/README.slk.md @@ -0,0 +1,121 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Prvé príspevky + +Je to ťažké. Je to vždy ťažké, keď niečo robíš prvýkrát. Najmä vtedy, keď spolupracuješ, robiť chyby nie je pohodlná vec. Chceli sme zjednodušiť spôsob, akým sa noví prispievatelia do open source učia a prispievajú prvýkrát. + +Čítanie článkov a sledovanie tutoriálov môže pomôcť, ale čo je lepšie, ako skutočne robiť veci v skúšobnom prostredí? Cieľom tohto projektu je poskytnúť usmernenie a zjednodušiť spôsob, akým prvýkrát prispievajú začiatočníci. Ak máš záujem o prvý príspevok, postupuj podľa nižšie uvedených krokov. + +#### *Ak sa ti nedarí s príkazovým riadkom, [tu sú návody s nástrojmi grafického rozhrania.]( #návody-pomocou-iných-nástrojov )* + +fork this repository + +Ak nemáš na svojom počítači git, [nainštaluj ho]( https://help.github.com/articles/set-up-git/). + +## Skopíruj toto úložisko + +Skopíruj toto úložisko kliknutím na tlačidlo vidlice(fork) v hornej časti tejto stránky. +Tým sa vytvorí kópia tohto úložiska na tvojom účte. + +## Stiahni toto úložisko + +clone this repository + +Teraz stiahni toto úložisko do tvojho zariadenia. Prejdi do tvojho účtu GitHub, otvor skopírované úložisko, klikni na tlačidlo klonovania a potom klikni na ikonu * kopírovať do schránky *. + +Otvor terminál a spusti nasledujúci git príkaz: + +``` +git clone "adresa, ktorú si práve skopíroval" +``` +kde "adresa ktorú si práve skopíroval" (bez úvodzoviek) je adresa URL tohto úložiska (tvoja kópia tohto projektu). Pozri si predchádzajúce kroky na získanie adresy URL. + +copy URL to clipboard + +Napríklad: +``` +git clone https://github.com/toto-si-ty/prve-prispevky.git +``` +kde `toto-si-ty` je tvoje GitHub užívateľské meno. Tu skopíruješ obsah GitHub úložiska prve-prispevky do tvojho počítača. + +## Vytvor vetvu + +Prejdi do adresára úložiska v tvojom počítači (ak ešte nie si tam): + +``` +cd prve-prispevky +``` +Teraz vytvor vetvu pomocou príkazu `git checkout`: +``` +git checkout -b +``` + +Napríklad: +``` +git checkout -b pridaj-ferko-mrkvicka +``` +(Názov pobočky nemusí obsahovať slovo * pridaj *, ale je rozumné pridať ho, pretože účelom tejto pobočky je pridať tvoje meno do zoznamu.) + +## Vykonaj potrebné zmeny a potvrď tieto zmeny + +Teraz otvor súbor `Contributors.md` v textovom editore a pridaj do neho svoje meno. Nepridávaj ho na začiatok alebo na koniec súboru. Daj ho kdekoľvek medzi tým. Teraz súbor ulož. + +git status + +Ak prejdeš do adresára projektu a vykonáš príkaz `git status`, uvidíš zmeny. + +Pridaj tieto zmeny do vetvy, ktorú si práve vytvoril, pomocou príkazu `git add`: + +``` +git add Contributors.md +``` + +Teraz vykonaj tieto zmeny pomocou príkazu `git commit`: +``` +git commit -m "Pridaj do zoznamu pripievateľov" +``` +nahraď `` tvojim menon. + +## Nahraj zmeny na GitHub + +Nahraj svoje zmeny pomocou príkazu `git push`: +``` +git push origin +``` +nahraď `` názvom vetvy, ktorú si vytvoril skôr. + +## Odošli svoje zmeny na kontrolu + +Ak prejdeš do tvojho úložiska v službe GitHub, zobrazí sa tlačidlo `Compare & pull request`. Klikni na toto tlačidlo. + +create a pull request + +Teraz predlož požiadavku na vytiahnutie. + +submit pull request + + +Čoskoro budem zlučovat všetky vaše zmeny do hlavnej pobočky tohto projektu. Po zlúčení zmien dostaneš upozornenie. + +## Kam ísť odtiaľto? + +Gratulujem! Práve si dokončil štandardný _fork -> klon -> upraviť -> PR_ pracovný postup, ktorý sa často stretneš ako prispievateľ! + +Osláv svoj príspevok a zdieľaj ho so svojimi priateľmi a nasledníkmi [web app](https://roshanjossey.github.io/first-contributions/#social-share). + +Môžeš sa pripojiť k nášmu slack tímu v prípade, že potrebuješ nejakú pomoc alebo máš nejaké otázky. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Teraz začni s účasťou na iných projektoch. Vytvorili sme zoznam projektov s jednoduchými problémami, s ktorými môžeš začať. Pozri [zoznam projektov vo webovej aplikácii](https://roshanjossey.github.io/first-contributions/#project-list). + +### [Dodatočný materiál](../additional-material/git_workflow_scenarios/additional-material.md) + + +## Návody pomocou iných nástrojov + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.sr.md b/translations/README.sr.md new file mode 100644 index 00000000000..3a6c3e4fff6 --- /dev/null +++ b/translations/README.sr.md @@ -0,0 +1,118 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Prvi prilog + +Teško je. Prvi pokušaj je uvek težak. Kada sarađuješ sa drugima, napraviti greške je utoliko strašnije. Želeli bismo da olakšamo proces kroz koji novi programeri koji doprinose otvorenom softveru (eng. open source) uče i doprinose po prvi put. + +Iako blogovi i tutorijali mogu da pomognu, ništa nije bolje nego uzeti stvari u svoje ruke i zaista doprinositi u trening-sredini. Ovaj projekat ima za cilj da pruži konkretne korake i olakša način na koji početnici prilažu svoje prve doprinose (eng. contributions). Ukoliko ste se prepoznali u tekstu iznad, pratite sledeće korake. + + +#### *Ako vam je nezgodno da čitate tekst u komandnoj liniji, [evo linka kroz GUI alate.](#Uputstva-za-druge-alate)* + +Napravite fork repozitorijuma + +Ukoliko nemati git instaliran na vašoj mašini, [instalirajte ga ovde]( https://help.github.com/articles/set-up-git/). + +## Napravite fork repozitorijuma + +Napravite račvanje (fork) tako što ćete kliknuti na dugme *fork* na vrhu stranice. Ovako pravite kopiju repozitorijuma na vašoj strani. + +## Klonirajte repozitorijum + +clone this repository + +Sledeće, klonirajte repozitorijum koji ste prethodno račvali. Posetite svoj GitHub profil, otvorite repozitorijum koji ste račvali, kliknite na *clone* dugme i kliknite na ikonicu *copy to clipboard*. + +Otvorite terminal i upišite sledeće git komande: + +``` +git clone "url you just copied" +``` +Umesto "url you just copied" (bez navodnika i razmaka) upišite url repozitorijuma koji ste kopirali u prethodnom koraku. + +copy URL to clipboard + +Na primer: +``` +git clone https://github.com/this-is-you/first-contributions.git +``` +Gde je umesto `this-is-you` upisano vaše korisničko ime. Ovim kopirate sadržaj repozitorijuma *first-contributions* na vašu mašinu. + +## Pravljenje grane *branch* + +Prebacite se u radni direktorijum na vašoj mašini: +``` +cd first-contributions +``` +Pa zatim napravite novo grananje *branch* koristeći `git checkout` comandu: +``` +git checkout -b +``` + +Na primer: +``` +git checkout -b add-alonzo-church +``` +(Naziv grane ne mora da sadrži *add* na početku, ali je zgodno uključiti ga jer je svrha ove grane da doda vaše ime na listu. + +## Napravite potrebne izmene i potvrdite promene + +Otvorite `Contributors.md` fajl u tekst editoru i dodajte vaše ime. Nemojte dodavati ime na sam početak ili kraj. Stavite ga negde u sredinu. Potom sačuvajte fajl. + +git status + +Ukoliko odete u radni direktorijum i izvršite komandu `git status`,primetićete da postoje promene. + +Dodajte ove promene u granu koju ste gore napravili koristeći `git add` komandu: + +``` +git add Contributors.md +``` + +Sada potvrdite ove promene koristeći `git commit` komandu: +``` +git commit -m "Add to Contributors list" +``` +Gde umesto `` upisujete svoje ime. + +## Push changes to GitHub + +Pošaljite izmene u repozitorijum na GitHub nalogu `git push`: +``` +git push origin +``` +gde umesto `` stavljate ime vašeg grananja. + +## Pošaljite izmene na reviziju + +Ukoliko odete na repozitorijum na vašem GitHub nalogu primetićete `Compare & pull request` Dugme. Kliknite na njega. + +create a pull request + +a potom pošaljite zahtev klikom na dugme *submit*. + +submit pull request + +Nakon toga, ja ću spojiti promene koje ste napravili sa master granom projekta. Dobićete mejl potvrde kada se grane spoje. + +## Šta dalje? + +Čestitamo! Završili ste standardni _fork -> clone -> edit -> PR_ tok koji će vas pratiti kroz vaš čitav programerski život! + +Proslavite tako što ćete podeliti vaš doprinos sa prijateljima i pratiocima otvaranjem [stranice](https://firstcontributions.github.io/#social-share). + +Pridružite se i našem Slack timu u slučaju da vam je potrebna ikakva pomoć ili imate bilo kakvih pitanja. [Slack tim](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +A sada, možemo početi sa doprinosima drugim projektima. Napravili smo spisak projekata sa jednostavnim problemima na kojima možete početi da radite. Posetite stranicu sa [the list of projects na našem sajtu](https://firstcontributions.github.io/#project-list). + +### [Dodatni materijali](../additional-material/git_workflow_scenarios/additional-material.md) + +## Uputstva za druge alate + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.ta.md b/translations/README.ta.md new file mode 100644 index 00000000000..a4b0fb25936 --- /dev/null +++ b/translations/README.ta.md @@ -0,0 +1,143 @@ +[![Open Source Love](https://firstcontributions.github.io/open-source-badges/badges/open-source-v1/open-source.svg)](https://github.com/firstcontributions/open-source-badges) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# முதல் பங்களிப்புகள் + +நீங்கள் ஏதாவது ஒன்றை முதல் முறை செய்யும் போது அது எப்போதுமே கடினமாக தான் இருக்கும். +குறிப்பாக, நீங்கள் குழுவாக சேர்ந்து வேலை செய்யும் போது, தவறு செய்துவிட்டால் அது மிகவும் +வருத்தம் அளிக்கக்கூடியாதாக இருக்கும். ஆகையால், திறந்த மூல மென்பொருள் +(open-source software) பங்களிப்பாளர்களாக எவ்வாறு செயலாற்ற வேண்டும் என்பதையும் +அதில் முதல் முறையாக பங்களிப்பு செய்வதை எளிதாக்குவதுமே எங்கள் நோக்கம். + +கட்டுரைகளைப் படிப்பதும், பயிற்சிகளைப் பார்ப்பதும் உதவக்கூடும், ஆனால் நடைமுறைச் சூழலில் +செய்முறையாகச் செய்வதை விட சிறந்தது என்ன? இந்த திட்டம் வழிகாட்டுதல்களை வழங்குவதையும், +ஆரம்பநிலை பங்களிப்பாளர்களை அவர்களின் முதல் பங்களிப்பை எளிதாக்குவதையும் நோக்கமாகக் +கொண்டுள்ளது. உங்கள் முதல் பங்களிப்பை வழங்க விரும்பினால், கீழே உள்ள வழிமுறைகளை +பின்பற்றவும். + +#### *command line tool உங்களுக்கு வசதியாக இல்லை என்றால், [இங்கே GUI tools ஐ பயன்படுத்தி பயிற்சிகள் உள்ளன.](#பிற-கருவிகளைப்-பயன்படுத்தி-பயிற்சிகள்)* + +இந்த repository ஐ fork செய்யவும் + +உங்கள் கணினியில் git இல்லை என்றால், [install செய்யவும்](https://help.github.com/articles/set-up-git/). + +## இந்த repository ஐ fork செய்தல் + + +இந்த பக்கத்தின் மேலே உள்ள fork பொத்தானைக் கிளிக் செய்வதன் மூலம் செயட்படுத்தலாம். +இது உங்கள் account இல் ஒரு copy ஐ உருவாக்கும். + +## இந்த repository ஐ clone செய்தல் + +இந்த repository ஐ clone செய்யவும் + +இப்போது உங்கள் கணினியில் fork செய்யப்பட்ட repository ஐ clone செய்யவும். உங்கள் GitHub கணக்கிற்குச் சென்று, forked செய்யப்பட்ட repository ஐ open செய்து clone பொத்தானைக் கிளிக் செய்து copy to clipboard கிளிக் செய்வதன் மூலம் நிறைவேற்றலாம். + +*terminal* அல்லது *command prompt* ஐ open செய்து பின்வரும் git கட்டளையை இயக்கவும்: + +``` +git clone "நீங்கள் copy செய்த url" +``` + +copy URL to clipboard + + +உதாரணத்திற்கு: + +``` +git clone https://github.com/இது நீங்கள்/first-contributions.git +``` + +இங்கு `இது நீங்கள்` என்பது GitHub username என்பதாகும். இதன் மூலம் நீங்கள் first-contributions repository இன் பிரதி ஒன்றை உங்கள் GitHub கணக்கில் செயட்படுத்துகிறீர்கள். + +## கிளையொன்றை உருவாக்குதல் + +repository directory க்கு செல்லவும் (நீங்கள் ஏற்கனவே அங்கு இல்லையென்றால்): + +``` +cd first-contributions +``` + + +இப்போது `git checkout` கட்டளையைப் பயன்படுத்தி ஒரு கிளையை உருவாக்கவும்: + +``` +git checkout -b <உங்கள்-கிளையின்-பெயர்> +``` + +உதாரணத்திற்கு: + +``` +git checkout -b உங்கள்-கிளையின்-பெயர் +``` + +(கிளையின் பெயருக்கு அதில் *add* சேர்க்க வேண்டிய அவசியமில்லை, ஆனால் இது ஒரு நியாயமான விஷயம், ஏனெனில் இந்த கிளையின் நோக்கம் உங்கள் பெயரை ஒரு பட்டியலில் சேர்ப்பதுதான்.) + +## தேவையான மாற்றங்களைச் செய்து அந்த மாற்றங்களை commit செய்யுங்கள் + +இப்போது *text editor* அல்லது *notepad* இல் `Contribitors.md` கோப்பைத் திறந்து, அதில் உங்கள் பெயரைச் சேர்க்கவும். கோப்பின் தொடக்கத்திலோ அல்லது முடிவிலோ இதைச் சேர்க்க வேண்டாம். இடையில் எங்கும் வைக்கவும். இப்போது, ​​கோப்பை சேமிக்கவும். + +git status + +நீங்கள் project directory சென்று `git status` இயக்கினால், மாற்றங்கள் இருப்பதை நீங்கள் காண்பீர்கள். + + +`git add` கட்டளையைப் பயன்படுத்தி நீங்கள் உருவாக்கிய கிளையில் அந்த மாற்றங்களைச் சேர்க்கவும்: + +``` +git add Contributors.md +``` + +இப்போது `git commit` கட்டளையைப் பயன்படுத்தி அந்த மாற்றங்களைச் செய்யுங்கள்: + +``` +git commit -m "Add <உங்கள்_பெயர்> to Contributors list" +``` + +`உங்கள்_பெயர்` என்ற இடத்தில் உங்கள் பெயரை கொடுங்கள். + +## மாற்றங்களை GitHub இட்கு push செய்தல் + +`git push` கட்டளையைப் பயன்படுத்தி உங்கள் மாற்றங்களைத் தள்ளுங்கள்: + +``` +git push origin <உங்கள்-கிளையின்-பெயர்> +``` + + +`<உங்கள்-கிளையின்-பெயர்>` ஐ நீங்கள் முன்பு உருவாக்கிய கிளையின் பெயருடன் மாற்றுங்கள். + +## உங்கள் மாற்றங்களை மதிப்பாய்வுக்கு சமர்ப்பிக்கவும் + + +GitHub இல் உள்ள உங்கள் களஞ்சியத்திற்குச் சென்றால், `Compare & pull request` கோரிக்கை பொத்தானைக் காண்பீர்கள். அந்த பொத்தானைக் கிளிக் செய்க. + +create a pull request + +இப்போது இழுக்கும் கோரிக்கையை சமர்ப்பிக்கவும். + +submit pull request + +விரைவில் உங்கள் எல்லா மாற்றங்களையும் இந்த திட்டத்தின் முதன்மை கிளையில் இணைக்கப்படும். மாற்றங்கள் ஒன்றிணைக்கப்பட்டவுடன் உங்களுக்கு அறிவிப்பு மின்னஞ்சல் கிடைக்கும். + +## இங்கிருந்து எங்கு செல்வது? + +வாழ்த்துக்கள்! நீங்கள் ஒரு பங்களிப்பாளராக அடிக்கடி சந்திக்கும் _fork -> clone -> edit -> PR_ பணிப்பாய்வு முடித்துவிட்டீர்கள். + + +உங்கள் பங்களிப்பைக் கொண்டாடுங்கள் மற்றும் உங்கள் நண்பர்கள் மற்றும் பின்தொடர்பவர்களுடன் [web app](https://firstcontributions.github.io/#social-share) சென்று பகிர்ந்து கொள்ளுங்கள். + +உங்களுக்கு ஏதேனும் உதவி தேவைப்பட்டால் அல்லது ஏதேனும் கேள்விகள் இருந்தால் எங்கள் slack team இல் இணையலாம். [Join our slack crew](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).. + +இப்போது மற்ற திட்டங்களுக்கு பங்களிப்பதன் மூலம் தொடங்குவோம். நீங்கள் தொடங்கக்கூடிய எளிதான சிக்கல்களுடன் திட்டங்களின் பட்டியலை நாங்கள் தொகுத்துள்ளோம். பாருங்கள் [the list of projects in the web app](https://firstcontributions.github.io/#project-list). + +### [கூடுதல் வளங்கள்](../additional-material/git_workflow_scenarios/additional-material.md) + +## பிற கருவிகளைப் பயன்படுத்தி பயிற்சிகள் + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.te.md b/translations/README.te.md new file mode 100644 index 00000000000..05d40452d23 --- /dev/null +++ b/translations/README.te.md @@ -0,0 +1,119 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# మొదటి విరాళములు + +అది కష్టం. అది ఏదో మొదటిసారి ఎల్లప్పుడూ కష్టం. ముఖ్యంగా మీరు సహకరించినప్పుడు, తప్పులు చేయడం అనేది ఒక సౌకర్యవంతమైన విషయం కాదు. కొత్త ఓపెన్ సోర్స్ కంట్రిబ్యూటర్లను తెలుసుకోవడానికి & మొదటిసారిగా దోహదపడే విధంగా మేము సరళీకృతం చేయాలనుకుంటున్నాము. + +వ్యాసాలు చదవడం & చూడటం ట్యుటోరియల్స్ సహాయపడతాయి, కానీ వాస్తవంగా ఆచరణాత్మక వాతావరణంలో stuff చేస్తున్నదాని కంటే మెరుగైనది ఏమిటి? మార్గదర్శిని అందించడం మరియు ప్రారంభకులకు వారి మొదటి సహకారాన్ని సులభతరం చేయడం ఈ ప్రాజెక్ట్ లక్ష్యం. మీరు మీ మొదటి సహకారం చేయాలని చూస్తే, క్రింది దశలను అనుసరించండి. + +#### *మీకు ఆదేశ పంక్తితో సౌకర్యంగా లేకపోతే, [ఇక్కడ GUI సాధనాలను ఉపయోగించి ట్యుటోరియల్స్ ఉన్నాయి.](#ఇతర-సాధనాలను-ఉపయోగించి-ట్యుటోరియల్స్)* + + + + +fork this repository + +మీకు మీ కంప్యూటరులో GIT లేకపోతే, [దీనిని ఇన్స్టాల్ చేయండి]( https://help.github.com/articles/set-up-git/). + +## ఫోర్క్ ఈ రిపోజిటరీ + +ఫోర్క్ ఈ రిపోజిటరీ ఈ పేజీ ఎగువ భాగంలో ఫోర్క్ బటన్ పై క్లిక్ చేయడం ద్వారా క్లిక్ చేయండి. +ఇది మీ ఖాతాలో ఈ రిపోజిటరీ కాపీని సృష్టిస్తుంది. + +## రిపోజిటరీ క్లోన్ + +clone this repository + +ఇప్పుడు మీ కంప్యూటరులో ఫోర్క్ రిపోను క్లోన్ చేయండి. మీ GitHub ఖాతాకు వెళ్లండి, ఫోర్క్ రెపోని తెరిచి, క్లోన్ బటన్పై క్లిక్ చేసి, ఆపై * కాపీ * క్లిప్బోర్డ్కు క్లిక్ చేయండి. + +టెర్మినల్ తెరిచి కింది git ఆదేశాన్ని అమలు చేయండి: +``` +git clone "url మీరు కాపీ చేసారు" +``` +ఇక్కడ "url మీరు కాపీ" (కోట్ మార్కులు లేకుండా) ఈ రిపోజిటరీ కు URL (ఈ ప్రాజెక్టు మీ ఫోర్క్). Url ను పొందడానికి మునుపటి దశలను చూడండి. +copy URL to clipboard + +ఉదాహరణకి: +``` +git clone https://github.com/this-is-you/first-contributions.git +``` +ఇక్కడ 'this-is-you' మీ GitHub వినియోగదారు పేరు. ఇక్కడ మీరు మొదటి-రచన రిపోజిటరీ యొక్క కంటెంట్లను GitHub లో మీ కంప్యూటర్కు కాపీ చేస్తున్నారు. + +## ఒక శాఖను సృష్టించండి + +మీ కంప్యూటర్లో రిపోజిటరీ డైరెక్టరీకి మార్చండి (మీరు ఇప్పటికే లేకపోతే): + +``` +cd first-contributions +``` +ఇప్పుడు 'git checkout' ఆదేశం ఉపయోగించి ఒక శాఖను సృష్టించండి: + + +ఉదాహరణకి: +``` +git checkout -b add-alonzo-church +``` +(బ్రాంచ్ యొక్క పేరు దానిలో పదం * add * ను కలిగి ఉండవలసిన అవసరం లేదు, కానీ చేర్చడానికి సహేతుకమైన విషయం ఎందుకంటే ఈ శాఖ యొక్క ఉద్దేశ్యం జాబితాకు మీ పేరును జోడించడం.) + +## అవసరమైన మార్పులు చేసి, ఆ మార్పులను నిరూపించండి + +టెక్స్ట్ ఎడిటర్లో ఇప్పుడు ఓపెన్ `Contributors.md` ఫైల్, దానికి మీ పేరుని జోడించండి. ఫైల్ ప్రారంభంలో లేదా ముగింపులో జోడించవద్దు. మధ్యలో ఎక్కడైనా ఉంచండి. ఇప్పుడు, ఫైల్ను సేవ్ చేయండి. + +git status + + +మీరు ప్రాజెక్ట్ డైరెక్టరీకి వెళ్లి `git status` ఆదేశాన్ని అమలు చేస్తే, మార్పులు ఉన్నాయి అని మీరు చూస్తారు. + +`Git add` కమాండ్ను ఉపయోగించి మీరు సృష్టించిన బ్రాంచ్లో ఈ మార్పులను జోడించండి: +``` +git add Contributors.md +``` + +ఇప్పుడు ఆ మార్పులను 'git commit' ఆదేశం ఉపయోగించి కట్టుకోండి: +``` +git commit -m "Add to Contributors list" +``` +`` తొలగించు మరియు మీ పేరును జోడించండి. + +## మార్పులను GitHub కు పంపండి + +కమాండ్ ఉపయోగించి మీ మార్పులను పంపండి `git push`: +``` +git push origin +``` +మీరు ముందుగా సృష్టించిన బ్రాంచీ పేరుతో `` ను జోడించుము. + +## సమీక్ష కోసం మీ మార్పులను సమర్పించండి + +మీరు GitHub లో మీ రిపోజిటరీకి వెళ్లినట్లయితే, మీరు 'Compare & pull request' బటన్ను చూస్తారు. ఆ బటన్పై క్లిక్ చేయండి. + +create a pull request + +ఇప్పుడు పుల్ అభ్యర్థనను సమర్పించండి. + +submit pull request + +త్వరలో నేను మీ అన్ని మర్పులను ఈ ప్రాజెక్ట్ యొక్క ప్రధాన విభాగానికి విలీనం చేస్తాను. మార్పులు విలీనం అయిన తర్వాత మీరు ఒక నోటిఫికేషన్ ఈమెయిల్ పొందుతారు. + +## ఇక్కడ నుండి ఎక్కడికి వెళ్లాలి? + +అభినందనలు! మీరు standard _fork -> clone -> edit -> PR_ workflow పూర్తి చేసాడు. + +మీ సహకారాన్ని జరుపుకుంటారు మరియు మీ స్నేహితులు మరియు అనుచరులతో దీన్ని [web app](https://roshanjossey.github.io/first-contributions/#social-share) కు వెళ్లండి. + +మీరు ఏ సహాయం అవసరం లేదా ఏవైనా ప్రశ్నలు ఉంటే మీరు మా స్లాక్ జట్టులో చేరవచ్చు. [స్లాక్ జట్టులో చేరండి](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) + +ఇప్పుడు మీరు ఇతర ప్రాజెక్టులకు తోడ్పడటం ప్రారంభించండి. మీరు ప్రారంభించగల సులభమైన సమస్యలతో ప్రాజెక్టుల జాబితాను మేము సంకలనం చేసాము. [వెబ్ ప్రాజెక్టుల జాబితాలు](https://roshanjossey.github.io/first-contributions/#project-list) ను చూడండి. + +### [అదనపు విషయం](../additional-material/git_workflow_scenarios/additional-material.md) + + +## ఇతర సాధనాలను ఉపయోగించి ట్యుటోరియల్స్ + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.th.md b/translations/README.th.md new file mode 100644 index 00000000000..a93d9acf3a0 --- /dev/null +++ b/translations/README.th.md @@ -0,0 +1,119 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# "Contribute" ผลงานใน GitHub กับผู้อื่นเป็นครั้งแรกใช่ไหม? + +มันเป็นเรื่องยาก, ครั้งแรกของทุกอย่างมันมักจะยากเสมอแหละ โดยเฉพาะการทำงานร่วมกับผู้อื่น เมื่อเราทำอะไรผิดพลาดเรามักจะรู้สึกไม่สบายใจ แต่โอเพนซอร์ส (open source) คือโลกของการทำงานร่วมกัน ! เราจึงอยากให้ผู้ที่เข้ามาใหม่ได้เรียนรู้วิธีการ "คอนทริบิ้วต์" ผลงานร่วมกับผู้อื่นใน GitHub แบบง่าย ๆ + +การอ่านบทความและการทำตามตัวอย่างต่าง ๆ ก็อาจจะช่วยได้ แต่จะมีอะไรดีไปกว่าการที่เราได้ลงมือทำสิ่งนั้น ๆ ด้วยตัวเองล่ะ ! โปรเจ็คนี้จะสอนให้มือใหม่ส่ง "คอนทริบิ้วชั่นครั้งแรก" ได้อย่างง่าย ๆ + +จำเอาไว้ว่า: ทำใจให้สบาย ยิ่งคุณผ่อนคลายมากเท่าไหร่ คุณก็ยิ่งเรียนรู้ได้ดีมากขึ้นเท่านั้น ! + +ถ้าคุณอยากร่วมส่งคอนทริบิ้วชั่นครั้งแรกของคุณ เพียงแค่ทำตามขั้นตอนง่าย ๆ ด้านล่าง เราบอกเลยว่า มันจะสนุกแน่นอน + +fork this repository + +ถ้าหากคุณยังไม่ได้ติดตั้ง git ลงบนเครื่องของคุณ คุณสามารถ[ติดตั้งได้ที่นี่]( https://help.github.com/articles/set-up-git/ ) + +## กด "Fork" โปรเจ็คนี้ + +โปรเจ็คหลักนี้ จะเรียกว่า โปรเจ็คต้นน้ำ คุณสามารถแยกโปรเจ็คต้นน้ำออกไปทำที่แอคเคาน์ส่วนตัวของคุณได้ โดยการกดปุ่ม "Fork" ที่ด้านบนของหน้านี้ + +แล้วโปรเจ็คต้นน้ำจะถูกคัดลอกนำไปใส่ไว้ในแอคเคาน์ของคุณ + +## กด "Clone" โปรเจ็คนี้ + +clone this repository + +เอาล่ะ ตอนนี้ก็ Clone โปรเจ็คนี้ลงบนเครื่องคอมพิวเตอร์ของคุณ โดยการคลิ๊กที่ปุ่ม "Clone" แล้วเลือก *Copy to clipboard* (คำสั่งคัดลอก) + +เปิดโปรแกรมเทอร์มินอลในเครื่อง (เช่น Terminal ใน MacOS หรือ cmd ใน Windows) แล้วรันคำสั่ง git ต่อไปนี้: + +``` +git clone "url ที่คัดลอกไว้" +``` +"url ที่คัดลอกไว้" (ไม่ต้องใส่ " ") คือ url ของโปรเจ็คของคุณ คุณสามารถเลื่อนกลับไปดูวิธีการคัดลอก url ได้จากหัวข้อก่อนหน้านี้ + +copy URL to clipboard + +ตัวอย่าง: +``` +git clone https://github.com/this-is-you/first-contributions.git +``` +`this-is-you` คือชื่อ username ของคุณบน GitHub ถึงตรงนี้คุณได้ "Clone" โปรเจ็ค first-contributions ไปไว้ที่คอมพิวเตอร์ของคุณแล้ว + +## สร้าง branch + +ในโปรแกรมเทอร์มินอล เปลี่ยน directory ไปยังที่ที่คุณได้ Clone โปรเจ็คไว้: + +``` +cd first-contributions +``` +ตรงนี้ให้สร้าง branch (แตกกิ่งการทำงานใหม่) ด้วยคำสั่ง `git checkout`: +``` +git checkout -b <ชื่อ branch> +``` + +ตัวอย่าง: +``` +git checkout -b add-alonzo-church +``` +(ปกติชื่อของ branch ไม่จำเป็นต้องมีคำว่า *add* แต่ในโปรเจ็คนี้อยากให้ใช้ add-ชื่อ-ของ-คุณ เพราะชื่อของคุณจะไปแสดงอยู่ในรายชื่อ Contributors (ผู้เข้าร่วม) ของโปรเจ็คนี้ + +## เพิ่มหรือลดโค้ดลงไปเลย แล้วอย่าลืม "Commit" บอกว่าคุณได้เปลี่ยนอะไรไปบ้างล่ะ + +ตอนนี้ให้เปิดไฟล์ `Contributors.md` ในโปรแกรม text editor เพิ่มชื่อของคุณลงไป จากนั้นเซฟไฟล์ + +git status + +ในโปรแกรมเทอร์มินอล ถ้าคุณอยู่ที่ directory ของโปรเจ็ค ให้ลองพิมพ์คำสั่ง `git status` จะเห็นว่าคุณได้ทำการเปลี่ยนอะไรไปบ้าง + +เพิ่มการเปลี่ยนแปลงนั้น ๆ เข้าไปใน branch ที่เพิ่งสร้าง ด้วยคำสั่ง `git add`: +``` +git add Contributors.md +``` + +ตอนนี้ "Commit" การเปลี่ยนแปลงนั้น ๆ ด้วยคำสั่ง `git commit`: +``` +git commit -m "Add <ชื่อของคุณ> to Contributors list" +``` +แทนที่ `<ชื่อของคุณ>` ด้วยชื่อจริง ๆ ของคุณ. + +## "Push" โค้ดที่เปลี่ยนไปขึ้นบน GitHub + +"Push" ผลงานที่คุณทำเมื่อกี้นี้ขึ้น GitHub ด้วยคำสั่ง `git push`: +``` +git push origin <ชื่อ branch ของคุณ> +``` +แทนที่ `<ชื่อ branch ของคุณ>` ด้วยชื่อของ branch ของคุณที่เพิ่งสร้างไปเมื่อหัวข้อที่แล้ว ๆ (add-ชื่อ-ของ-คุณ) + +## ส่งผลงานของคุณและรอรีวิวจากเจ้าของโปรเจ็ค + +ไปที่ repository ของคุณบน GitHub คลิ๊กที่ `Compare & pull request` + +create a pull request + +ตอนนี้ก็ส่ง Pull Request ไปที่โปรเจ็คต้นน้ำได้เลย + +submit pull request + +แล้วเดี๋ยวเราจะ "Merge" หรือรวมผลงานที่คุณได้เปลี่ยนแปลงโค้ดมาที่ master branch ของโปรเจ็คนี้ คุณจะได้รับอีเมลล์ เมื่อเราได้ทำการ Merge ผลงานของคุณเรียบร้อยแล้ว + +## ไปไหนต่อดีหลังจากนี้? +ยินดีด้วย คุณเพิ่งทำวัฏจักรพื้นฐานของการทำ contribute คือ fork -> clone -> edit -> pull request ซึ่งสิ่งเหล่านี้คุณจะพบเจอเป็นปกติเมื่อเป็น contributor +ฉลองการมีส่วนร่วมของคุณ จากนั้นก็แบ่งปันให้เพื่อน ๆ ได้ทราบ โดยการไปที่ [หน้าเว็บนี้](https://roshanjossey.github.io/first-contributions/#social-share) + +หรือจะมาร่วมสนทนากับเราผ่าน Slack ในกรณีที่คุณต้องการความช่วยเหลือ หรือมีข้อสงสัยใด ๆ [เข้าร่วม slack กับเรา](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) + +จากนี้คุณสามารถคอนทริบิ้วต์ให้กับโครงการอื่น ๆ ได้ โดยเราได้สร้างรายการบางส่วน เพื่อให้ง่ายต่อการเริ่มต้น [รายชื่อโครงการที่น่าสนใจ](https://roshanjossey.github.io/first-contributions/#project-list) + +### [ข้อมูลอื่น ๆ เพิ่มเติม](../additional-material/git_workflow_scenarios/additional-material.md) + +## ฝึกการคอนทริบิ้วต์โดยใช้เครื่องมืออื่น ๆ + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + diff --git a/translations/README.tl.md b/translations/README.tl.md new file mode 100644 index 00000000000..41033ab6edf --- /dev/null +++ b/translations/README.tl.md @@ -0,0 +1,124 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Mga unang kontribusyon + +Mahirap. Laging mahirap sa unang beses ng anumang gawain. Lalo na sa isang kolaborasyon, kung saan hindi komportableng paglaanan ng tuon ang mga pagkakamali. Gusto naming simplehan at linawin ang modernong pamamaraan kung papaanong matuto at tumulong ang mga bagong *open-source contributors*. + +Maaaring makatulong ang pagbabasa ng mga artikulo at panonood ng mga *tutorials*, pero ano pa bang mas epektibong pamamaraan kaysa sa aktual na aplikasyon ng isang pagsasanay? Ang pangunahing pakay ng proyektong ito ay gabayan ang mga baguhan na gawin ang kanilang unang *contribution*. Kung ikaw ay isa sa mga taong iyon, sundin lang ang mga sumusunod na tagubilin. + +#### *Kung hindi ka komportable na gumamit ng *command line*, [ito ay mga tutorials gamit ang mga *GUI* tools.](#Mga-tutorials-gamit-ang-ibang-tools)* + + +fork this repository + +Kung hindi naka-*install* ang *git* sa iyong kompyuter, [i-install mo](https://help.github.com/articles/set-up-git/). + +## I-fork ang repository + +I-fork ang *repository* sa pamamagitan ng pag-click ng *fork* *button* na matatagpuan sa bandang itaas na kanan ng *webpage* na ito. +Magkakaroon na ng kopya ng *repository* na ito sa iyong account. + +## I-clone ang repository + +clone this repository + +Ngayon, i-clone ang ngayong na-forked na repository sa iyong kompyuter. Pumunta lang sa iyong GitHub account, buksan ang nai-forked na repository, i-click ang clone button pagkatapos i-click ang *copy to clipboard* icon. + +Buksan ang terminal at i-enter ang sumusunod na git command: + +``` +git clone "url na nakopya mo" +``` +kung saan ang "url na nakopya mo" (wala ang mga panipi) ay ang URL ng repository (ang fork ng iyong proyekto). Pakitingnan nang mabuti ang mga nakaraang hakbang upang makuha ang url. + +copy URL to clipboard + +Halimbawa: +``` +git clone https://github.com/iyong-username/first-contributions.git +``` +kung saan ang `iyong-username` ang iyong username sa GitHub. Mula sa command na ito, dito nagsisimula ng paggawa ng kopya ng nilalaman ng first-contributions repository mula sa GitHub papunta sa iyong kompyuter. + +## Gumawa ng isang branch + +Pumunta sa kompyuter directory ng iyong repository (kung hindi ka pa nakapunta): + +``` +cd first-contributions +``` +Ngayon, gumawa na ng isang branch gamit ang `git checkout` command: +``` +git checkout -b +``` + +Halimbawa: +``` +git checkout -b dagdag-juan-dela-cruz +``` +(Hindi kailangan ng salitang *"dagdag"* sa pangalan ng i-dadagdag na branch pero makatwiran pa rin na gawin dahil layunin ng branch ang pagdagdag ng iyong pangalan sa isang listahan.) + +## Gumawa ng kinakailangan na pagbabago at i-commit ang mga natukoy na pagbabago + +Ngayon, buksan ang `Contributors.md` file sa isang text editor, idagdag ang iyong pangalan. Huwag mong idagdag sa simula o sa hulian ng tinutukoy na file. Ilagay sa kalagitnaan ng file. At i-save and file. + +git status + + +Kung pumunta ka sa directory ng iyong proyekto at i-enter ang command na `git status`, may makikita kang mga pagbabago. + + +Idagdag ang mga pagbabagong naganap papunta sa iyong branch gamit ang `git add` command: + +``` +git add Contributors.md +``` + +Ngayon, i-commit ang mga nabagong files gamit ang `git commit` command: +``` +git commit -m "Add to Contributors list" +``` +kung saan ang `` ay ang iyong pangalan. + +## I-push ang mga changes sa GitHub + +I-push ang mga nabago mong files gamit ang command na `git push`: +``` +git push origin +``` +kung saan ang `` ay ang pangalan ng branch na naidagdag mo kani-kanila lang. + +## I-submit ang changes para sa review + +Pumunta sa iyong repository sa GitHub at may makikita kang `Compare & pull request` button, i-click mo ang tumutukoy na button. + +create a pull request + +I-submit ang pull request. + +submit pull request + +Mga oras na nakalipas at sasamahin ko ang mga pagbabago na nagawa mo papunta sa master branch ng proyekto na ito. May makukuha kang notification email kapag ang mga pagbabago ay na-isama sa proyekto. + +## Saan na mula rito? + +Congrats! Nakumpleto mo ang standard _fork -> clone -> edit -> PR_ na workflow na laging mong makakasalamuha bilang isang kontribyutor! + +I-celebrate ang iyong kontribusyon at i-share mo sa mga kaibigan at followers mo sa pagpunta sa [web app](https://firstcontributions.github.io/#social-share). + +Puwede ka rin sumama sa aming Slack team kung kailangan mo ng karagdagan tulong o gustong magtanong. [Sumama sa aming Slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Ngayon, magsimula ka na mag-contribute sa ibang proyekto. Nagtipon kami ng listahan ng mga proyekto na may madaling issues na puwedeng-puwede kang makisabay. Paki-visit lang [ang listahan mula sa web app](https://firstcontributions.github.io/#project-list). + +### [Mga karagdagan na materyal](../additional-material/git_workflow_scenarios/additional-material.md) + + +## Mga tutorials gamit ang ibang tools + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + diff --git a/translations/README.tr.md b/translations/README.tr.md new file mode 100644 index 00000000000..32296abe105 --- /dev/null +++ b/translations/README.tr.md @@ -0,0 +1,134 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# İlk katkılar + +Zor gelir. Bir işi ilk kez yapmak her zaman zor gelir. Özellikle birileriyle işbirliği içindeyseniz, hata yapmak içinize sinmez. Fakat açık kaynağın temelinde işbirliği ve birlikte çalışma yatar. Biz açık kaynak projelere ilk kez katkıda bulunacak kişilerin süreci öğrenmesini ve ilk katkılarını sunmalarını kolaylaştırmak istiyoruz. + +Makale okumak ve eğitim videoları izlemek yardımcı olabilir, fakat bir işi gerçekten yapmanın yerini ne tutabilir ki? Bu proje yeni başlayanların veya ilk defa katkıda bulunacakların işini kolaylaştırmak ve onlara rehberlik etmek amacındadır. Unutmayın ki ne kadar rahat olursanız o kadar rahat öğrenirsiniz. Eğer bir GitHub projesine ilk defa katkıda bulunacaksanız, aşağıda gösterilen basit adımları izlemeniz yeterli olacaktır. Söz veriyoruz, eğlenceli olacak. + +fork this repository + +Eğer bilgisayarınızda git kurulu değil ise, [ yükleyin ]( https://help.github.com/articles/set-up-git/ ). + +## Projeyi "çatallama" + +Sayfanın sağ üst köşesinde bulunan "Fork" butonuna basıp bu projeyi çatallayın. +Bu işlem sizin hesabınız altında projenin bir kopyasını oluşturacaktır. + +## Depoyu (Repository) klonlama + +clone this repository + +Şimdi bu depoyu bilgisayarınıza klonlayın. GitHub hesabınıza gidin, çatalladığınız depoyu açın, 'clone' butonuna basıp ardından *copy to clipboard* ikonuna basın. + +Daha sonra komut istemini açıp aşağıdaki git komutunu çalıştırın: + +``` +git clone "kopyaladığınız-url" +``` +"kopyaladığınız-url" (tırnak işaretleri olmadan) yerine bu deponun GitHub sayfasından aldığınız linki koplayın. + +copy URL to clipboard + +Örneğin: +``` +git clone https://github.com/kullanıcı-adi/first-contributions.git +``` +`kullanıcı-adi` sizin GitHub kullanıcı adınız. Burada GitHub üzerinde bulunan first-contributions reposunun içeriğini bilgisayarınıza kopyalıyorsunuz. + +## Dal (Branch) oluşturma + +Eğer henüz klasör içinde değilseniz komut isteminde ana klasörünün konumuna gidin: + +``` +cd first-contributions +``` +`git checkout` komutunu kullanarak yeni bir dal(branch) oluşturun: +``` +git checkout -b +``` + +Örneğin: +``` +git checkout -b ekle-aydin-cagri-dumlu +``` +(Dal ismi içinde *ekle* kelimesinin geçme zorunluluğu yok, fakat bu dal isminizi katkı sunanlar listesine ekleme amacıyla oluşturulduğundan, ekle yazmak mantıklı olacaktır.) + +## Gerekli değişiklikleri yapıp bu değişiklikleri onaylama + +Şimdi, bir metin editöründe `Contributors.md` dosyasını açın. Hafif bir işaretleme dili olan Markdown'a alışkın olmanız gerekmektedir. Nasıl kullanacağınızı öğrenmek için bu [kopya kağıdına](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet) göz atabilirsiniz. + +`Contributors.md` dosyasının sonuna bu satırı ekleyin: + +``` +- [İsminiz](https://github.com/kullanici-adiniz) +``` + +Örneğin: + +``` +- [Ahmet Yılmaz](https://github.com/ahmet-yilmaz) +``` + +`](` arasında boşluk olmadığından emin olun. Dosyayı kaydedin ve kapatın. + +git status + +Komut istemi üzerinde proje klasörüne gidip `git status` komutunu yazdığınızda yaptığınız değişiklikleri göreceksiniz. + +`git add` komutu ile bu değişiklikleri oluşturduğunuz dal içine ekleyin. + +``` +git add Contributors.md +``` + +Şimdi `git commit` komutunu kullanarak değişikliklerinizi onaylayın (commit): +``` +git commit -m " katkıda bulunanlar listesine eklendi" +``` +`` yerine kendi isminizi yazın. + +(Ç.N: Açık kaynak dünyasında dünyanın farklı yerlerinden insanlarla birlikte çalışacağınız için onay mesajını İngilizce yazabilirsiniz.) + +## Değişiklikleri GitHub üzerine "itme" (Push) + +`git push` komutu ile değişikliklerinizi ittirin: +``` +git push origin +``` +`` yerine daha önce oluşturduğunuz dalın ismini girin. + +## Değişikliklerinizi inceleme için gönderin + +Oluşturduğunuz deponun Github sayfasında `Compare & pull request` butonunu göreceksiniz. Bu butona basın. + +create a pull request + +Şimdi çekme isteğini (pull request) gönderin. + +submit pull request + +Yaptığınız değişiklikleri en kısa zamanda projenin "master" dalı ile birleştireceğiz. Bu işlem tamamlandığı zaman bir bilgilendirme e-postası alacaksınız. + +## Bundan sonra ne yapabilirim? + +Tebrikler! Katkıda bulunan kişi olarak sıklıkla karşılaşacağınız standart _çatal -> klon -> düzenle -> çekme isteği_ iş akışını tamamladınız! + +Sunduğunuz katkının coşkusunu yaşamak ve bunu arkadaşlarınız ve takipçilerinizle paylaşmak için [bu bağlantıdaki](https://roshanjossey.github.io/first-contributions/#social-share) uygulamamızı kullanabilirsiniz. + +Bir sorunuz veya yardıma ihtiyacınız olursa Slack takımımıza katılabilirsiniz. [Slack takımına katıl](https://firstcontributions.herokuapp.com) + +Artık diğer projelere katkı sunmaya hazırsınız. Çözmeye başlayabileceğiniz giriş seviyesindeki konulara (issue) sahip projeleri [sizin için derledik](https://roshanjossey.github.io/first-contributions/#project-list). + +### [Ek bilgi](../additional-material/git_workflow_scenarios/additional-material.md) + +## Diğer araçlarla ilgili eğitimler + + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + diff --git a/translations/README.ua.md b/translations/README.ua.md new file mode 100644 index 00000000000..48f6aff1ae9 --- /dev/null +++ b/translations/README.ua.md @@ -0,0 +1,138 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +# Перший внесок + +Це важко. Це завжди важко - робити щось вперше. Проте якщо ви працюєте над проєктом з кимось, помилки будуть вдвічі неприємнішими. Але Open Source завжди пов’язаний з колективною роботою. Ми хочемо полегшити шлях для початківців, які бажають зробити свій перший внесок. + +Можна прочитати безліч інструкцій та переглянути сотні відео, але що може бути краще, ніж спробувати зробити внесок не боячись нічого зламати? Ціль цього проєкту - надати можливість новачкам зробити їх перший внесок. Запам’ятайте: чим більше ви розслаблені, тим краще ви вчитеся. Якщо ви хочете зробити свій перший внесок, просто виконуйте прості кроки нижче. Ми обіцяємо, що це буде весело! + +fork this repository + +Якщо ви ще не встановили GIT, тоді [ зробіть це негайно ]( https://help.github.com/articles/set-up-git/ ) :) + +## Відгалужте репозиторій + +Відгалужте свою власну копію цього репозиторію, натиснувши кнопку `fork` вгорі цієї сторінки. +Таким чином, ви створите копію цього репозиторію у вашому акаунті. + +## Клонуйте репозиторій + +clone this repository + +Тепер клонуйте цей репозиторій на ваш комп’ютер. Натисніть на кнопку `clone`, а потім - на іконку `copy to clipboard`. + +Відкрийте термінал і виконайте наступні команди: + +``` +git clone "посилання, яке ви щойно скопіювали" +``` +де `посилання, яке ви щойно скопіювали` (без лапок) - адреса цього репозиторію. Дивіться попередній крок для того, щоб отримати цю адресу. + +copy URL to clipboard + +Наприклад: +``` +git clone https://github.com/this-is-you/first-contributions.git +``` +де `this-is-you` - ваш GitHub нікнейм. Таким чином, ви копіюєте вміст репозиторію з GitHub, в який збираєтесь зробити внесок, на ваш комп’ютер. + +## Створюємо гілку + +Перейдіть в директорію з репозиторієм на вашому комп’ютері (якщо ви ще цього не зробили): + +``` +cd first-contributions +``` +Тепер створюємо гілку за допомогою команди `git checkout`: +``` +git checkout -b +``` + +Наприклад: +``` +git checkout -b add-petro-church +``` +(Назва гілки не повинна обов’язково містити слово *add*, але це має сенс, якщо майбутні зміни передбачають додавання чогось, наприклад, вашого імені у список контрибуторів.) + +## Робимо необхідні зміни та записуємо їх в репозиторій + +Тепер відкриваємо файл `Contributors.md` в текстовому редакторі та додаємо ваше ім’я, а потім зберігаємо файл. Якщо ви перейдете в директорію проєкту і виконаєте команду `git status`, ви побачите зміни. Додайте ці зміни до гілки, яку ви тільки що створили, за допомогою команди `git add`: +``` +git add Contributors.md +``` + +Тепер запишіть ці зміни за допомогою команди `git commit`: +``` +git commit -m "Add to Contributors list" +``` +замініть `` своїм іменем. + +## Відправляємо зміни в GitHub + +Відправте зміни на віддалений репозиторій в GitHub за допомогою команди `git push`: +``` +git push origin +``` +замініть `` назвою гілки, яку ви створили раніше. + +## Відправляємо зміни на перевірку + +Коли ви перейдете до свого репозиторію в GitHub, ви побачите кнопку `Compare & pull request`. Сміливо натисніть на неї. + +create a pull request + +Тепер зміни відправлені на перевірку і затвердження. + +submit pull request + +Згодом я об’єднаю ваші запропоновані зміни з основною гілкою цього репозиторію. Ви отримаєте листа, коли це буде зроблено. + +Основна гілка вашого репозиторію не буде змінена. Якщо ви хочете синхронізувати ваше відгалуження з моїм репозиторієм, дотримуйтесь цієї інструкції. + +## Тримаємо свій репозиторій синхронізованим + + Спочатку перейдіть на основну гілку. + ``` + git checkout master + ``` + + Потім додайте мій репозиторій як `upstream remote url`: +``` +git remote add upstream https://github.com/Roshanjossey/first-contributions +``` +Таким чином ми повідомляємо git про те, що інша версія цього проєкту існує за визначеною адресою і ми називаємо це `upstream`. Як тільки зміни будуть об’єднані, заберіть нову версію мого репозиторію: +``` +git fetch upstream +``` +Тобто ви забираєте всі зміни з мого репозиторію. Тепер ви повинні об’єднати зміни, які прийшли з мого репозиторію, у вашу основну гілку. +``` +git rebase upstream/master +``` +Цим ви приймаєте всі зміни до основної гілки. Якщо ви відправите зміни до GitHub, ваше відгалуження також буде містити ці зміни: +``` +git push origin master +``` +Зауважте, що ви відправляєте зміни до віддаленого репозиторію, який був названий `origin`. + +Тепер я об’єднав вашу гілку `` з моєю основною гілкою, а ви об’єднали мою основну гілку зі своєю основною гілкою. Гілка, яку ви створювали для внесення змін, більше не потрібна. Ви можете видалити її: +``` +git branch -d +``` +Крім цього, ви можете видалити і її віддалену версію: +``` +git push origin --delete +``` +Називати гілку в такий спосіб не обов’язково, однак це було зроблено з певною метою, аби показати призначення цієї гілки. Існування будь-якої гілки може бути коротким, адже врешті-решт, всі гілки об’єднуються з основною гілкою. + +## Інструкції для інших інструментів + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + +## Що далі? + +Ви можете приєднатися до нашої команди в Slack, якщо ви потребуєте будь-якої допомоги або маєте якісь запитання. [Приєднатися до команди в Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) diff --git a/translations/README.un-aln.md b/translations/README.un-aln.md new file mode 100644 index 00000000000..ab81e39a4fe --- /dev/null +++ b/translations/README.un-aln.md @@ -0,0 +1,129 @@ +[![Open Source Love](https://firstcontributions.github.io/open-source-badges/badges/open-source-v1/open-source.svg)](https://github.com/firstcontributions/open-source-badges) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# ⎎⟟⍀⌇⏁ ☊⍜⋏⏁⍀⟟⏚⎍⏁⟟⍜⋏⌇ + +⏁⊑⟟⌇ ⌿⍀⍜⟊⟒☊⏁ ⏃⟟⋔⌇ ⏁⍜ ⌇⟟⋔⌿⌰⟟⎎⊬ ⏃⋏⎅ ☌⎍⟟⎅⟒ ⏁⊑⟒ ⍙⏃⊬ ⏚⟒☌⟟⋏⋏⟒⍀⌇ ⋔⏃☍⟒ ⏁⊑⟒⟟⍀ ⎎⟟⍀⌇⏁ ☊⍜⋏⏁⍀⟟⏚⎍⏁⟟⍜⋏. ⟟⎎ ⊬⍜⎍ ⏃⍀⟒ ⌰⍜⍜☍⟟⋏☌ ⏁⍜ ⋔⏃☍⟒ ⊬⍜⎍⍀ ⎎⟟⍀⌇⏁ ☊⍜⋏⏁⍀⟟⏚⎍⏁⟟⍜⋏, ⎎⍜⌰⌰⍜⍙ ⏁⊑⟒ ⌇⏁⟒⌿⌇ ⏚⟒⌰⍜⍙. + +_⟟⎎ ⊬⍜⎍'⍀⟒ ⋏⍜⏁ ☊⍜⋔⎎⍜⍀⏁⏃⏚⌰⟒ ⍙⟟⏁⊑ ☊⍜⋔⋔⏃⋏⎅ ⌰⟟⋏⟒, [⊑⟒⍀⟒ ⏃⍀⟒ ⏁⎍⏁⍜⍀⟟⏃⌰⌇ ⎍⌇⟟⋏☌ ☌⎍⟟ ⏁⍜⍜⌰⌇.](#tutorials-using-other-tools)_ + +fork this repository + +#### ⟟⎎ ⊬⍜⎍ ⎅⍜⋏'⏁ ⊑⏃⎐⟒ ☌⟟⏁ ⍜⋏ ⊬⍜⎍⍀ ⋔⏃☊⊑⟟⋏⟒, [⟟⋏⌇⏁⏃⌰⌰ ⟟⏁](https://help.github.com/articles/set-up-git/). + +## ⎎⍜⍀☍ ⏁⊑⟟⌇ ⍀⟒⌿⍜⌇⟟⏁⍜⍀⊬ + +⎎⍜⍀☍ ⏁⊑⟟⌇ ⍀⟒⌿⍜⌇⟟⏁⍜⍀⊬ ⏚⊬ ☊⌰⟟☊☍⟟⋏☌ ⍜⋏ ⏁⊑⟒ `fork` ⏚⎍⏁⏁⍜⋏ ⍜⋏ ⏁⊑⟒ ⏁⍜⌿ ⍜⎎ ⏁⊑⟟⌇ ⌿⏃☌⟒. + ⏁⊑⟟⌇ ⍙⟟⌰⌰ ☊⍀⟒⏃⏁⟒ ⏃ ☊⍜⌿⊬ ⍜⎎ ⏁⊑⟟⌇ ⍀⟒⌿⍜⌇⟟⏁⍜⍀⊬ ⟟⋏ ⊬⍜⎍⍀ ⏃☊☊⍜⎍⋏⏁. + +## ☊⌰⍜⋏⟒ ⏁⊑⟒ ⍀⟒⌿⍜⌇⟟⏁⍜⍀⊬ + +clone this repository + +⋏⍜⍙ ☊⌰⍜⋏⟒ ⏁⊑⟒ ⎎⍜⍀☍⟒⎅ ⍀⟒⌿⍜⌇⟟⏁⍜⍀⊬ ⏁⍜ ⊬⍜⎍⍀ ⋔⏃☊⊑⟟⋏⟒. ☌⍜ ⏁⍜ ⊬⍜⎍⍀ ☌⟟⏁⊑⎍⏚ ⏃☊☊⍜⎍⋏⏁, ⍜⌿⟒⋏ ⏁⊑⟒ ⎎⍜⍀☍⟒⎅ ⍀⟒⌿⍜⌇⟟⏁⍜⍀⊬, ☊⌰⟟☊☍ ⍜⋏ ⏁⊑⟒ ☊⍜⎅⟒ ⏚⎍⏁⏁⍜⋏ ⏃⋏⎅ ⏁⊑⟒⋏ ☊⌰⟟☊☍ ⏁⊑⟒ _copy to clipboard_ ⟟☊⍜⋏. + +⍜⌿⟒⋏ ⏃ ⏁⟒⍀⋔⟟⋏⏃⌰ ⏃⋏⎅ ⍀⎍⋏ ⏁⊑⟒ ⎎⍜⌰⌰⍜⍙⟟⋏☌ `git` ☊⍜⋔⋔⏃⋏⎅: + +``` +git clone "url you just copied" +``` + +⍙⊑⟒⍀⟒ "url you just copied" (⍙⟟⏁⊑⍜⎍⏁ ⏁⊑⟒ ⍾⎍⍜⏁⏃⏁⟟⍜⋏ ⋔⏃⍀☍⌇) ⟟⌇ ⏁⊑⟒ ⎍⍀⌰ ⏁⍜ ⏁⊑⟟⌇ ⍀⟒⌿⍜⌇⟟⏁⍜⍀⊬ (⊬⍜⎍⍀ ⎎⍜⍀☍ ⍜⎎ ⏁⊑⟟⌇ ⌿⍀⍜⟊⟒☊⏁). ⌇⟒⟒ ⏁⊑⟒ ⌿⍀⟒⎐⟟⍜⎍⌇ ⌇⏁⟒⌿⌇ ⏁⍜ ⍜⏚⏁⏃⟟⋏ ⏁⊑⟒ ⎍⍀⌰. + +copy URL to clipboard + +⎎⍜⍀ ⟒⌖⏃⋔⌿⌰⟒: + +``` +git clone https://github.com/this-is-you/first-contributions.git +``` + +⍙⊑⟒⍀⟒ `this-is-you` ⟟⌇ ⊬⍜⎍⍀ GitHub ⎍⌇⟒⍀⋏⏃⋔⟒. ⊑⟒⍀⟒ ⊬⍜⎍'⍀⟒ ☊⍜⌿⊬⟟⋏☌ ⏁⊑⟒ ☊⍜⋏⏁⟒⋏⏁⌇ ⍜⎎ ⏁⊑⟒ ⎎⟟⍀⌇⏁-☊⍜⋏⏁⍀⟟⏚⎍⏁⟟⍜⋏⌇ ⍀⟒⌿⍜⌇⟟⏁⍜⍀⊬ ⍜⋏ GitHub ⏁⍜ ⊬⍜⎍⍀ ☊⍜⋔⌿⎍⏁⟒⍀. + +## ☊⍀⟒⏃⏁⟒ ⏃ ⏚⍀⏃⋏☊⊑ + +☊⊑⏃⋏☌⟒ ⏁⍜ ⏁⊑⟒ ⍀⟒⌿⍜⌇⟟⏁⍜⍀⊬ ⎅⟟⍀⟒☊⏁⍜⍀⊬ ⍜⋏ ⊬⍜⎍⍀ ☊⍜⋔⌿⎍⏁⟒⍀ (⟟⎎ ⊬⍜⎍ ⏃⍀⟒ ⋏⍜⏁ ⏃⌰⍀⟒⏃⎅⊬ ⏁⊑⟒⍀⟒): + +``` +cd first-contributions +``` + +⋏⍜⍙ ☊⍀⟒⏃⏁⟒ ⏃ ⏚⍀⏃⋏☊⊑ ⎍⌇⟟⋏☌ ⏁⊑⟒ `git checkout` ☊⍜⋔⋔⏃⋏⎅: + +``` +git checkout -b your-new-branch-name +``` + +⎎⍜⍀ ⟒⌖⏃⋔⌿⌰⟒: + +``` +git checkout -b add-alonzo-church +``` + +## ⋔⏃☍⟒ ⋏⟒☊⟒⌇⌇⏃⍀⊬ ☊⊑⏃⋏☌⟒⌇ ⏃⋏⎅ ☊⍜⋔⋔⟟⏁ ⏁⊑⍜⌇⟒ ☊⊑⏃⋏☌⟒⌇ + +⋏⍜⍙ ⍜⌿⟒⋏ `Contributors.md` ⎎⟟⌰⟒ ⟟⋏ ⏃ ⏁⟒⌖⏁ ⟒⎅⟟⏁⍜⍀, ⏃⎅⎅ ⊬⍜⎍⍀ ⋏⏃⋔⟒ ⏁⍜ ⟟⏁. ⎅⍜⋏'⏁ ⏃⎅⎅ ⟟⏁ ⏃⏁ ⏁⊑⟒ ⏚⟒☌⟟⋏⋏⟟⋏☌ ⍜⍀ ⟒⋏⎅ ⍜⎎ ⏁⊑⟒ ⎎⟟⌰⟒. ⌿⎍⏁ ⟟⏁ ⏃⋏⊬⍙⊑⟒⍀⟒ ⟟⋏ ⏚⟒⏁⍙⟒⟒⋏. ⋏⍜⍙, ⌇⏃⎐⟒ ⏁⊑⟒ ⎎⟟⌰⟒. + +git status + +⟟⎎ ⊬⍜⎍ ☌⍜ ⏁⍜ ⏁⊑⟒ ⌿⍀⍜⟊⟒☊⏁ ⎅⟟⍀⟒☊⏁⍜⍀⊬ ⏃⋏⎅ ⟒⌖⟒☊⎍⏁⟒ ⏁⊑⟒ ☊⍜⋔⋔⏃⋏⎅ `git status`, ⊬⍜⎍'⌰⌰ ⌇⟒⟒ ⏁⊑⟒⍀⟒ ⏃⍀⟒ ☊⊑⏃⋏☌⟒⌇. + +⏃⎅⎅ ⏁⊑⍜⌇⟒ ☊⊑⏃⋏☌⟒⌇ ⏁⍜ ⏁⊑⟒ ⏚⍀⏃⋏☊⊑ ⊬⍜⎍ ⟊⎍⌇⏁ ☊⍀⟒⏃⏁⟒⎅ ⎍⌇⟟⋏☌ ⏁⊑⟒ `git add` ☊⍜⋔⋔⏃⋏⎅: + +``` +git add Contributors.md +``` + +⋏⍜⍙ ☊⍜⋔⋔⟟⏁ ⏁⊑⍜⌇⟒ ☊⊑⏃⋏☌⟒⌇ ⎍⌇⟟⋏☌ ⏁⊑⟒ `git commit` ☊⍜⋔⋔⏃⋏⎅: + +``` +git commit -m "Add to Contributors list" +``` + +⍀⟒⌿⌰⏃☊⟟⋏☌ `` ⍙⟟⏁⊑ ⊬⍜⎍⍀ ⋏⏃⋔⟒. + +## ⌿⎍⌇⊑ ☊⊑⏃⋏☌⟒⌇ ⏁⍜ GitHub + +⌿⎍⌇⊑ ⊬⍜⎍⍀ ☊⊑⏃⋏☌⟒⌇ ⎍⌇⟟⋏☌ ⏁⊑⟒ ☊⍜⋔⋔⏃⋏⎅ `git push`: + +``` +git push origin -u +``` + +⍀⟒⌿⌰⏃☊⟟⋏☌ `` ⍙⟟⏁⊑ ⏁⊑⟒ ⋏⏃⋔⟒ ⍜⎎ ⏁⊑⟒ ⏚⍀⏃⋏☊⊑ ⊬⍜⎍ ☊⍀⟒⏃⏁⟒⎅ ⟒⏃⍀⌰⟟⟒⍀. + +
+ ⟟⎎ ⊬⍜⎍ ☌⟒⏁ ⏃⋏⊬ ⟒⍀⍀⍜⍀⌇ ⍙⊑⟟⌰⟒ ⌿⎍⌇⊑⟟⋏☌, ☊⌰⟟☊☍ ⊑⟒⍀⟒: + +- ### ⏃⎍⏁⊑⟒⋏⏁⟟☊⏃⏁⟟⍜⋏ ⟒⍀⍀⍜⍀ + 
remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead.
+  remote: Please see https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ for more information.
+  fatal: Authentication failed for 'https://github.com//first-contributions.git/'
+ ☌⍜ ⏁⍜ [GitHub's ⏁⎍⏁⍜⍀⟟⏃⌰](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account) ⍜⋏ ☌⟒⋏⟒⍀⏃⏁⟟⋏☌ ⏃⋏⎅ ☊⍜⋏⎎⟟☌⎍⍀⟟⋏☌ ⏃⋏ ⌇⌇⊑ ☍⟒⊬ ⏁⍜ ⊬⍜⎍⍀ ⏃☊☊⍜⎍⋏⏁. + +
+ +## ⌇⎍⏚⋔⟟⏁ ⊬⍜⎍⍀ ☊⊑⏃⋏☌⟒⌇ ⎎⍜⍀ ⍀⟒⎐⟟⟒⍙ + +⟟⎎ ⊬⍜⎍ ☌⍜ ⏁⍜ ⊬⍜⎍⍀ ⍀⟒⌿⍜⌇⟟⏁⍜⍀⊬ ⍜⋏ ☌⟟⏁⊑⎍⏚, ⊬⍜⎍'⌰⌰ ⌇⟒⟒ ⏃ `Compare & pull request` ⏚⎍⏁⏁⍜⋏. ☊⌰⟟☊☍ ⍜⋏ ⏁⊑⏃⏁ ⏚⎍⏁⏁⍜⋏. + +create a pull request + +⋏⍜⍙ ⌇⎍⏚⋔⟟⏁ ⏁⊑⟒ `pull request`. + +submit pull request + +⌇⍜⍜⋏ ⟟'⌰⌰ ⏚⟒ ⋔⟒⍀☌⟟⋏☌ ⏃⌰⌰ ⊬⍜⎍⍀ ☊⊑⏃⋏☌⟒⌇ ⟟⋏⏁⍜ ⏁⊑⟒ ⋔⏃⌇⏁⟒⍀ ⏚⍀⏃⋏☊⊑ ⍜⎎ ⏁⊑⟟⌇ ⌿⍀⍜⟊⟒☊⏁. ⊬⍜⎍ ⍙⟟⌰⌰ ☌⟒⏁ ⏃ ⋏⍜⏁⟟⎎⟟☊⏃⏁⟟⍜⋏ ⟒⋔⏃⟟⌰ ⍜⋏☊⟒ ⏁⊑⟒ ☊⊑⏃⋏☌⟒⌇ ⊑⏃⎐⟒ ⏚⟒⟒⋏ ⋔⟒⍀☌⟒⎅. + +## ⍙⊑⟒⍀⟒ ⏁⍜ ☌⍜ ⎎⍀⍜⋔ ⊑⟒⍀⟒? + +☊⍜⋏☌⍀⏃⏁⌇! ⊬⍜⎍ ⟊⎍⌇⏁ ☊⍜⋔⌿⌰⟒⏁⟒⎅ ⏁⊑⟒ ⌇⏁⏃⋏⎅⏃⍀⎅ _fork -> clone -> edit -> pull request_ ⍙⍜⍀☍⎎⌰⍜⍙ ⏁⊑⏃⏁ ⊬⍜⎍'⌰⌰ ⟒⋏☊⍜⎍⋏⏁⟒⍀ ⍜⎎⏁⟒⋏ ⏃⌇ ⏃ ☊⍜⋏⏁⍀⟟⏚⎍⏁⍜⍀! + +☊⟒⌰⟒⏚⍀⏃⏁⟒ ⊬⍜⎍⍀ ☊⍜⋏⏁⍀⟟⏚⎍⏁⟟⍜⋏ ⏃⋏⎅ ⌇⊑⏃⍀⟒ ⟟⏁ ⍙⟟⏁⊑ ⊬⍜⎍⍀ ⎎⍀⟟⟒⋏⎅⌇ ⏃⋏⎅ ⎎⍜⌰⌰⍜⍙⟒⍀⌇ ⏚⊬ ☌⍜⟟⋏☌ ⏁⍜ [⍙⟒⏚ ⏃⌿⌿](https://firstcontributions.github.io/#social-share). + +⊬⍜⎍ ☊⍜⎍⌰⎅ ⟊⍜⟟⋏ ⍜⎍⍀ slack ⏁⟒⏃⋔ ⟟⋏ ☊⏃⌇⟒ ⊬⍜⎍ ⋏⟒⟒⎅ ⏃⋏⊬ ⊑⟒⌰⌿ ⍜⍀ ⊑⏃⎐⟒ ⏃⋏⊬ ⍾⎍⟒⌇⏁⟟⍜⋏⌇. [⟊⍜⟟⋏ slack ⏁⟒⏃⋔](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +⋏⍜⍙ ⌰⟒⏁'⌇ ☌⟒⏁ ⊬⍜⎍ ⌇⏁⏃⍀⏁⟒⎅ ⍙⟟⏁⊑ ☊⍜⋏⏁⍀⟟⏚⎍⏁⟟⋏☌ ⏁⍜ ⍜⏁⊑⟒⍀ ⌿⍀⍜⟊⟒☊⏁⌇. ⍙⟒'⎐⟒ ☊⍜⋔⌿⟟⌰⟒⎅ ⏃ ⌰⟟⌇⏁ ⍜⎎ ⌿⍀⍜⟊⟒☊⏁⌇ ⍙⟟⏁⊑ ⟒⏃⌇⊬ ⟟⌇⌇⎍⟒⌇ ⊬⍜⎍ ☊⏃⋏ ☌⟒⏁ ⌇⏁⏃⍀⏁⟒⎅ ⍜⋏. ☊⊑⟒☊☍ ⍜⎍⏁ [⏁⊑⟒ ⌰⟟⌇⏁ ⍜⎎ ⌿⍀⍜⟊⟒☊⏁⌇ ⟟⋏ ⏁⊑⟒ ⍙⟒⏚ ⏃⌿⌿](https://firstcontributions.github.io/#project-list). diff --git a/translations/README.ur.md b/translations/README.ur.md new file mode 100644 index 00000000000..2651e66a619 --- /dev/null +++ b/translations/README.ur.md @@ -0,0 +1,151 @@ +
+Open Source LoveOpen Source Helpers +
+ +#
پہلی شراکت
+ +
+یہ مشکل ہے. پہلی بار جب آپ کچھ کرتے ہو تو وہ ہمیشہ مشکل لگتا ہے. خاص طور پر جب آپ تعاون کر رہے ہیں، غلطیاں کرنا کوئ پرسکون چیز نہیں ہے. لیکن اوپن سورس مکمل طورپر تعاون اور مل جل کر کام کرنے کا نام ہے. ہم چاہتے ہیں کہ نئے اوپن سورس کے معاونین اسےآسانی سے سیکھیں اور پہلی بار اس میں شرکت کریں. +
+
+
+مضامین پڑھنے اور سبق دیکھنے سے مدد مل سکتی ہے، لیکن چیزوں میں الجھے بغیر کسی کام کو اصل میں کرنا کتنا بہتر ہے؟ اس پروجیکٹ کا مقصد رہنمائی فراہم کرنا اور نئے شرکت کرنے والے لوگوں کے راستے کو آسان بنانا ہے. یاد رکھیں: آپ جتنا پرسکوں ہوں گے، آپ اتنا بہتر سیکھیں گے. اگر آپ اپنا پہلا اشتراک کرنا چاہتے ہیں، تو ذیل میں دیے گئے سادہ مراحل پر عمل کریں. ہم آپ سے وعدہ کرتے ہیں، یہ قابل لطف ہوں گے. +
+ + + +
+اگر آپ کی مشین پر گٹ نہیں ہے تو، +انسٹال کریں +
+ +##
اس ریپوزٹری کوفورک کریں
+
+اس صفحے کے سب سے اوپر فورک بٹن دبا کر اس ریپوزٹری کا استعمال کریں. +اس ریپوزٹری کوفورک کریں +
+یہ آپ کے کھاتے میں اس کی ایک نقل ذخیرہ کرے گا۔. +
+ +##
ریپوزٹری کا کلون کیجیے
+ +
+اب آپ اپنے کمپیوٹر مشین پر یہ ریپوزٹری کلون کریں. +
+ریپوزٹری کا کلون کیجیئے +
+ کلون بٹن کو دبائیں اور پھر "copy to clipboard" آئیکن کو دبائیں۔ +
+یوآرایل کلپ بورڈ پر کاپی کریں +
+ایک ٹرمینل کھولیں اور مندرجہ ذیل گٹ کمانڈ چلائیں: +
+ +``` +git clone "یو آر ایل جو آپ نے ابھی کاپی کیا" +``` + +
+جہاں "یو آر ایل جو آپ نے ابھی کاپی کیا" (اقتباس کے نشانات " " کے بغیر) اس ریپوزٹری کو کلون کرنے کا یو آر ایل کا اندراج مراد ہے. یو آر ایل حاصل کرنے کیلئے پچھلے مرحلے کو دیکھیں. +
+ +
مثال کے طور پر:
+ +``` +git clone https://github.com/this-is-you/first-contributions.git +``` + +
اس میں 'this-is-you' آپکا GitHub یوزرنیم ہے۔ یہاں آپ first-contributions GitHub ریپوزٹری کے مندرجات کمپیوٹر پر نقل کر رہے ہیں.
+ +##
ایک شاخ بنائیں
+ +
اپنے کمپیوٹر پر ریپوزٹری کی ڈائرکٹری تبدیل کریں (اگرآپ پہلے سے وہاں نہیں ہیں):
+ +``` +cd first-contributions +``` + +
اب git checkout کمانڈاستعمال کرتے ہوئے ایک شاخ تشکیل دیں :
+ +``` +git checkout -b +``` + +
مثال کے طور پر:
+ +``` +git checkout -b add-alonzo-church +``` + +
(شاخ کا نام میں ضروری نہیں add شامل کریں، لیکن یہ مناسب ہے کہ اس میں یہ شامل ہو، کیونکہ اس شاخ کا مقصد آپ کے نام کو فہرست میں شامل کرنا ہے.)
+ +##
ضروری تبد یلیاں کریں اور ان تبد یلیوں کو انجام دیں۔
+ +
+اب Contributors.md فائل کو ٹیکسٹ ایڈیٹر پر کھولیں، اپنا نام اس میں شامل کریں، اور پھر فائل کو محفوظ کریں. اگر آپ پراجیکٹ ڈائرکٹری میں جاتے ہیں اور کمانڈ git status کو چلاتے ہیں، تو آپ دیکھیں گے کہ تبدیلیاں موجود ہیں. ان تبدیلیوں کو اس شاخ میں git add کمانڈ استعمال کرتے ہوئے شامل کریں، جسے ابھی آپ نے بنایا تھا۔ : +
+ +``` +git add Contributors.md +``` + +
اب git commit کمانڈ کا استعمال کرتے ہوئے ان تبدیلیوں کو سونپ دیں:
+ +``` +git commit -m "Add to Contributors list" +``` + +
<your-name> کو اپنے نام کے ساتھ تبدیل کردیں.
+ +##
ان تبدیلیوں کو GitHub پردهکیل دیں۔
+ +
git push کمانڈ کے ذریعے اپنی تبدیلیوں کو پش کریں:
+ +``` +git push origin +``` + +
<add-your-name> کو شاخ کے نام کے ساتھ بدل دیں، جسے آپ نے پہلے بنایا تھا.
+ +##
اپنی تبدیلیوں کوجائزے کیلئے جمع کروائیں۔
+ +
اگر آپ GitHub پر اپنی ریپوزٹری پر جاتے ہیں تو، آپ کو Compare & pull request دکھائی دے گا. اس بٹن کو دبائیں.
+ +ایک پل درخواست کریں + +
اب پل درخواست جمع کروائیں.
+ +پل درخواست جمع کروائیں + +
جلد ہی میں آپ کی تمام تبدیلیوں کو اس پروجیکٹ کی ماسٹر شاخ میں ضم کر دونگا. تبدیلیوں کو ضم کرنے کے بعد آپ کو نوٹیفکیشن ای میل مل جائے گی
+ +###
[ اضافی مواد ](../additional-material/git_workflow_scenarios/additional-material.md)
+ +##
دوسرے ٹولز کو استعمال کرتے ہوئے سبق۔
+ + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + +##
یہاں سے کہاں جایا جائے؟
+ +
+ آپ کو مدد کی ضرورت ہے یا کوئی سوال ہو تو آپ ہماری سلیک ٹیم میں بھی شامل ہوسکتے ہیں. +سلیک ٹیم میں شمولیت اختیار کریں۔ +
+
+
+ادھر آپ چند مقبول ذخیروں میں کچھ ابتدائی سطح کے مسائل حل کر سکتے ہیں. آگے بڑھیے اور مزید جاننے کے لئے ان ذخیروں پر جائیے۔ +
+
+ +|[![exercism](https://avatars2.githubusercontent.com/u/5624255?v=3&s=100)](https://github.com/exercism/exercism.io/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+patch%22)|[![fun-retro](https://avatars3.githubusercontent.com/u/15913975?v=3&s=100)](https://github.com/funretro/distributed/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly)|[](https://github.com/facebook/react/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+bug%22)|[![habitat](https://avatars1.githubusercontent.com/u/18171698?v=3&s=100)](https://github.com/habitat-sh/habitat/issues?q=is%3Aopen+is%3Aissue+label%3AEasy)|[![scikit-learn](https://avatars0.githubusercontent.com/u/365630?v=3&s=100)](https://github.com/scikit-learn/scikit-learn/issues?q=is%3Aopen+is%3Aissue+label%3AEasy)|[](https://github.com/technomancy/leiningen/issues?q=is%3Aopen+is%3Aissue+label%3ANewbie)|[](https://github.com/numpy/numpy/issues?q=is%3Aopen+is%3Aissue+label%3A%22Easy+Fix%22)|[![elasticsearch](https://avatars2.githubusercontent.com/u/6764390?v=3&s=100)](https://github.com/elastic/elasticsearch/issues?q=is%3Aopen+is%3Aissue+label%3A%22low+hanging+fruit%22)| +|---|---|---|---|---|---|---|---| +|[exercism](https://github.com/exercism/exercism.io/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+patch%22)|[Fun Retros](https://github.com/funretro/distributed/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly)|[react](https://github.com/facebook/react/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+bug%22)|[habitat](https://github.com/habitat-sh/habitat/issues?q=is%3Aopen+is%3Aissue+label%3AEasy)|[scikit-learn](https://github.com/scikit-learn/scikit-learn/issues?q=is%3Aopen+is%3Aissue+label%3AEasy)|[Leiningen](https://github.com/technomancy/leiningen/issues?q=is%3Aopen+is%3Aissue+label%3ANewbie)|[numpy](https://github.com/numpy/numpy/issues?q=is%3Aopen+is%3Aissue+label%3A%22Easy+Fix%22)|[elasticsearch](https://github.com/elastic/elasticsearch/issues?q=is%3Aopen+is%3Aissue+label%3A%22low+hanging+fruit%22)| +|[![homebrew](https://avatars2.githubusercontent.com/u/1503512?v=3&s=100)](https://github.com/Homebrew/brew/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22)|[![rust](https://avatars1.githubusercontent.com/u/5430905?v=3&s=100)](https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Aissue+label%3AE-easy)|[![vuejs](https://avatars1.githubusercontent.com/u/6128107?v=3&s=100)](https://github.com/vuejs/vue/issues?q=is%3Aopen+is%3Aissue+label%3A%22contribution+welcome%22)|[![Suave](https://avatars2.githubusercontent.com/u/5822862?v=3&s=100)](https://github.com/SuaveIO/suave/issues?q=is%3Aopen+is%3Aissue+label%3Ahardness-easy)|[![OpenRA](https://avatars3.githubusercontent.com/u/409046?v=3&s=100)](https://github.com/OpenRA/OpenRA/issues?q=is%3Aopen+is%3Aissue+label%3AEasy)|[![PowerShell](https://avatars0.githubusercontent.com/u/11524380?v=3&s=100)](https://github.com/powershell/powershell/issues?q=is%3Aopen+is%3Aissue+label%3AUp-for-Grabs)|[![coala](https://avatars2.githubusercontent.com/u/10620750?v=3&s=100)](https://github.com/coala/coala/issues?q=is%3Aopen+is%3Aissue+label%3Adifficulty%2Flow+label%3Adifficulty%2Fnewcomer)|[![moment](https://avatars2.githubusercontent.com/u/4129662?v=3&s=100)](https://github.com/moment/moment/issues?q=is%3Aopen+is%3Aissue+label%3AUp-For-Grabs)| +|[homebrew](https://github.com/Homebrew/brew/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22)|[Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Aissue+label%3AE-easy)|[vuejs](https://github.com/vuejs/vue/issues?q=is%3Aopen+is%3Aissue+label%3A%22contribution+welcome%22)|[Suave](https://github.com/SuaveIO/suave/issues?q=is%3Aopen+is%3Aissue+label%3Ahardness-easy)|[OpenRA](https://github.com/OpenRA/OpenRA/issues?q=is%3Aopen+is%3Aissue+label%3AEasy)|[PowerShell](https://github.com/powershell/powershell/issues?q=is%3Aopen+is%3Aissue+label%3AUp-for-Grabs)|[coala](https://github.com/coala/coala/issues?q=is%3Aopen+is%3Aissue+label%3Adifficulty%2Flow+label%3Adifficulty%2Fnewcomer)|[moment](https://github.com/moment/moment/issues?q=is%3Aopen+is%3Aissue+label%3AUp-For-Grabs)| +|[![ava](https://avatars0.githubusercontent.com/u/8527916?v=3&s=100)](https://github.com/avajs/ava/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+for+beginner%22)|[![freeCodeCamp](https://avatars0.githubusercontent.com/u/9892522?v=3&s=100)](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only)|[![webpack](https://avatars3.githubusercontent.com/u/2105791?v=3&s=100)](https://github.com/webpack/webpack/issues?q=is%3Aopen+is%3Aissue+label%3A%22D1%3A+Easy+%28Contrib.+Difficulty%29%22)|[![hoodie](https://avatars1.githubusercontent.com/u/1888826?v=3&s=100)](https://github.com/hoodiehq/hoodie/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only)|[![pouchdb](https://avatars3.githubusercontent.com/u/3406112?v=3&s=100)](https://github.com/pouchdb/pouchdb/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22)|[![neovim](https://avatars0.githubusercontent.com/u/6471485?v=3&s=100)](https://github.com/neovim/neovim/issues?q=is%3Aopen+is%3Aissue+label%3Aentry-level)|[![babel](https://avatars2.githubusercontent.com/u/9637642?v=3&s=100)](https://github.com/babel/babel/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly) |[](https://github.com/adobe/brackets/labels/Starter%20bug)| +|[ava](https://github.com/avajs/ava/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+for+beginner%22)|[freeCodeCamp](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only)|[webpack](https://github.com/webpack/webpack/issues?q=is%3Aopen+is%3Aissue+label%3A%22D1%3A+Easy+%28Contrib.+Difficulty%29%22)|[hoodie](https://github.com/hoodiehq/hoodie/issues?q=is%3Aopen+is%3Aissue+label%3Afirst-timers-only)|[pouchdb](https://github.com/pouchdb/pouchdb/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22)|[neovim](https://github.com/neovim/neovim/issues?q=is%3Aopen+is%3Aissue+label%3Aentry-level)|[babel](https://github.com/babel/babel/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner-friendly) |[brackets](https://github.com/adobe/brackets/labels/Starter%20bug)| +| [![Node.js](https://avatars1.githubusercontent.com/u/9950313?v=3&s=100)](https://github.com/nodejs/node/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22)|[](https://github.com/Semantic-Org/Semantic-UI-React/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22)| +| [Node.js](https://github.com/nodejs/node/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22) |[Semantic-UI-React](https://github.com/Semantic-Org/Semantic-UI-React/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+contribution%22) | diff --git a/translations/README.uz.md b/translations/README.uz.md new file mode 100644 index 00000000000..03f21b229df --- /dev/null +++ b/translations/README.uz.md @@ -0,0 +1,139 @@ +[![Open Source Love](https://firstcontributions.github.io/open-source-badges/badges/open-source-v1/open-source.svg)](https://github.com/firstcontributions/open-source-badges) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Birinchi hissalar + +Ushbu loyiha yangi boshlanuvchilarning birinchi hissasini qo'shish usullarini soddalashtirish va yo'naltirishga qaratilgan. Agar siz birinchi hissangizni qo'shmoqchi bo'lsangiz, quyidagi amallarni bajaring. + +_Agar buyruq satri sizga mos bo'lmasa, [Bu erda GUI vositalaridan foydalanib amalga oshirishga oid darsliklari mavjud](#boshqa-vositalardan-foydalangan-darsliklar)_ + + +repositoryni fork qiling + +#### Agar kompyuteringizda git mavjud bo'lmasa, [buni o'rnating](https://help.github.com/articles/set-up-git/). + +## Bu repositoryni fork qilib oling + +Bu repositoryni ushbu sahifaning yuqorisidagi fork tugmasini bosish orqali fork qilib oling +Bu akkountingizda ushbu repositoryning nusxasini yaratadi. + +## Bu repositoryni klon qilib oling + +bu repositoryni klon qilib oling + +Endi fork qilingan repositoryni kompyuteringizga klon qiling. Github akkountingizga kirib, fork qilingan repositoryni oching, code tugmasi ustiga bosing va keyin _copy to clipboard_ belgisi (icon) ustiga bosing. + +Terminalni oching va quyidagi git buyruqlarini yurg'izing: + +``` +git clone "siz horizgina ko'chirib olgan url" +``` + +bu yerda "siz horizgina ko'chirib olgan url" (qo'shtirnoqlarsiz) ushbu repositoryning (siz fork qilingan proyekt) urlidir. URLni olish uchun oldingi bosqichlarni ko'ring. + +urlni klipboardga ko'chiring + +Misol uchun: + +``` +git clone https://github.com/bu-siz/first-contributions.git +``` + +bu yerdagi `bu-siz` sizning Github akkount nomingiz (username). Bu yerda Githubdagi first-contributions repositorysining kontentlarini kompyuteringizga +ko'chiryapsiz. + +## Branch yaratish + +Kompyuteringizda repository katalogiga kiring (agar u yerda bo'lmasangiz) + +``` +cd first-contributions +``` + +Endi `git switch` buyrug'i orqali branch yarating: + +``` +git switch -c yangi-branch-nomingiz +``` + +Misol uchun: + +``` +git switch -c add-aliml92 +``` + +## Kerakli o'zgarishlarni qiling va bu o'zgarishlarni commit qiling + +Endi matn muharririda `Contributors.md` faylini oching, unga ismingizni qo'shing. Uni faylning boshiga yoki oxiriga qo'shmang. Uni istalgan o'rta qismga qo'shing. Endi faylni saqlang. + +git status + +Agar proyekt katalogiga o'tsangiz va `git status` buyrug'ini yurg'izsangiz, o'zgarishlar borligini ko'rasiz. + +`git add` buyrug'i yordamida hosil qilgan branchingizga o'zgarishlarni qo'shing: + +``` +git add Contributors.md +``` + +Endi `git commit` buyrug'i yordamida bu o'zgarishlarni commit qiling: + +``` +git commit -m "Contributors royxatiga ismingiz-ni kiritish" +``` +`ismingiz-` ni o'rniga o'zingizni ismingizni yozing. + +## O'zgarishlarni Githubga push qilish + +`git push` buyrug'i bilan o'zgartishlaringizni push qiling: + +``` +git push origin -u yangi-branch-nomingiz +``` + +albatta, `yangi-branch-nomingiz` ni biroz oldin yaratgan branch nomiga almashtirgan holda. + +
+ Push qilish vaqtida biror xatolarni ko'rsangiz, bu yerni bosing + +- ### Autentifikatsiya Xatoligi + 
remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead.
+  remote: Please see https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ for more information.
+  fatal: Authentication failed for 'https://github.com//first-contributions.git/'
+ Akkountingizga SSH kalit yaratish va konfiguratsiya qilish uchun [GitHub qo'llanma](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account) ga o'ting. + +
+ +## O'zgartirishlaringizni ko'rib chiqilishi uchun topshirish + +Agar Githubdagi repositoryingizga o'tsangiz, `Compare & pull request` tugmasini ko'rasiz. O'sha tugmani bosing. + +pull request hosil qilish + +Endi pull requestni submit qiling. + +pull request submit qilish + +Tez orada men sizning barcha o'zgarishlaringizni ushbu proyektning main branchiga birlashtiraman. O'zgarishlar birlashtirilgandan so'ng sizga elektron pochta xabarnomasi keladi. + +## bu yerdan qayerga borish? + +Tabriklayman! Siz horizgina contributor sifatida tez-tez uchraydigan standard ish ketma-ketligi ya'ni _fork -> clone -> edit -> pull request_ ni tamonladingiz. + +Hissangizni nishonlang va [web app](https://firstcontributions.github.io/#social-share)ga o'tish orqali hamtovoqlaringiz va ergashuvshilaringizga ulashing. + + +Agar sizga yordam kerak bo'lsa yoki savollaringiz bo'lsa, bizning slack jamoamizga qo'shilishingiz mumkin.[Slack jamoasiga qo'shiling](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Endi boshqa proyektlarga hissa qo‘shishni boshlaylik. Siz boshlashingiz mumkin bo'lgan oson masalalar bilan proyektlar ro'yxatini tuzdik. Ko'zdan kechiring [web appdagi proyektlar ro'yxati](https://firstcontributions.github.io/#project-list). + +### [Qo'shimcha materiallar](additional-material/git_workflow_scenarios/additional-material.md) + +## Boshqa Vositalardan Foydalangan Darsliklar + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [GitHub Desktop](gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.vn.md b/translations/README.vn.md new file mode 100644 index 00000000000..97abae83fe4 --- /dev/null +++ b/translations/README.vn.md @@ -0,0 +1,123 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + +*Người dịch: [Tran Ly Vu](https://github.com/tranlyvu)* +*Người chỉnh sửa: [Phuc Cai](https://github.com/hoangphuc05)* + +# Đóng góp đầu tiên + +Lần đầu tiên bạn làm điều gì đó thật khó khăn. Đặc biệt khi bạn đang cộng tác, sai lầm là điều rất khó chịu. Chúng tôi muốn đơn giản hóa quy trình học và đóng góp vào những dự án (project) mã nguồn mở. + +Việc đọc hướng dẫn có tác dụng, nhưng có gì tốt hơn là thực sự đóng góp trong môi trường thực tiễn? project này nhằm mục đích cung cấp hướng dẫn và đơn giản hóa cách thức những người mới tham gia đóng góp. Nếu bạn mong muốn thực hiện việc đóng góp đầu tiên của mình, chỉ cần làm theo các bước đơn giản bên dưới. + +#### *Nếu bạn không thích làm việc với dòng lệnh, [đây là hướng dẫn sử dụng GUI.]( #Hướng-dẫn-sử-dụng-các-công-cụ-khác )* + +fork this repository + +Nếu bạn không có git trên máy tính của bạn, [cài đặt](https://help.github.com/articles/set-up-git/) + +## Copy kho mã nguồn (Fork) + +Copy kho mã nguồn này bằng cách nhấn vào nút `Fork` đầu trang này. Bản sao kho mã nguồn mày sẽ được tạo ra trong tài khoản của bạn. + +## Sao chép kho mã nguồn (clone) + +clone this repository + +Bây giờ sao chép kho mã nguồn này vào máy của bạn. Nhấn vào nút `clone` và sau đó nhấn vào biểu tượng *copy to clipboard* + +Mở một bộ xử lý terminal và chạy lệnh git sau đây: + +``` +git clone "url bạn vừa sao chép" +``` +Trong đó "url bạn vừa sao chép" (không có dấu ngoặc kép) là url dẫn vào kho mã nguồn này. Xem các bước trước đó để có được url. + +copy URL to clipboard + +Ví dụ: +``` +git clone https://github.com/tên-bạn/first-contributions.git +``` +Trong đó `tên-bạn` là tên người dùng github của bạn. Ở đây bạn đang sao chép nội dung của kho mã nguồn "first-contributions" trong github vào máy tính của bạn + +## Tạo chi nhánh (branch) + +Thay đổi môi trường làm việc bằng thư mục của kho mã nguồn trên máy tính của bạn. + +``` +cd first-contributions +``` +Bây giờ tạo ra một chi nhánh sử dụng lệnh `git checkout` +``` +git checkout -b +``` + +Ví dụ: +``` +git checkout -b thêm-Tran-Ly-Vu +``` +(Tên của chi nhánh không cần phải có từ *thêm* trong đó, nhưng nó được dùng vì mục đích của chi nhánh này là thêm tên của bạn vào danh sách.) + +## Thực hiện những thay đổi cần thiết và chấp nhận những thay đổi này + +Bây giờ mở tập tin `Contributors.md` trong một trình soạn thảo văn bản và thêm tên của mình vào nó. +Đừng thêm vào đầu hoặc cuối tập tin. Thêm vào bất cứ nơi nào ở giữa. Bây giờ, lưu tập tin. + +git status + +Nếu bạn vào thư mục hiện tại của project và thực hiện lệnh `git status`, bạn sẽ thấy những thay đổi. + +Thêm những thay đổi vào chi nhánh bạn vừa tạo bằng lệnh `git add`: + +``` +git add Contributors.md +``` + +Bây giờ chấp nhận những thay đổi bằng cách sử dụng dòng lệnh `git commit` dưới đây. +``` +git commit -m "Them vào danh sách Cộng tác viên" +``` + +Thay thế `` với tên của bạn + +## Đẩy thay đổi lên github + +Đẩy những thay đổi của bạn sử dụng `git push` +``` +git push origin +``` +Thay thế `` với tên của chi nhánh bạn tạo ra trước đó + +## Gửi những thay đổi của bạn để xem xét + +Nếu bạn mở kho mã nguồn của bạn trên github, bạn sẽ thấy nút `Compare & pull request`. Nhấp vào nút đó. + +create a pull request + +Bây giờ gửi yêu cầu kéo. + +submit pull request + +Tôi sẽ sớm hợp nhất tất cả các thay đổi của bạn vào nhánh chủ (master branch) của project này. Bạn sẽ nhận được email thông báo sau khi các thay đổi đã được hợp nhất. + +## Tiếp theo + +Chúc mừng! Bạn vừa hoàn thành quy trình tiêu chuẩn copy (fork) -> Sao chép (clone) -> chỉnh sửa (edit) -> yêu cầu kéo (pull request) mà bạn sẽ gặp thường xuyên khi đóng góp! + +Hãy ăn mừng đóng góp của bạn và chia sẻ nó với bạn bè và những người theo dõi của bạn bằng cách truy cập [ứng dụng web](https://roshanjossey.github.io/first-contribution/#social-share). + +Bạn có thể tham gia slack của chúng tôi trong trường hợp bạn cần trợ giúp hoặc có câu hỏi nào. [Tham gia slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Để hỗ trợ bạn với việc đóng góp cho các project khác. Chúng tôi đã chuẩn bị danh sách các project đơn giản mà bạn có thể bắt đầu. Hãy kiểm tra [danh sách các project](https://roshanjossey.github.io/first-contributions/#project-list). + +### [Tài liệu bổ sung](../additional-material/git_workflow_scenarios/additional-material.md) + +## Hướng dẫn sử dụng các công cụ khác + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + diff --git a/translations/README.yor.md b/translations/README.yor.md new file mode 100644 index 00000000000..27ef9838310 --- /dev/null +++ b/translations/README.yor.md @@ -0,0 +1,129 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Akọkọ ilowosi + +Lati dasi nko lakoko n'le, pataki ti a ba ronu nipa asise ti a le bapade, a fe ko rorun fun awon ilowosi akoko lati le dasi +ise agbese lakoko, ise agbese yi a ko yin be ese le se, e tele ilana ni isalẹ + + +#### *to ba le lo pipaṣẹ, [awon ona mi re.](#Tutorials-Usin'-Other-Tools)* + +fork this repository + +e fi git sori ẹrọ [install it](https://help.github.com/articles/set-up-git/). + +## orita ibi ipamọ yii +orita ibi ipamọ yii, e te ' fork bọtini' ni oke oju iwe yi, e leyi a fun yin ni daako ni accounti yin + +## Dide ibi ipamọ + +clone this repository + +oya e de ibi ipamọ yi si account yin, e lo si githubu accounti yin, e te 'clone botini, ke wa te 'copy to clipboard' +. + +e sii ebute in ero ise yin, e te pipaṣẹ to be a labe oro yi si: + +``` +git clone "ọna asopọ ' te daakọ" +``` + +ibi, "ọna asopọ ' te daakọ" (lai awọn ' quote iṣmiṣ) lo je ono asopo ti e dide ibi ipamo (e dide ibi ipamo ise igbesi). e wo awon atono ti tele to n be loke + +copy URL to clipboard + +oye ko ri bi: + +``` +git clone https://github.com/oruko yin/first-contributions.git +``` + +ibi `oruko yin` ni oruko githubu accounti yin. ni bi yi en didako awon akoonu ' first-contributions repository in GitHubu' si ero ise yin. + +## ṣẹda ẹka + +seda eka si ero, amo ko to sebe te pipaṣẹ yi si ibe + +``` +cd first-contributions +``` + +oya seda eka si pelu ' `git checkout` pipase: + +``` +git checkout -b +``` + +fun apere: + +``` +git checkout -b add-luke-oliff +``` + +(kon se dadun ki e lo "add", amo o daa fun irun nnkan bayii) + +## Ṣe awọn ayipada to ṣe pataki 'n ṣe awọn ayipada yẹn + +oya shi faili `Contributors.md` ninu olootu ọrọ, fi oruko re mo awon oruko to 'n wan be, ma fe se akoko tabi igbeyn, fi si arin. + +git status + +to ba te pipase `git status` si ebute re, wa re awon ayipada ti ose + +fi won mo eka ti ode pelu pipase yii `git add`: + +``` +git add Contributors.md +``` + +oya dawon papop pelu pipase yi `git commit`: + +``` +git commit -m "Add to Contributors list" +``` + +yi `` pada si oruko re. + +## Titari awọn ayipada si GitHub + +te pipase yi `git push`: + +``` +git push origin +``` + +yi `` pada si orku e da ti ese ni ibere + +## Fi yer ayipada fer awotẹlẹ + +Ti o ba lọ t' yer ibi ipamọ lori GitHub, iwọ yoo ri a `Compare & pull request` botini. te botini yen. + +create a pull request + +oya fi silẹ. + +submit pull request + +To ba ya a ma so gbogo yipada ti e se papo, e o gba iwifunni lori imeeli yin + +## Nibo ni lati lọ? + +Ku ise oti pari boṣewa bisesenlo _fork -> clone -> edit -> PR_ bisesenlo ti o ma bapade ni ise asowopo + +Ṣe ayẹyẹ ilowosi yer 'ki o pin pẹlu' awọn ọkan ati awọn ọmọlẹyin nipasẹ lilọ’ si [web app](https://roshanjossey.github.io/first-contributions/#social-share). + +Ẹ lè darapọ̀ mọ́ àwọn òṣìṣẹ́ òṣìṣẹ́ wa tí kò já fáfá tí ẹ bá nílò ìrànlọ́wọ́ èyíkéyìí tàbí kí ẹ lè gba àlọ́ kankan. [Darapo](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Bayi jẹ ki a bẹrẹ pẹlu' idasi' t' awọn iṣẹ akanṣe miiran. A ti ṣe akojọpọ awọn iṣẹ akanṣe pẹlu awọn ọran irọrun ti o le bẹrẹ. Ṣayẹwo [awon re](https://roshanjossey.github.io/first-contributions/#project-list). + +### [Ptu le ka](../additional-material/git_workflow_scenarios/additional-material.md) + +## Tutorial lilo 'miiran Irinṣẹ + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.zh-cn.md b/translations/README.zh-cn.md new file mode 100644 index 00000000000..a6852344238 --- /dev/null +++ b/translations/README.zh-cn.md @@ -0,0 +1,113 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) + +# 第一次参与开源项目 + +万事开头难。尤其是和其他人合作时，犯错总是格外令人不舒服。不过，开源的本质就是和其他人合作。这个项目就是希望为初学者带来一个简单的方法去学习及参与开源项目。 + +你可以选择阅读文章和观看教程来得到帮助，但实际动手才是最好的学习方式。本项目旨在简化并指导初学者参与他们的第一次开源。记住：过程越轻松，学习效益越高。如果你想要做出第一次贡献，只需按照以下简单步骤操作即可。这将很好玩 :) + +fork this repository + +如果你的电脑上尚未安装 git, 请按照 [这个](https://help.github.com/articles/set-up-git/) 进行安装。 + +## Fork（复制）本代码仓库 + +点击图示中的按钮去 Fork 这个代码仓库。 +这个操作会将代码仓库复制到你的账户名下。 + +## Clone（克隆）代码仓库 + +clone this repository + +接下来将复制后的代码仓库克隆到你的电脑上。点击图示中的绿色按钮，接着点击复制到剪切板按钮（将代码仓库地址复制下来） + +随后打开命令行窗口，敲入如下 git 命令： + +``` +git clone "刚才复制的 url 链接" +``` +"刚才复制的 url 链接"（去掉双引号）就是复制到你账户名下的代码仓库地址。获取这链接地址的方法请见上一步。 + +copy URL to clipboard + +譬如： +``` +git clone https://github.com/你的Github用户名/first-contributions.git +``` + +'你的 Github 用户名' 指的就是你的 Github 用户名。这一步，你将复制到你账户名下的 first-contributions 这个代码仓库克隆到本地电脑上。 + +## 新建一个代码分支 + +下面的命令能在命令行窗口中，把目录切换到 first-contributions + +``` +cd first-contributions +``` +接下来使用 `git checkout` 命令新建一个代码分支 +``` +git checkout -b <新分支的名称> +``` + +譬如： +``` +git checkout -b add-myname +``` + +(新分支的名称不一定需要有 *add*。然而，在新分支的名称加入 *add* 是一件合理的事情，因为这个分支的目的是将你的名字添加到列表中。) + +## 对代码进行修改，而后 Commit (提交) 修改 + +打开 `Contributors.md` 这个文件，更新文件内容，将你的名字加上去，保存修改。`git status` 这命令会列出被改动的文件。接着 `git add` 这命令则可以添加你的改动，就像如下这条命令。 + +git status + +``` +git add Contributors.md +``` + +现在就可以使用 `git commit` 命令 commit 你的修改了。 +``` +git commit -m "Add <你的名字> to Contributors list" +``` +将 `<你的名字>` 替换成你的名字 + +## 将改动 Push（发布）到 GitHub + +使用 `git push` 命令发布代码 +``` +git push origin <分支的名称> +``` +将 `<分支的名称>` 替换为之前新建的分支名称。 + +## 提出 Pull Request 将你的修改供他人审阅 + +前往 Github 你的代码仓库，你会看到一个 `Compare & pull request` 的按钮。点击该按钮。 + +create a pull request + +接着再点击 `Create pull request` 按钮，正式提交 pull request。 + +submit pull request + +不久之后，我便会把你所有的变化合并到这个项目的主分支。更改合并后，你会收到电子邮件通知。 + +### [ 更多资料 ](../additional-material/git_workflow_scenarios/additional-material.md) + +## 接下来做什么呢？ + +为你第一次的贡献庆祝吧，不要忘记和你的朋友以及迷弟迷妹们分享我们的[网站](https://roshanjossey.github.io/first-contributions/#social-share)哟！ + +如果有任何疑问或想获得更多协助，欢迎加入我们的 [Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)！ + +还等什么，马上加入到其他项目的开发中去吧。为了方便你快速上手，我们收集了当前流行的众多代码仓库中，适合初学者解决的[问题列表](https://roshanjossey.github.io/first-contributions/#project-list)。 + +## 使用其他工具的教程 + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | + diff --git a/translations/README.zh-tw.md b/translations/README.zh-tw.md new file mode 100644 index 00000000000..9221a83f352 --- /dev/null +++ b/translations/README.zh-tw.md @@ -0,0 +1,115 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) + +# 第一次參與開源 + +萬事起頭難。特別是和其他人合作時，犯錯格外令人不舒服。不過，開源的本質就是和其他人合作。我們希望為初學者帶來一個簡單的方法來學習及參與開源項目。 + +閱讀文章和觀看教學會有所幫助。不過，有什麼方法能比在不會弄亂任何東西的情況下，實際動手做來得更好？本項目旨在指導初學者及簡化初學者參與開源的方式。記住：過程越輕鬆，學習效益越高。如果妳/你想要做出第一次貢獻，只需按照以下簡單步驟操作即可。跟你保證，這會很好玩 :) + +#### *如果你不喜歡使用指令列，[這裡有使用圖形界面工具的教學。]( #使用其他工具的教學)* + +fork this repository + +如果你的電腦上尚未安裝 git，請按照這個[安裝指引（英文）](https://help.github.com/articles/set-up-git/)進行安裝。 + +## 分叉（Fork）本代碼庫 + +點選圖示中的按鈕來 Fork 這個 Git 儲存庫。 +這個操作會將儲存庫分叉到你/妳的 GitHub 帳號下。 + +## 複製（Clone）代碼庫 + +clone this repository + +接下來，將複製後的儲存庫複製到你/妳的電腦上。點選圖示中的綠色按鈕，接著點選複製到剪貼簿按鈕（將儲存庫地址複製下來） + +隨後打開命令列視窗，鍵入如下 git 命令： + +``` +git clone "url you just copied" +``` +"url you just copied"（去掉雙引號）就是複製到妳/你帳戶名下的儲存庫地址。取得這鏈接地址的方法請見上一步。 + +copy URL to clipboard + +譬如： +``` +git clone https://github.com/this-is-you/first-contributions.git +``` + +'this-is-you' 指的就是你/妳自己的 GitHub 用戶名。這一步，會將你/妳的 first-contributions 儲存庫複製到你的電腦上。 + +## 新建一個分支 + +下面的命令能在命令行窗口中，把目錄切換到 first-contributions。 + +``` +cd first-contributions +``` +接下來使用 `git checkout` 命令建立一個程式碼分支： +``` +git checkout -b +``` + +譬如： +``` +git checkout -b add-david +``` + +（新分支的名稱不一定需要有 *add*。然而，在這個新分支的名稱加入 *add* 是一件合理的事情，因為這個分支的目的是將妳/你的名字添加到貢獻者列表中。） + +## 對程式碼進行修改，然後提交 (Commit) 修改 + +使用妳/你喜歡的文字編輯器打開 `Contributors.md` 這個文件，更新文件內容，將自己的名字加上去，然後存檔。在命令窗口執行 `git status`，這會列出被更動的文件。接著 `git add` 這命令則可以添加更動項目到分支裡，就像以下這條命令。 + +git status + +``` +git add Contributors.md +``` + +現在就可以使用 `git commit` 命令 commit（提交）你/妳的修改了。 +``` +git commit -m "Add to Contributors list" +``` +將 `` 替換為自己的名字 + +## 將更動發佈（Push）到 GitHub + +使用 `git push` 命令發佈代碼 +``` +git push origin +``` +將 `` 替換為之前新建的分支名稱。 + +## 提出 Pull Request 將你/妳的修改供他人審閱 + +前往先前自己 Fork 的 GitHub 儲存庫，會看到一個 `Compare & pull request` 的按鈕，點選該按鈕。 + +create a pull request + +接著再點選 `Create pull request` 按鈕，正式提交 pull request。 + +submit pull request + +不久之後，如果妳/你更改的文件與原本沒有衝突，我們會把所有的變化合併到這個項目的主分支。 +變更合併後，妳/你會收到通知 email。 + +## 接下來做什麼呢？ + +在[這個網站](https://roshanjossey.github.io/first-contributions/#social-share)慶祝妳/你的成就並跟朋友及追隨者分享。 + +如果有任何疑問或想獲得更多協助，歡迎加入我們的 [Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) + +現在就動手為其他專案貢獻你/妳的心力。我們整理了一個清單，裡面的專案都有簡單的議題可以著手。[去看看吧！](https://roshanjossey.github.io/first-contributions/#project-list) + +### [ 更多資料 ](../additional-material/git_workflow_scenarios/additional-material.md) + +## 使用其他工具的教學 + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/README.zul.md b/translations/README.zul.md new file mode 100644 index 00000000000..cf9248a3afa --- /dev/null +++ b/translations/README.zul.md @@ -0,0 +1,133 @@ +[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/) +[](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) +[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) +[![Open Source Helpers](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions) + + +# Iminikelo Yokuqala + + +Kulukhuni. Kuhlale kunzima okokuqala lapho wenza okuthile. Ikakhulukazi uma ubambisana, ukwenza amaphutha akuyona into ekhululekile. Sifuna ukwenza lula ukuthi abanikeli abasha abavulekile bafunde futhi bahlanganyele okokuqala. + +Ukufunda izihloko nokufundiswa kokubuka kungasiza, kodwa yini engcono kunokwenza okwamanje izinto ezenzakalweni? Le phrojekthi ihlose ukunikeza isiqondiso nokwenza ukuthi abaqalayo benze indlela yabo yokuqala. Uma ubheka ukwenza umnikelo wakho wokuqala, landela izinyathelo ezingezansi. + +#### *Uma ungakhululekile ngomugqa womyalo, [nansi izifundo ezisebenzisa amathuluzi we-GUI.](#Izinto-ezengeziwe)* + + +fork this repository + + +Uma ungenayo i-git kumshini wakho, [faka]( https://help.github.com/articles/set-up-git/). + +## Fometha le ndawo yokugcina + +Fometha le repo ngokuchofoza inkinobho yemfoloko phezulu kwaleli khasi. Lokhu kuzokhipha ikhophi yalesi sikhwama ku-akhawunti yakho. + +## Qalisa i-repository + +clone this repository + +Manje faka i-repo efakwe emshini wakho kumshini wakho. Yiya ku-akhawunti yakho ye-GitHub, vula i-repo evuliwe, chofoza inkinobho ye-clone bese uchofoza ikhophi ku-clipboard icon. + +Vula i-console bese ugijima umyalo we-git: + +``` +git clone "url you just copied" +``` +lapho "u-url osuvele ukopishe khona" (ngaphandle kwama-quote marks) yi-url kule ndawo yokugcina (ifomu lakho lephrojekthi). Bona izinyathelo zangaphambilini ukuthola i-url. + +copy URL to clipboard + + +Ngokwesibonelo: + +``` +git clone https://github.com/this-is-you/first-contributions.git +``` + +iphi this-is-youigama lomsebenzisi lakho le-GitHub. Lapha ukopisha okuqukethwe kokulondoloza kokuqala ku-GitHub kwikhompyutha yakho. + +## Dala igatsha + +Shintsha kwirekhodi lokugcina ekhompyutheni yakho (uma ungasekho kakade): + +``` +cd first-contributions +``` + +Manje dala igatsha usebenzisa `git checkout` umyalo: + +``` +git checkout -b +``` + +Ngokwesibonelo + +``` +git checkout -b engeza-adam-kowalski +``` +(Igama legatsha ayidingi ukuba izwi engeza kuwo, kodwa into enengqondo ukufaka ngoba inhloso yaleli gatsha ukwengeza igama lakho uhlu.) + +## Yenza ushintsho oludingekile bese wenza lezo zinguquko + +Manje `Contributors.md` ifayela evulekile kumhleli wombhalo, engeza igama lakho kuyo. Ungayifaki ekuqaleni noma ekupheleni kwefayela. Beka noma kuphi phakathi. Manje, londoloza ifayela. + +git status + +Uma uya encwadini yomhlahlandlela bese wenza umyalo `git status`, uzobona kukhona izinguquko. + + +Engeza lezo zinguquko egatsheni owake wadala usebenzisa `git add` umyalo: + +``` +git add Contributors.md +``` + +Manje yenza lezo zinguquko usebenzisa `git commit` umyalo: + +``` +git commit -m "Add to Contributors list" +``` + +ukufaka esikhundleni `` ngegama lakho. + +## Shintsha izinguquko ku-GitHub + +Pushisa izinguquko zakho usebenzisa umyalo `git push`: + +``` +git push origin +``` + +kufaka esikhundleni `` segama legatsha owadala ngaphambilini. + +## Thumela izinguquko zakho ukuze zibuyekezwe + +Uma uya endaweni yakho yokugcina ku-GitHub, uzobona `Compare & pull request` inkinobho. Chofoza kuleyo nkinobho. + +create a pull request + +Manje thumela isicelo sokudonsa. + +submit pull request + +Ngokushesha ngizohlanganisa zonke izinguquko zakho zibe yigatsha eliyinhloko laphrojekthi. Uzothola i-imeyili yesaziso uma izinguquko sezihlanganisiwe. + +## Ungaphi lapho? + +Siyakuhalalisela! Usanda kuqedela umshini ojwayelekile -> clone -> edit -> PR ukuhamba komsebenzi ozohlangana ngaso sonke isikhathi njengomnikelo! + +Gubha umnikelo wakho bese uwabelana nabangani bakho nabalandeli ngokuya kuhlelo [lokusebenza lewebhu](https://roshanjossey.github.io/first-contributions/#social-share). + +Ungakwazi ukujoyina ithimba lethu elihle uma kwenzeka udinga noma yiluphi usizo noma unemibuzo. [Joyina ithimba le-slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA). + +Manje ake siqale ngokunikela ngeminye imiklamo. Senze uhlu lwamaphrojekthi ngezinkinga ezilula ongaqala ngazo. Hlola [uhlu lwamaphrojekthi kuhlelo lokusebenza lewebhu .](https://roshanjossey.github.io/first-contributions/#project-list). + +### [Izinto ezengeziwe](../additional-material/git_workflow_scenarios/additional-material.md) + + +## Izinto ezengeziwe + +| GitHub Desktop | Visual Studio 2017 | GitKraken | VS Code | Sourcetree App | IntelliJ IDEA | +| --- | --- | --- | --- | --- | --- | +| [GitHub Desktop](../gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](../gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](../gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](../gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](../gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](../gui-tool-tutorials/github-windows-intellij-tutorial.md) | diff --git a/translations/Translations.md b/translations/Translations.md new file mode 100644 index 00000000000..fd375b639e9 --- /dev/null +++ b/translations/Translations.md @@ -0,0 +1,74 @@ +# Translations + +| | Translated Link | +| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- | +| ગુજરાતી | [ગુજરાતી](README.guj.md) | +| हिन्दी | [हिन्दी](README.hi.md) | +| मराठी | [मराठी](README.mr.md) | +| മലയാളം | [മലയാളം](README.ml.md) | +| ಕನ್ನಡ | [ಕನ್ನಡ](README.ka.md) | +| తెలుగు | [తెలుగు](README.te.md) | +| छत्तीसगढ़ी | [छत्तीसगढ़ी](README.hne.md) | +| ਪਨਜਾਬੀ | [ਪਨਜਾਬੀ](README.pb.md) | +| বাংলা বাংলা | [বাংলা](README.bn.md) | +| தமிழ் தமிழ் | [தமிழ்](README.ta.md) | +| မြန်မာ | [မြန်မာ](README.mm_unicode.md) | +| Bahasa Indonesia | [Bahasa Indonesia](README.id.md) | +| Català | [Català](README.ca.md) | +| Français | [Français](README.fr.md) | +| Español | [Español](README.es.md) | +| Nederlands | [Nederlands](README.nl.md) | +| Русский язык | [Русский язык](README.ru.md) | +| Bulgarian | [Bulgarian](README.bg.md) | +| Македонски | [Македонски](README.mk.md) | +| Magyar | [Magyar](README.hu.md) | +| Slovenčina | [Slovenčina](README.slk.md) | +| 日本語 | [日本語](README.ja.md) | +| Tiếng Việt | [Tiếng Việt](README.vn.md) | +| Polski | [Polski](README.pl.md) | +| فارسی | [فارسی](README.fa.md) | +| Persian_Finglish | [Persian_Finglish](README.fa.en.md) | +| Lietuvių kalba | [Lietuvių kalba](README.lt.md) | +| [한국어 [한국어 | [한국어](README.ko.md) | +| Deutsch | [Deutsch](README.de.md) | +| 中文 中文 | [中文(Simplified)](README.zh-cn.md), [中文(Traditional)](README.zh-tw.md) | +| ελληνικά | [ελληνικά](README.gr.md) | +| العربية | [العربية](README.ar.md) | +| Українська | [Українська](README.ua.md) | +| Português (Brasil) | [Português (Brasil)](README.pt_br.md) | +| Português (Portugal) | [Português (Portugal)](README.pt-pt.md) | +| Italiano | [Italiano](README.it.md) | +| ภาษาไทย | [ภาษาไทย](README.th.md) | +| 󠁥󠁳󠁧󠁡Galego | [Galego](README.gl.md) | +| नेपाली | [नेपाली](README.np.md) | +| اردو | [اردو](README.ur.md) | +| Limba Română Limba Română | [Limba Română](README.ro.md) | +| English | [English](../README.md) | +| English (Pirate) | [English (Pirate)](README.en-pirate.md) | +| Türkçe | [Türkçe](README.tr.md) | +| עברית | [עברית](README.hb.md) | +| Bahasa Melayu / بهاس ملايو‎ / Malay | [Bahasa Melayu / بهاس ملايو‎ / Malay](README.my.md) | +| Czech | [Czech](README.cs.md) | +| Slovenščina | [Slovenščina](README.sl.md) | +| Norsk | [Norsk](README.no.md) | +| Svenska | [Svenska](README.se.md) | +| Dansk | [Dansk](README.da.md) | +| المصرية | [المصرية](README.eg.md) | +| Wikang Filipino | [Wikang Filipino](README.tl.md) | +| Қазақша | [Қазақша](README.kz.md) | +| Afrikaans (South Africa) | [Afrikaans (South Africa)](README.afk.md) | +| Zulu (South Africa) | [Zulu (South Africa)](README.zul.md) | +| Kiswahili (Kenya) | [Kiswahili (Kenya)](README.kws.md) | +| ქართული | [ქართული](README.ge.md) | +| Igbo (Nigeria) | [Igbo (Nigeria)](README.igb.md) +| Yoruba (Nigeria) | [Igbo (Nigeria)](README.yor.md) | +| Suomeksi | [Suomeksi](README.fi.md) | +| Español de México | [Español de México](README.mx.md) | +| Српски | [Српски](README.sr.md) | +| Latvia | [Latvia](README.lv.md) | +| Shqip | [Shqip](README.al.md) | +| Беларуская мова | [Беларуская мова](README.by.md) | +| Azərbaycan dili | [Azərbaycan dili](translations/README.aze.md) | +| Bosanski |[Bosanski](README.bih.md)| +| پښتو |[پښتو - Pashto](README.ps.md) +| ພາສາລາວ | [ພາສາລາວ](README.la.md) |