Merge branch 'main' into dev

This commit is contained in:
Roshan Jossy
2025-09-29 11:24:52 +02:00
committed by GitHub
65 changed files with 3410 additions and 1995 deletions
+73 -73
View File
@@ -10,77 +10,77 @@ If you're making changes to a translation, please request a review from our prev
| Language Name | Name in English | Reviewers|
|---|---|---|
| Afrikaans | [Afrikaans](../translations/README.afk.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/36197725?v=4" alt="@zecollokaris" />](https://github.com/zecollokaris) |
| Albanian | [Albanian](../translations/README.al.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/40631828?v=4" alt="RronKurtishi" />](https://github.com/RronKurtishi) [<img width="100" src="https://avatars.githubusercontent.com/u/98396887?s=400&v=4" alt="RronKurtishi" />](https://github.com/auronvila) |
| العربية | [Arabic](../translations/README.ar.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/83532081?v=4" alt="OsaidAlhomedy" />](https://github.com/OsaidAlhomedy) [<img width="100" src="https://avatars.githubusercontent.com/u/97640062?v=4" alt="AlaaYlula" />](https://github.com/AlaaYlula) [<img width="100" src="https://avatars.githubusercontent.com/u/60319236?v=4" alt="Laith-Alayassa" />](https://github.com/Laith-Alayassa) |
| Azerbaijani | [Azerbaijani](../translations/README.aze.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/60487349?v=4" alt="@isakurbanov744" />](https://github.com/isakurbanov744) [<img width="100" src="https://avatars.githubusercontent.com/u/58222828?v=4" alt="@Ahm3tJ4f" />](https://github.com/Ahm3tJ4f) |
| Bulgarian | [Bulgarian](../translations/README.bg.md) | []() |
| Bosnian | [Bosnian](../translations/README.bih.md) | []() |
| বাংলা | [Bengali](../translations/README.bn.md) | [<img width="100" src="https://avatars3.githubusercontent.com/u/12910423?s=460&v=4" alt="@cse031sust02" />](https://github.com/cse031sust02) |
| Belarusian | [Belarusian](../translations/README.by.md) | []() |
| Català | [Catalan](../translations/README.ca.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/16263046?s=460&v=4" alt="@Sergih28" />](https://github.com/Sergih28) |
| čeština | [Czech](../translations/README.cs.md) | []() |
| Danish | [Danish](../translations/README.da.md) | [<img width="100" src="https://avatars1.githubusercontent.com/u/15271858?s=460&v=4" alt="@7013145" />](https://github.com/7013145) |
| Deutsch | [German](../translations/README.de.md) | [<img width="100" src="https://avatars3.githubusercontent.com/u/22977266?s=460&v=4" alt="@lkreimann" />](https://github.com/lkreimann) |
| المصرية | [Egyptian](../translations/README.eg.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/12827629?s=460&v=4" alt="@MichaelKMalak" />](https://github.com/MichaelKMalak) |
| English (Pirate) | [English (Pirate)](../translations/README.en-pirate.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/956290?s=460&v=4" alt="@lukeoliff" />](https://github.com/lukeoliff) |
| Español | [Spanish](../translations/README.es.md) | [<img width="100" src="https://avatars3.githubusercontent.com/u/16923944?s=460&v=4" alt="@yirini" />](https://github.com/yirini) [<img width="100" src="https://avatars.githubusercontent.com/u/10425834?v=4" alt="@aaossa" />](https://github.com/aaossa) |
| فارسی | [Persian](../translations/README.fa.md) | [<img width="100" src="https://avatars2.githubusercontent.com/u/20030805?s=460&v=4" alt="@ThirdScript" />](https://github.com/ThirdScript) |
| Finnish | [Finnish](../translations/README.fi.md) | []() |
| Français | [French](../translations/README.fr.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/13402464?s=460&v=4" alt="@LePetitRenard" />](https://github.com/LePetitRenard) |
| ქართული | [Georgian](../translations/README.ka.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/9116447?s=460&v=4" alt="@iko1133" />](https://github.com/iko1133) |
| Galego | [Galician](../translations/README.gl.md) | [<img width="100" src="https://avatars1.githubusercontent.com/u/16878891?s=460&v=4" alt="@siderio2" />](https://github.com/siderio2) |
| Greek | [Greek](../translations/README.gr.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/63111742?v=4" alt="@adreaskar" />](https://github.com/adreaskar) [<img width="100" src="https://avatars.githubusercontent.com/u/19299306?v=4" alt="@porfanid" />](https://github.com/porfanid) |
| Gujarati | [Gujarati](../translations/README.guj.md) | [<img width="100" src="https://avatars2.githubusercontent.com/u/38134283?s=460&v=4" alt="@smitgajjar" />](https://github.com/smitgajjar) [<img width="100" src="https://avatars.githubusercontent.com/u/16669911?v=4" alt="@kaushalgosaliya5" />](https://github.com/kaushalgosaliya5/) |
| Hausa | [Hausa](../translations/README.hau.md) | []() |
| עברית | [Hebrew](../translations/README.hb.md) | [<img width="100" src="https://avatars1.githubusercontent.com/u/23402988?s=460&v=4" alt="@TomerPacific" />](https://github.com/TomerPacific) |
| हिन्दी | [Hindi](../translations/README.hi.md) | [<img width="100" src="https://avatars2.githubusercontent.com/u/4654382?s=460&v=4" alt="@arshadkazmi42" />](https://github.com/arshadkazmi42) [<img width="100" src="https://avatars2.githubusercontent.com/u/7047079?s=460&v=4" alt="@sara-02" />](https://github.com/sara-02) [<img width="100" src="https://avatars.githubusercontent.com/u/20799404?v=4" alt="shrut1996" />](https://github.com/shrut1996) |
| Chhattisgarhi | [Chhattisgarhi](../translations/README.hne.md) | [<img width="100" src="https://avatars2.githubusercontent.com/u/54806739?s=400&v=4" alt="@pradyyadav" />](https://github.com/pradyyadav) |
| Magyar | [Hungarian](../translations/README.hu.md) | []() |
| Armenian | [Armenian](../translations/README.hy.md) | []() |
| Indonesian | [Indonesian](../translations/README.id.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/315048?s=460&v=4" alt="@hahn" />](https://github.com/hahn) |
| Igbo | [Igbo](../translations/README.igb.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/36197725?v=4" alt="@zecollokaris" />](https://github.com/zecollokaris) []() |
| Italiano | [Italian](../translations/README.it.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/22260641?s=460&v=4" alt="@platipo" />](https://github.com/platipo) |
| 日本語 | [Japanese](../translations/README.ja.md) | [<img width="100" src="https://avatars3.githubusercontent.com/u/12928246?s=460&v=4" alt="@cbondurant" />](https://github.com/cbondurant) |
| ಕನ್ನಡ | [Kannada](../translations/README.ka.md) | []() |
| 한국어 | [Korean](../translations/README.ko.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/2732120?s=460&v=4" alt="@espozbob" />](https://github.com/espozbob) |
| Kiswahili | [Kiswahili](../translations/README.ksw.md) |[<img width="100" src="https://avatars.githubusercontent.com/u/36197725?v=4" alt="@zecollokaris" />](https://github.com/zecollokaris) []() |
| Kazakh | [Kazakh](../translations/README.kz.md) | [<img width="100" src="https://avatars3.githubusercontent.com/u/12928246?s=460&v=4" alt="@kurshakuz" />](https://github.com/kurshakuz) |
| Lietuvių kalba | [Lithuanian](../translations/README.lt.md) | [<img width="100" src="https://avatars1.githubusercontent.com/u/9092712?s=460&v=4" alt="@neone35" />](https://github.com/neone35) |
| Latviešu valoda | [Latvian](../translations/README.lv.md) | []() |
| | [me](../translations/README.me.md) | [<img width="100" src="https://avatars1.githubusercontent.com/u/9092712?s=460&v=4" alt="@neone35">]() |
| Македонски | [Macedonian](../translations/README.mk.md) | []() |
| മലയാളം | [Malayalam](../translations/README.ml.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/3657426?v=4" alt="@yedhukrishnan">](https://github.com/yedhukrishnan) |
| Burmese | [Burmese](../translations/README.mm_unicode.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/13135332?s=460&v=4" alt="@lwinkyawmyat" />](https://github.com/lwinkyawmyat) |
| मराठी | [Marathi](../translations/README.mr.md) | [<img width="100" src="https://avatars1.githubusercontent.com/u/16685565?s=460&v=4" alt="@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) | [<img width="100" src="https://avatars0.githubusercontent.com/u/3897815?s=460&v=4" alt="@MJMajoor" />](https://github.com/MJMajoor) |
| Norsk | [Norwegian](../translations/README.no.md) | []() |
| नेपाली | [Nepali](../translations/README.np.md) | [<img width="100" src="https://avatars2.githubusercontent.com/u/2145263?s=460&v=4" alt="@milap-neupane" />](https://github.com/milap-neupane) |
| ਪੰਜਾਬੀ | [Punjabi](../translations/README.pa.md) | []() |
| Polski | [Polish](../translations/README.pl.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/3372341?s=460&v=4" alt="@P1X3L0V4" />](https://github.com/P1X3L0V4) [<img width="100" src="https://avatars2.githubusercontent.com/u/1311358?v=4" alt="@mikowhy" />](https://github.com/mikowhy) |
| Português | [Portugues (Portugal)](../translations/README.pt-pt.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/36346554?v=4" alt="@RamosCSV" />](https://github.com/RamosCSV) |
| Português do Brasil | [Portugues (Brazil)](../translations/README.pt-br.md) | [<img width="100" src="https://avatars2.githubusercontent.com/u/10578275?s=460&v=4" alt="@OtacilioN" />](https://github.com/OtacilioN) [<img width="100" src="https://avatars2.githubusercontent.com/u/47339825?s=460&v=4" alt="@gabrielsanttana" />](https://github.com/gabrielsanttana)|
| Română | [Romanian](../translations/README.ro.md) | [ <img width="100" src="https://avatars2.githubusercontent.com/u/20670448?s=460&v=4" alt="@dp97" />](https://github.com/dp97) |
| Русский | [Russian](../translations/README.ru.md) | [<img width="100" src="https://avatars2.githubusercontent.com/u/4745723?s=460&v=4" alt="@ayanovsk" />](https://github.com/ayanovsk) |
| Svenska | [Swedish](../translations/README.sv.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/2447741?s=460&v=4" alt="@jcer" />](https://github.com/jcer) |
| Sinhala | [Sinhala](../translations/README.si.md) | []() |
| Sindhi | [Sindhi](../translations/README.sindhi.md) | []() |
| Slovenčina | [Slovak](../translations/README.sk.md) | [<img width="100" src="https://avatars3.githubusercontent.com/u/16558136?s=460&v=4" alt="@CoderKlemen" />](https://github.com/CoderKlemen) |
| Slovenščina | [Slovenian](../translations/README.slk.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/11976353?s=460&v=4" alt="@hercegtomas" />](https://github.com/hercegtomas) |
| Serbian | [Serbian](../translations/README.sr.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/35745051?v=4" alt="@Mateja3m" />](https://github.com/Mateja3m) |
| தமிழ் | [Tamil](../translations/README.ta.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/7114806?v=4" alt="@sathishkumar-manogaran" />](https://github.com/sathishkumar-manogaran) |
| తెలుగు | [Telugu](../translations/README.te.md) | []() |
| ไทย | [Thai](../translations/README.th.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/5433758?s=460&v=4" alt="@AimeTPGM" />](https://github.com/AimeTPGM) |
| Tagalog | [Tagalog](../translations/README.tl.md) | []() |
| Türkçe | [Turkish](../translations/README.tr.md) | [<img width="100" src="https://avatars3.githubusercontent.com/u/32689837?s=460&v=4" alt="@yamac-kurtulus" />](https://github.com/yamac-kurtulus) |
| Українська | [Ukrainian](../translations/README.ua.md) | []() |
| Universal Alien | [Universal Alien](../translations/README.un-aln.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/68442560?v=4" alt="@debjit-bw" />]() |
| اردو | [Urdu](../translations/README.ur.md) | [<img width="100" src="https://avatars3.githubusercontent.com/u/4142795?s=460&v=4" alt="@Shhzdmrz" />](https://github.com/Shhzdmrz) |
| Tiếng Việt | [Vietnamese](../translations/README.vn.md) | [<img width="100" src="https://avatars3.githubusercontent.com/u/12371875?s=460&v=4" alt="@tranlyvu" />](https://github.com/tranlyvu) |
| Yorùbá | [Yorùbá](../translations/README.yor.md) | []() |
| 中文 | [Chinese (Simplified)](../translations/README.zh-cn.md) | [<img width="100" src="https://avatars2.githubusercontent.com/u/6414741?s=400&v=4" alt="@yuzhoujr" />](https://github.com/yuzhoujr) |
| 中文 | [Chinese (Traditional)](../translations/README.zh-tw.md) | [<img width="100" src="https://avatars2.githubusercontent.com/u/27748281?s=460&v=4" alt="@WeiChienHsu" />](https://github.com/WeiChienHsu) |
| Zulu | [Zulu](../translations/README.zu.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/36197725?v=4" alt="@zecollokaris" />](https://github.com/zecollokaris) []() |
| Afrikaans | [Afrikaans](../docs/translations/README.afk.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/36197725?v=4" alt="@zecollokaris" />](https://github.com/zecollokaris) |
| Albanian | [Albanian](../docs/translations/README.al.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/40631828?v=4" alt="RronKurtishi" />](https://github.com/RronKurtishi) [<img width="100" src="https://avatars.githubusercontent.com/u/98396887?s=400&v=4" alt="RronKurtishi" />](https://github.com/auronvila) |
| العربية | [Arabic](../docs/translations/README.ar.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/83532081?v=4" alt="OsaidAlhomedy" />](https://github.com/OsaidAlhomedy) [<img width="100" src="https://avatars.githubusercontent.com/u/97640062?v=4" alt="AlaaYlula" />](https://github.com/AlaaYlula) [<img width="100" src="https://avatars.githubusercontent.com/u/60319236?v=4" alt="Laith-Alayassa" />](https://github.com/Laith-Alayassa) |
| Azerbaijani | [Azerbaijani](../docs/translations/README.aze.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/60487349?v=4" alt="@isakurbanov744" />](https://github.com/isakurbanov744) [<img width="100" src="https://avatars.githubusercontent.com/u/58222828?v=4" alt="@Ahm3tJ4f" />](https://github.com/Ahm3tJ4f) |
| Bulgarian | [Bulgarian](../docs/translations/README.bg.md) | []() |
| Bosnian | [Bosnian](../docs/translations/README.bih.md) | []() |
| বাংলা | [Bengali](../docs/translations/README.bn.md) | [<img width="100" src="https://avatars3.githubusercontent.com/u/12910423?s=460&v=4" alt="@cse031sust02" />](https://github.com/cse031sust02) |
| Belarusian | [Belarusian](../docs/translations/README.by.md) | []() |
| Català | [Catalan](../docs/translations/README.ca.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/16263046?s=460&v=4" alt="@Sergih28" />](https://github.com/Sergih28) |
| čeština | [Czech](../docs/translations/README.cs.md) | []() |
| Danish | [Danish](../docs/translations/README.da.md) | [<img width="100" src="https://avatars1.githubusercontent.com/u/15271858?s=460&v=4" alt="@7013145" />](https://github.com/7013145) |
| Deutsch | [German](../docs/translations/README.de.md) | [<img width="100" src="https://avatars3.githubusercontent.com/u/22977266?s=460&v=4" alt="@lkreimann" />](https://github.com/lkreimann) |
| المصرية | [Egyptian](../docs/translations/README.eg.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/12827629?s=460&v=4" alt="@MichaelKMalak" />](https://github.com/MichaelKMalak) |
| English (Pirate) | [English (Pirate)](../docs/translations/README.en-pirate.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/956290?s=460&v=4" alt="@lukeoliff" />](https://github.com/lukeoliff) |
| Español | [Spanish](../docs/translations/README.es.md) | [<img width="100" src="https://avatars3.githubusercontent.com/u/16923944?s=460&v=4" alt="@yirini" />](https://github.com/yirini) [<img width="100" src="https://avatars.githubusercontent.com/u/10425834?v=4" alt="@aaossa" />](https://github.com/aaossa) |
| فارسی | [Persian](../docs/translations/README.fa.md) | [<img width="100" src="https://avatars2.githubusercontent.com/u/20030805?s=460&v=4" alt="@ThirdScript" />](https://github.com/ThirdScript) |
| Finnish | [Finnish](../docs/translations/README.fi.md) | []() |
| Français | [French](../docs/translations/README.fr.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/13402464?s=460&v=4" alt="@LePetitRenard" />](https://github.com/LePetitRenard) |
| ქართული | [Georgian](../docs/translations/README.ka.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/9116447?s=460&v=4" alt="@iko1133" />](https://github.com/iko1133) |
| Galego | [Galician](../docs/translations/README.gl.md) | [<img width="100" src="https://avatars1.githubusercontent.com/u/16878891?s=460&v=4" alt="@siderio2" />](https://github.com/siderio2) |
| Greek | [Greek](../docs/translations/README.gr.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/63111742?v=4" alt="@adreaskar" />](https://github.com/adreaskar) [<img width="100" src="https://avatars.githubusercontent.com/u/19299306?v=4" alt="@porfanid" />](https://github.com/porfanid) |
| ગુજરાતી | [Gujarati](../docs/translations/README.guj.md) | [<img width="100" src="https://avatars2.githubusercontent.com/u/38134283?s=460&v=4" alt="@smitgajjar" />](https://github.com/smitgajjar) [<img width="100" src="https://avatars.githubusercontent.com/u/16669911?v=4" alt="@kaushalgosaliya5" />](https://github.com/kaushalgosaliya5/) |
| Hausa | [Hausa](../docs/translations/README.hau.md) | []() |
| עברית | [Hebrew](../docs/translations/README.hb.md) | [<img width="100" src="https://avatars1.githubusercontent.com/u/23402988?s=460&v=4" alt="@TomerPacific" />](https://github.com/TomerPacific) |
| हिन्दी | [Hindi](../docs/translations/README.hi.md) | [<img width="100" src="https://avatars2.githubusercontent.com/u/4654382?s=460&v=4" alt="@arshadkazmi42" />](https://github.com/arshadkazmi42) [<img width="100" src="https://avatars2.githubusercontent.com/u/7047079?s=460&v=4" alt="@sara-02" />](https://github.com/sara-02) [<img width="100" src="https://avatars.githubusercontent.com/u/20799404?v=4" alt="shrut1996" />](https://github.com/shrut1996) |
| Chhattisgarhi | [Chhattisgarhi](../docs/translations/README.hne.md) | [<img width="100" src="https://avatars2.githubusercontent.com/u/54806739?s=400&v=4" alt="@pradyyadav" />](https://github.com/pradyyadav) |
| Magyar | [Hungarian](../docs/translations/README.hu.md) | []() |
| Armenian | [Armenian](../docs/translations/README.hy.md) | []() |
| Indonesian | [Indonesian](../docs/translations/README.id.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/315048?s=460&v=4" alt="@hahn" />](https://github.com/hahn) |
| Igbo | [Igbo](../docs/translations/README.igb.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/36197725?v=4" alt="@zecollokaris" />](https://github.com/zecollokaris) []() |
| Italiano | [Italian](../docs/translations/README.it.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/22260641?s=460&v=4" alt="@platipo" />](https://github.com/platipo) |
| 日本語 | [Japanese](../docs/translations/README.ja.md) | [<img width="100" src="https://avatars3.githubusercontent.com/u/12928246?s=460&v=4" alt="@cbondurant" />](https://github.com/cbondurant) |
| ಕನ್ನಡ | [Kannada](../docs/translations/README.ka.md) | []() |
| 한국어 | [Korean](../docs/translations/README.ko.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/2732120?s=460&v=4" alt="@espozbob" />](https://github.com/espozbob) |
| Kiswahili | [Kiswahili](../docs/translations/README.kws.md) |[<img width="100" src="https://avatars.githubusercontent.com/u/36197725?v=4" alt="@zecollokaris" />](https://github.com/zecollokaris) []() |
| Kazakh | [Kazakh](../docs/translations/README.kz.md) | [<img width="100" src="https://avatars3.githubusercontent.com/u/12928246?s=460&v=4" alt="@kurshakuz" />](https://github.com/kurshakuz) |
| Lietuvių kalba | [Lithuanian](../docs/translations/README.lt.md) | [<img width="100" src="https://avatars1.githubusercontent.com/u/9092712?s=460&v=4" alt="@neone35" />](https://github.com/neone35) |
| Latviešu valoda | [Latvian](../docs/translations/README.lv.md) | []() |
| | [me](../docs/translations/README.me.md) | [<img width="100" src="https://avatars1.githubusercontent.com/u/9092712?s=460&v=4" alt="@neone35">]() |
| Македонски | [Macedonian](../docs/translations/README.mk.md) | []() |
| മലയാളം | [Malayalam](../docs/translations/README.ml.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/3657426?v=4" alt="@yedhukrishnan">](https://github.com/yedhukrishnan) |
| Burmese | [Burmese](../docs/translations/README.mm_unicode.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/13135332?s=460&v=4" alt="@lwinkyawmyat" />](https://github.com/lwinkyawmyat) |
| मराठी | [Marathi](../docs/translations/README.mr.md) | [<img width="100" src="https://avatars1.githubusercontent.com/u/16685565?s=460&v=4" alt="@bantya" />](https://github.com/bantya) |
| Español de México | [Spanish of Mexico](../docs/translations/README.mx.md) | []() |
| Bahasa Melayu | [Malay](../docs/translations/README.my.md) | []() |
| Nederlandse | [Dutch](../docs/translations/README.nl.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/3897815?s=460&v=4" alt="@MJMajoor" />](https://github.com/MJMajoor) |
| Norsk | [Norwegian](../docs/translations/README.no.md) | []() |
| नेपाली | [Nepali](../docs/translations/README.np.md) | [<img width="100" src="https://avatars2.githubusercontent.com/u/2145263?s=460&v=4" alt="@milap-neupane" />](https://github.com/milap-neupane) |
| ਪੰਜਾਬੀ | [Punjabi](../docs/translations/README.pb.md) | []() |
| Polski | [Polish](../docs/translations/README.pl.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/3372341?s=460&v=4" alt="@P1X3L0V4" />](https://github.com/P1X3L0V4) [<img width="100" src="https://avatars2.githubusercontent.com/u/1311358?v=4" alt="@mikowhy" />](https://github.com/mikowhy) |
| Português | [Portugues (Portugal)](../docs/translations/README.pt-pt.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/36346554?v=4" alt="@RamosCSV" />](https://github.com/RamosCSV) |
| Português do Brasil | [Portugues (Brazil)](../docs/translations/README.pt_br.md) | [<img width="100" src="https://avatars2.githubusercontent.com/u/10578275?s=460&v=4" alt="@OtacilioN" />](https://github.com/OtacilioN) [<img width="100" src="https://avatars2.githubusercontent.com/u/47339825?s=460&v=4" alt="@gabrielsanttana" />](https://github.com/gabrielsanttana)|
| Română | [Romanian](../docs/translations/README.ro.md) | [ <img width="100" src="https://avatars2.githubusercontent.com/u/20670448?s=460&v=4" alt="@dp97" />](https://github.com/dp97) |
| Русский | [Russian](../docs/translations/README.ru.md) | [<img width="100" src="https://avatars2.githubusercontent.com/u/4745723?s=460&v=4" alt="@ayanovsk" />](https://github.com/ayanovsk) |
| Svenska | [Swedish](../docs/translations/README.se.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/2447741?s=460&v=4" alt="@jcer" />](https://github.com/jcer) |
| Sinhala | [Sinhala](../docs/translations/README.si.md) | []() |
| Sindhi | [Sindhi](../docs/translations/README.sindhi.md) | []() |
| Slovenčina | [Slovak](../docs/translations/README.sk.md) | [<img width="100" src="https://avatars3.githubusercontent.com/u/16558136?s=460&v=4" alt="@CoderKlemen" />](https://github.com/CoderKlemen) |
| Slovenščina | [Slovenian](../docs/translations/README.slk.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/11976353?s=460&v=4" alt="@hercegtomas" />](https://github.com/hercegtomas) |
| Serbian | [Serbian](../docs/translations/README.sr.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/35745051?v=4" alt="@Mateja3m" />](https://github.com/Mateja3m) |
| தமிழ் | [Tamil](../docs/translations/README.ta.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/7114806?v=4" alt="@sathishkumar-manogaran" />](https://github.com/sathishkumar-manogaran) |
| తెలుగు | [Telugu](../docs/translations/README.te.md) | []() |
| ไทย | [Thai](../docs/translations/README.th.md) | [<img width="100" src="https://avatars0.githubusercontent.com/u/5433758?s=460&v=4" alt="@AimeTPGM" />](https://github.com/AimeTPGM) |
| Tagalog | [Tagalog](../docs/translations/README.tl.md) | []() |
| Türkçe | [Turkish](../docs/translations/README.tr.md) | [<img width="100" src="https://avatars3.githubusercontent.com/u/32689837?s=460&v=4" alt="@yamac-kurtulus" />](https://github.com/yamac-kurtulus) |
| Українська | [Ukrainia n](../docs/translations/README.ua.md) | []() |
| Universal Alien | [Universal Alien](../docs/translations/README.un-aln.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/68442560?v=4" alt="@debjit-bw" />]() |
| اردو | [Urdu](../docs/translations/README.ur.md) | [<img width="100" src="https://avatars3.githubusercontent.com/u/4142795?s=460&v=4" alt="@Shhzdmrz" />](https://github.com/Shhzdmrz) |
| Tiếng Việt | [Vietnamese](../docs/translations/README.vn.md) | [<img width="100" src="https://avatars3.githubusercontent.com/u/12371875?s=460&v=4" alt="@tranlyvu" />](https://github.com/tranlyvu) |
| Yorùbá | [Yorùbá](../docs/translations/README.yor.md) | []() |
| 中文 | [Chinese (Simplified)](../docs/translations/README.zh-cn.md) | [<img width="100" src="https://avatars2.githubusercontent.com/u/6414741?s=400&v=4" alt="@yuzhoujr" />](https://github.com/yuzhoujr) |
| 中文 | [Chinese (Traditional)](../docs/translations/README.zh-tw.md) | [<img width="100" src="https://avatars2.githubusercontent.com/u/27748281?s=460&v=4" alt="@WeiChienHsu" />](https://github.com/WeiChienHsu) |
| Zulu | [Zulu](../docs/translations/README.zul.md) | [<img width="100" src="https://avatars.githubusercontent.com/u/36197725?v=4" alt="@zecollokaris" />](https://github.com/zecollokaris) []() |
+1
View File
@@ -393,3 +393,4 @@ FodyWeavers.xsd
desktop.ini
.codegpt
.qodo
+1052 -1209
View File
File diff suppressed because it is too large Load Diff
+4 -6
View File
@@ -3,7 +3,6 @@
[![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](docs/translations/Translations.md)._
<kbd>[<img title="Shqip" alt="Shqip" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/al.svg" width="22">](docs/translations/README.al.md)</kbd>
<kbd>[<img title="Armenian" alt="Armenian" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/am.svg" width="22">](docs/translations/README.arm.md)</kbd>
<kbd>[<img title="Uzbek" alt="Uzbek language" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/uz.svg" width="22">](docs/translations/README.uz.md)</kbd>
@@ -16,7 +15,7 @@
<kbd>[<img title="Czech" alt="Czech" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/cz.svg" width="22">](docs/translations/README.cs.md)</kbd>
<kbd>[<img title="Deutsch" alt="Deutsch" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/de.svg" width="22">](docs/translations/README.de.md)</kbd>
<kbd>[<img title="Dansk" alt="Dansk" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/dk.svg" width="22">](docs/translations/README.da.md)</kbd>
<kbd>[<img title="العربية" alt="العربية" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/eg.svg" width="22">](docs/translations/README.eg.md)</kbd>
<kbd>[<img title="المصرية" alt="المصرية" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/eg.svg" width="22">](docs/translations/README.eg.md)</kbd>
<kbd>[<img title="Dezéiriya" alt="Dezéiriya" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/dz.svg" width="22">](docs/translations/README.dz.md)</kbd>
<kbd>[<img title="Español de España" alt="Español de España" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/es.svg" width="22">](docs/translations/README.es.md)</kbd>
<kbd>[<img title="Française" alt="Française" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/fr.svg" width="22">](docs/translations/README.fr.md)</kbd>
@@ -30,7 +29,6 @@
<kbd>[<img title="हिंदी/ગુજરાતી/मराठी/മലയാളം/ಕನ್ನಡ/తెలుగు/छत्तीसगढ़ी/বাংলা/தமிழ்" alt="हिंदी/ગુજરાતી/मराठी/മലയാളം/ಕನ್ನಡ/తెలుగు/छत्तीसगढ़ी/বাংলা/தமிழ்" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/in.svg" width="22">](docs/translations/Translations.md)</kbd>
<kbd>[<img title="தமிழ்" alt="தமிழ்" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/lk.svg" width="22">](docs/translations/README.ta.md)</kbd>
<kbd>[<img title="فارسی" alt="فارسی" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/ir.svg" width="22">](docs/translations/README.fa.md)</kbd>
<kbd>[<img title="پښتو" alt="پښتو" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/af.svg" width="22">](docs/translations/README.pus.md)</kbd>
<kbd>[<img title="Italiano" alt="Italiano" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/it.svg" width="22">](docs/translations/README.it.md)</kbd>
<kbd>[<img title="日本語" alt="日本語" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/jp.svg" width="22">](docs/translations/README.ja.md)</kbd>
<kbd>[<img title="සිංහල" alt="සිංහල" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/lk.svg" width="22">](docs/translations/README.si.md)</kbd>
@@ -52,7 +50,7 @@
<kbd>[<img title="Polski" alt="Polski" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/pl.svg" width="22">](docs/translations/README.pl.md)</kbd>
<kbd>[<img title="Português (Portugal)" alt="Português (Portugal)" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/pt.svg" width="22">](docs/translations/README.pt-pt.md)</kbd>
<kbd>[<img title="Русский язык" alt="Русский язык" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/ru.svg" width="22">](docs/translations/README.ru.md)</kbd>
<kbd>[<img title="عربى" alt="عربى" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/sa.svg" width="22">](docs/translations/README.ar.md)</kbd>
<kbd>[<img title="العربية" alt="العربية" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/sa.svg" width="22">](docs/translations/README.ar.md)</kbd>
<kbd>[<img title="Svenska" alt="Svenska" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/se.svg" width="22">](docs/translations/README.se.md)</kbd>
<kbd>[<img title="Slovenčina" alt="Slovenčina" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/sk.svg" width="22">](docs/translations/README.slk.md)</kbd>
<kbd>[<img title="Slovenščina" alt="Slovenščina" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/si.svg" width="22">](docs/translations/README.sl.md)</kbd>
@@ -74,7 +72,6 @@
<kbd>[<img title="Српски" alt="Српски" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/rs.svg" width="22">](docs/translations/README.sr.md)</kbd>
<kbd>[<img title="Қазақша" alt="Қазақша" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/kz.svg" width="22">](docs/translations/README.kz.md)</kbd>
<kbd>[<img title="Bosanski" alt="Bosanski" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/ba.svg" width="22">](docs/translations/README.bih.md)</kbd>
<kbd>[<img title="Bosanski" alt="Bosanski" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/et.svg" width="22">](docs/translations/README.bih.md)</kbd>
<kbd>[<img title="Hrvatski" alt="Hrvatski" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/hr.svg" width="22">](docs/translations/README.hr.md)</kbd>
<kbd>[<img title="پښتو" alt="پښتو" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/af.svg" width="22">](docs/translations/README.ps.md)</kbd>
<kbd>[<img title="Af-soomaali" alt="Somalia" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/so.svg" width="22">](docs/translations/README.so.md)</kbd>
@@ -87,6 +84,7 @@
<kbd>[<img title="Malagasy" alt="Malagasy" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/mg.svg" width="22">](docs/translations/README.mg.md)</kbd>
<kbd>[<img title="ភាសាខ្មែរ" alt="ភាសាខ្មែរ" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/kh.svg" width="22">](docs/translations/README.kh.md)</kbd>
<kbd>[<img title="Morocco" alt="Moroccan Darija" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/ma.svg" width="22">](docs/translations/README.ma.md)</kbd>
<kbd>[<img title="Mongolian" alt="Mongolian" src="https://cdn.statically.io/flags/mn.svg" width="22">](docs/translations/README.mn.md)</kbd>
# First Contributions
@@ -107,7 +105,7 @@ This will create a copy of this repository in your account.
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="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, then on SSH tab and then click the _copy to clipboard_ icon.
Now clone the forked repository to your machine. Go to your GitHub account, open the forked repository, click on the code button, then on SSH tab and then click the _copy url to clipboard_ icon.
Open a terminal and run the following git command:
@@ -0,0 +1,164 @@
# حاجات ممكن اللي مش مبرمج يعملها
## اسمع الأول
كل حاجة في الـ Open Source بتعتمد على الناس اللي شغالة فيها.
إنت عايز تنضم لفريق، وده معناه إنك تفهم المجتمع شغال إزاي.
لو دخلت على مشروع وقلت "هاي، أنا شايف إن المشروع المفروض يعمل كذا" غالبًا ده مش هيكون مقبول.
ممكن مشاريع معينة تكون بتحب الأسلوب ده، لكن لو المشروع ليه فترة شغال، نسبة إن الناس تتقبل الكلام ده قليلة.
**أحسن حاجة تعملها في الأول إنك تسمع وتشوف الناس شغالة إزاي.**
1. **اشترك في Mailing List**: في مشاريع كتير، الـ mailing list هي وسيلة التواصل الرئيسية بين الناس اللي بتطور المشروع.
في المشاريع الكبيرة، هتلاقي كذا mailing list.
مثلاً، مشروع PostgreSQL عنده أكتر من 12 mailing list للمستخدمين و6 للمطورين.
ابدأ بمتابعة الـ list الأساسية للمستخدمين وواحدة من بتوع المطورين علشان تفهم اللي بيحصل.
2. **تابع Blog**: المطورين الكبار غالبًا بيكتبوا تدوينات بيشرحوا فيها اللي هيحصل في النسخ الجاية،
وبيتكلموا عن اللي اتعمل علشان نوصل للمرحلة دي.
في مواقع اسمها Planet بتجمع التدوينات والأخبار من كذا مصدر عن المشروع.
لو فيه planet زي planet.gnome.org أو planet.mysql.com، يبقى ده مكان كويس تبدأ منه.
اكتب في جوجل "planet <اسم المشروع>".
3. **ادخل على قناة IRC**: معظم مشاريع الـ Open Source عندها قنوات IRC الناس بتدخل تتكلم فيها عن المشاكل والتطوير.
ادخل على موقع المشروع وشوف اسم القناة على أي شبكة IRC.
**اشتغل على التذاكر**
الكود هو الأساس في أي مشروع مفتوح المصدر، بس ده مش معناه إن الكود هو الطريقة الوحيدة اللي ممكن تساهم بيها.
فيه حاجات تانية كتير الناس بتكسل تعملها، زي صيانة النظام أو متابعة المشاكل.
ابدأ من هنا وهتلاقي نفسك بقيت جزء من الفريق.
معظم المشاريع عندها نظام تذاكر على الموقع الرسمي.
ده بيكون وسيلة تواصل بين الناس اللي بتستخدم البرنامج والمطورين.
تنضيف التذاكر دي وتحديثها بيساعد الفريق جدًا.
ممكن تحتاج صلاحيات علشان تعدل على التذاكر، بس صدقني، أول ما تقول إنك عايز تساعد، هيدوك الصلاحيات دي على طول.
4. **حلل مشكلة (Bug)**: ساعات الناس بتبلّغ عن مشاكل بشكل مش واضح.
لو حد قال "البرنامج بيهنّج لما بعمل كذا"، خد وقتك وحاول تعرف المشكلة دي بتحصل إزاي.
هل بتتكرر؟ تقدر تكتب خطوات تثبت بيها إنها بتحصل؟ بتحصل على متصفح معين؟ ولا في نظام تشغيل معين؟
حتى لو معرفتش تحلها، إنك توضّح المشكلة أكتر بيسهّل على حد تاني ييجي يحلها.
وكل اللي تكتشفه، اكتبه في التذكرة علشان غيرك يستفيد.
5. **اقفل التذاكر القديمة**: كتير من المشاكل بتكون اتحلت، بس التذاكر لسه مفتوحة.
البحث في التذاكر القديمة وتنضيفها حاجة مهمة جدًا.
ابدأ بدور على تذاكر بقالها أكتر من سنة وشوف هل المشكلة لسه موجودة ولا اتصلحت.
راجع سجل التغييرات في الإصدارات وشوف لو فيه ذكر للمشكلة.
لو اتحلت، اكتب رقم النسخة في التذكرة واقفلها.
جرّب تعيد المشكلة في آخر نسخة من البرنامج.
لو مشتغلتش، اكتب ده في التذكرة واقفلها.
لو لسه موجودة، اكتبه برضو وسيب التذكرة مفتوحة.
## الشغل على الكود
الناس اللي عندها خبرة مختلفة في البرمجة تقدر تساعد في الكود.
مش لازم تكون مبرمج جامد علشان تساهم.
لو ناوي تعدل على الكود، اعرف الأول المشروع بيشتغل إزاي في موضوع استلام التعديلات.
كل مشروع ليه طريقة معينة، فاسأل الأول.
مثلاً، PostgreSQL بيستقبل التعديلات على شكل Patch في mailing list، والمطورين بيراجعوها كويس جدًا.
لكن في مشروع زي Parrot، ممكن تاخد صلاحيات التعديل بسهولة.
لو المشروع على GitHub، غالبًا بيستخدموا Pull Requests.
كل مشروع وليه طريقته.
لما تعدل حاجة، خليك محترم مع باقي الفريق وحافظ على تنسيق الكود زي ما هو.
ما تحاولش تفرض أسلوبك.
الكود اللي بتكتبه لازم يشبه اللي موجود، حتى لو مش عاجبك.
6. **اختبر نسخة Beta أو Release Candidate**:
المشاريع اللي بتشتغل على كذا نظام تشغيل ساعات بيكون فيها مشاكل توافق.
قبل الإصدارات، المطورين بينزلوا نسخ تجريبية علشان الناس تجربها.
لو شغّلت البرنامج على نظام تشغيل مختلف واشتغل، ده بيساعدهم يعرفوا إن النسخة كويسة.
مش لازم تعمل حاجة غير إنك تبني البرنامج وتفتحه وتجربه.
لو شغال، بلغهم.
ده بيفرق كتير جدًا مع المطورين.
7. **صلّح Bug**: ده غالبًا أول حاجة الناس بتعملها لما تبدأ تشتغل في الكود.
دور على Bug شكله بسيط، وجرب تصلحه.
اكتب ملاحظاتك جوه الكود، ولو في Test يوضح إن المشكلة اتحلت، ضيفه.
لو معرفتش تصلحها، اكتب اللي وصلتله في التذكرة.
8. **اكتب Test**:
معظم المشاريع عندها Tests، بس دايمًا فيه مكان لإضافة تانية.
استخدم أدوات بتقيس مدى التغطية، زي `gcov` أو `Devel::Cover`.
وشوف أجزاء الكود اللي مش متغطية، وضيف لها Test.
9. **اسكت تحذير من الكومبايلر**:
لما تبني برامج C، ممكن يطلعلك تحذيرات.
مش دايمًا معناها إن فيه مشكلة، بس بتشوّش.
لو شفت تحذير، شوف هل فعلاً فيه مشكلة؟
لو لأ، عدل الكود علشان تسكت التحذير.
10. **ضيف تعليق**:
لو لقيت جزء في الكود مش مفهوم، اكتبه تعليق.
أكيد في ناس غيرك هتتلخبط برضو.
ابعت تعديل فيه التعليقات دي.
## الشغل على التوثيق
المستندات دايمًا بتتاخد بشكل بسيط.
وساعات بتكون مكتوبة كأن اللي بيقراها أصلاً فاهم المشروع.
لو حسيت إن التوثيق مش واضح، قول.
اللي عنيهم جديدة بيشوفوا حاجات الناس اللي شغالة عليها مش شايفاها.
11. **اعمل مثال**:
مفيش مشروع عنده أمثلة كتير كفاية.
لو فيه API، أو مكتبة، أو برنامج GUI زي Gimp، أو حتى أداة سطر أوامر – اعمل مثال عملي بيشرح ازاي تستخدمه.
ممكن المثال يكون حاجة بسيطة من كود انت كتبته، أو حتى فيديو Screen Recording وانت بتستخدمه.
الناس بتحب تشوف التطبيق العملي أكتر من الكلام.
## اشتغل مع المجتمع
الـ Open Source مش بس كود. المجتمع هو اللي بيخلي المشاريع دي تعيش وتكبر.
فيه طرق كتير تقدر تساعد بيها في تقوية المجتمع حوالي المشروع.
12. **جاوب على سؤال**:
أحسن طريقة تساعد بيها المشروع والمجتمع هي إنك تساعد غيرك.
لما حد جديد يسأل سؤال، وحضرتك تجاوبه بدل ما تقول له "روح اقرأ الـ Manual"، كده إنت مش بس ساعدته،
إنت كمان شجّعته يكمل، ويمكن كمان يبقى عضو نشيط في المشروع بعد كده.
كلنا بدأنا من الصفر، والمشاريع محتاجة دايمًا ناس جديدة تدخل علشان تفضل عايشة.
13. **اكتب تدوينة (Blog Post)**:
لو عندك مدونة، احكي فيها عن تجربتك مع المشروع اللي بتستخدمه.
قول واجهت إيه مشاكل، وازاي حليتها.
كده بتساعد المشروع بطريقتين:
- إنك بتخلي الناس تفكر في المشروع وتسمع عنه.
- وإنك بتسيب أثر للي بعدك لو حد واجه نفس المشكلة وعمل بحث على جوجل.
(والتدوينة دي كمان ممكن تبقى وسيلة كويسة توري بيها خبرتك الحقيقة في الشغل لما تيجي تدور على شغل.)
14. **طوّر موقع المشروع**:
لو عندك خبرة في تصميم المواقع، وساعدت في تحسين الموقع أو شكله العام، ده وقتك مش بيضيع.
يمكن المشروع محتاج لوجو، أو ستايل أحسن، أو تنظيم أحسن للمحتوى.
الحاجات دي ساعات بتكون ناقصة عند المبرمجين، وساعتها أي حد عنده ذوق أو خبرة في التصميم بيفرق جامد.
أنا عن نفسي بتمنى ألاقي حد يساعدني في التصميم في مشاريعي!
15. **اكتب توثيق تقني (Documentation)**:
لو تقدر تشرح ازاي برنامج أو أداة شغالة، يبقى تقدر تكتب توثيق تقني عنها.
مشاريع Open Source كتير بتبقى محتاجة توثيق جديد، أو تطوير اللي موجود، أو تبسيطه للناس.
كل ما كانت كتابتك أبسط وأوضح، كل ما كانت أحسن.
وأجمل حاجة؟ مش لازم تكون مبرمج علشان تكتب Documentation.
والأهم من كل ده، اسمع الناس بتتكلم عن إيه.
حاول تلاحظ المشاكل اللي محتاجة حل.
مثلاً، في مرة على Mailing List لمشروع Parrot، قرروا ينقلوا من Trac لـ GitHub في نظام التذاكر.
ناس كتير كانوا ضد القرار علشان مفيش طريقة ينقلوا التذاكر القديمة.
دخلت وقلت "طب ما أكتب أنا برنامج يحوّل التذاكر؟" والناس فرحت جدًا.
فعلاً كتبت برنامج نقل أكتر من 450 تذكرة، واحتفظنا بتاريخهم.
نجاح جميل، وساعدت الفريق، والمطورين ركزوا في شغلهم بدل وجع الدماغ.
16. **علّم وساعد غيرك**:
أحسن طريقة تتعلم بيها أكتر، إنك تشرح اللي فهمته لحد تاني.
المدرّس الشاطر هو اللي يقدر يشرح حاجة معقدة بطريقة بسيطة.
لو علمت حد، أو ساعدته، مش بس هتحس إنك عملت حاجة كويسة،
ده كمان هيثبت المعلومة في دماغك، ويقوّي مهاراتك.
ولما حد يساعدك، ما تحتفظش بالمعلومة لنفسك.
شارك اللي عرفته، وخلّي الدنيا مكان أحسن.
والسلام عليكم ورحمة الله وبركاته.
@@ -101,7 +101,7 @@ Menjawab pertanyaan, terutama dari seseorang yang baru saja memulai, sangat pent
Waktu yang Anda luangkan untuk membantu seorang pemula, bahkan jika mereka mengajukan pertanyaan di mana Anda dapat dengan mudah menjawab “RTFM” dengan cepat, akan terbayar di kemudian hari dengan mendapatkan anggota aktif lainnya di dalam komunitas.
Semua orang memulai dari suatu tempat, dan proyek membutuhkan arus masuk orang yang konstan jika ingin tetap hidup.
13. **Tulislah sebuah postingan blog:
13. **Tulislah sebuah postingan blog**:
Jika Anda memiliki sebuah blog, tulislah tentang pengalaman Anda dengan proyek yang Anda gunakan.
Ceritakan tentang masalah yang Anda hadapi dengan menggunakan perangkat lunak dan apa yang Anda lakukan untuk menyelesaikannya.
Anda akan membantu dengan dua cara, yaitu dengan membantu menjaga proyek tetap berada di benak orang lain di sekitar Anda,
@@ -0,0 +1,81 @@
## 오픈소스 프로젝트는 프로그래머만 기여할 수 있는 것이 아닙니다. 코딩 실력이 없어도 오픈소스 프로젝트에 참여하고 기여할 수 있는 다양한 방법들이 있습니다.
## 경청하기
오픈소스의 모든 것은 다른 사람들과의 상호작용을 포함합니다. 여러분은 팀에 합류하려는 것이므로, 커뮤니티와 그 작동 방식을 이해하는 것이 중요합니다. 프로젝트에 불쑥 끼어들어 "안녕하세요, 이 프로젝트는 이렇게 해야 한다고 생각합니다"라고 말하는 것은 일반적으로 좋게 받아들여지지 않습니다. 그런 접근 방식을 환영하는 프로젝트도 있겠지만, 프로젝트가 오랫동안 진행되어 온 경우 그러한 태도가 받아들여질 가능성은 적습니다.
**경청하는 것이 프로젝트에 필요한 것을 아는 가장 좋은 방법입니다.**
1. **메일링 리스트 가입하기**: 많은 프로젝트에서 메일링 리스트는 프로젝트 개발에 대한 주요 커뮤니케이션 수단입니다. 대규모 프로젝트에는 선택할 수 있는 메일링 리스트가 많습니다. 예를 들어, PostgreSQL 프로젝트는 메일링 리스트 페이지에 사용자 중심 리스트 12개 이상과 개발자 리스트 6개를 보유하고 있습니다. 시작하려면 주요 사용자 중심 리스트와 핵심 개발자 리스트를 팔로우하여 경청하는 것을 추천합니다.
2. **블로그 팔로우하기**: 핵심 개발자들이 운영하는 블로그는 종종 향후 릴리스에 대한 정보와 그 과정에 대한 정보를 제공합니다. 플래닛 사이트는 프로젝트와 관련된 여러 출처의 뉴스 및 블로그 게시물을 모아 보여줍니다. planet.gnome.org나 planet.mysql.com과 같은 플래닛 사이트가 있다면 거기서부터 시작하세요. Google에서 "planet <프로젝트 이름>"으로 검색해보세요.
3. **IRC 채널 가입하기**: 많은 오픈소스 프로젝트에는 개발자와 사용자가 문제 및 개발에 대해 논의하는 전용 IRC(Internet Relay Chat) 채널이 있습니다. 프로젝트 웹사이트에서 채널 이름과 IRC 네트워크 세부 정보를 확인하세요.
## 티켓 작업하기
코드는 모든 오픈소스 프로젝트의 핵심이지만, 코드를 작성하는 것만이 기여하는 유일한 방법이라고 생각하지 마세요. 코드 유지 보수 및 코드를 둘러싼 시스템은 새로운 기능을 만들고 버그를 수정하는 데 급급하여 종종 소홀히 다루어집니다. 이러한 영역을 프로젝트에 발을 들여놓을 수 있는 쉬운 방법으로 살펴보세요. 대부분의 프로젝트에는 프로젝트 웹사이트 첫 페이지에 링크되어 있고 문서에 포함된 공개적으로 볼 수 있는 문제 티켓 시스템이 있습니다. 이는 사용자와 개발자 간의 주요 커뮤니케이션 수단입니다. 이를 최신 상태로 유지하는 것은 프로젝트를 돕는 좋은 방법입니다. 티켓 시스템에서 특별한 권한을 얻어야 할 수도 있는데, 대부분의 프로젝트 리더는 티켓 정리를 돕고 싶다고 말하면 기꺼이 권한을 부여할 것입니다.
4. **버그 진단하기**: 버그는 종종 제대로 보고되지 않습니다.
버그를 진단하고 분류하는 것은 개발자가 문제의 세부 사항을 파악하는 데 드는 수고를 덜어줄 수 있습니다. 사용자가 "X를 하면 소프트웨어가 작동하지 않습니다"라고 보고했다면, 그 문제의 구체적인 내용이 무엇인지 파악하는 데 시간을 투자하세요. 반복 가능한가요? 문제를 반복적으로 발생시킬 수 있는 일련의 단계를 만들 수 있나요? 특정 브라우저에서만 발생하거나 특정 배포판에서만 발생하는 등 문제를 좁힐 수 있나요?
문제의 원인을 모르더라도, 상황을 좁히기 위해 기울인 노력은 다른 사람이 문제를 해결하는 것을 더 쉽게 만듭니다. 발견한 모든 것을 모든 사람이 볼 수 있도록 버그 시스템의 티켓에 추가하세요.
5. **수정된 버그 닫기**: 종종 버그는 코드베이스에서 수정되지만, 이에 대해 보고된 티켓은 티켓 시스템에서 업데이트되지 않습니다. 이러한 불필요한 것들을 정리하는 것은 시간이 많이 걸릴 수 있지만, 전체 프로젝트에 매우 중요합니다.
먼저 1년 이상 된 티켓을 티켓 시스템에서 쿼리하여 버그가 여전히 존재하는지 확인하세요. 프로젝트의 릴리스 변경 로그를 확인하여 버그가 수정되었고 닫을 수 있는지 확인하세요. 수정된 것으로 알려져 있다면 티켓에 버전 번호를 기록하고 닫으세요.
소프트웨어의 최신 버전으로 버그를 재현해보세요. 최신 버전으로 재현할 수 없다면 티켓에 기록하고 닫으세요. 여전히 존재한다면 티켓에 기록하고 열어 두세요.
## 코드 작업하기
모든 경험 수준의 프로그래머가 프로젝트의 코드를 도울 수 있습니다. 좋아하는 프로젝트에 실질적인 기여를 하기 위해 코딩 천재가 되어야 한다고 생각하지 마세요.
작업에 코드 수정이 포함된다면, 프로젝트가 기여자로부터 코드를 받는 데 사용하는 방법을 조사하세요. 각 프로젝트마다 고유한 워크플로우가 있으므로, 코드를 제출하기 전에 어떻게 해야 하는지 물어보세요.
예를 들어, PostgreSQL 프로젝트는 매우 엄격한 프로세스를 따릅니다. 코드 수정은 핵심 개발자들이 변경 사항의 모든 측면을 면밀히 조사하는 메일링 리스트에 패치 형태로 전송됩니다. 반대편에는 Parrot과 같이 코드베이스에 커밋 권한을 쉽게 얻을 수 있는 프로젝트도 있습니다. 프로젝트가 GitHub를 사용하는 경우, GitHub의 풀 리퀘스트 기능을 사용하는 워크플로우가 있을 수 있습니다. 어떤 프로젝트도 똑같지 않습니다.
코드를 수정할 때마다 커뮤니티의 책임 있는 구성원으로서 행동하고 코드 스타일을 나머지 코드베이스와 일치시키도록 하세요. 추가하거나 수정하는 코드는 다른 코드와 같아야 합니다. 중괄호 스타일이나 들여쓰기를 위한 공백 처리가 마음에 들지 않을 수도 있지만, 기존 표준과 일치하지 않는 코드 변경을 제출하는 것은 무례한 행동입니다. 이는 "당신의 스타일이 마음에 들지 않고 내 스타일이 더 낫다고 생각하므로 내 방식대로 해야 합니다"라고 말하는 것과 같습니다.
6. **베타 또는 릴리스 후보 테스트하기**: 여러 플랫폼에서 실행되도록 설계된 모든 프로젝트는 온갖 종류의 이식성 문제를 겪을 수 있습니다. 릴리스가 다가오고 베타 또는 릴리스 후보가 게시되면 프로젝트 리더는 많은 다른 사람들이 많은 다른 플랫폼에서 테스트하기를 바랍니다. 여러분은 그 사람들 중 한 명이 되어 패키지가 자신의 플랫폼에서 작동하는지 확인하는 데 도움을 줄 수 있습니다.
일반적으로 소프트웨어를 다운로드, 빌드 및 테스트하기만 하면 되지만, 흔하지 않은 배포판이나 하드웨어를 사용하고 있다면 프로젝트에 엄청난 가치를 제공할 수 있습니다. 빌드 및 테스트가 작동한다고 보고하는 것만으로도 프로젝트 리더는 임박한 릴리스가 견고하다는 것을 알 수 있습니다.
7. **버그 수정하기**: 이것은 일반적으로 코드 작업을 시작하려는 기여자들의 시작점입니다. 간단합니다. 티켓 시스템에서 흥미롭게 들리는 버그를 찾아 코드에서 수정하려고 시도하세요. 적절하다면 코드에 수정 사항을 문서화하세요. 수정한 코드 부분을 테스트하기 위해 테스트 스위트에 테스트를 추가하는 것이 좋습니다. 일부 프로젝트에서는 버그 수정에 테스트를 포함하도록 요구합니다. 이 익숙하지 않은 코드베이스를 살펴보면서 메모를 계속 작성하세요. 버그를 수정할 수 없더라도 수정 시도의 일환으로 발견한 내용을 티켓에 문서화하세요. 여러분이 발견한 내용은 다음에 오는 사람들에게 도움이 됩니다.
8. **테스트 작성하기**: 대부분의 프로젝트에는 코드를 테스트하는 테스트 스위트가 있지만, 더 많은 테스트를 추가할 수 없는 테스트 스위트는 상상하기 어렵습니다. C 언어용 gcov 또는 Perl용 Devel::Cover와 같은 테스트 커버리지 도구를 사용하여 테스트 스위트에서 테스트되지 않는 소스 코드 영역을 식별하세요. 그런 다음, 테스트를 스위트에 추가하여 해당 영역을 커버하세요.
9. **컴파일러 경고 잠재우기**: 많은 C 기반 프로젝트의 빌드 프로세스는 종종 이상한 컴파일러 경고 플래그를 화면에 뿜어냅니다. 이러한 경고는 일반적으로 문제의 지표는 아니지만 그렇게 보일 수 있습니다. 너무 많은 경고는 컴파일러가 거짓 경고를 하는 것처럼 들리게 할 수 있습니다. 코드가 실제로 버그를 숨기고 있는지 확인하세요. 그렇지 않다면, 소스를 수정하여 잠재우는 것은 이러한 오탐을 숨기는 데 도움이 됩니다.
10. **주석 추가하기**: 코드를 살펴보는 동안 혼란스러운 부분이 있을 수 있습니다. 여러분이 혼란스러웠다면 다른 사람들도 마찬가지일 가능성이 높습니다. 코드에 문서화하고 패치를 제출하세요.
## 문서 작업하기
문서는 일반적으로 프로젝트에서 소홀히 다루어지는 부분입니다. 또한 프로젝트에 익숙한 사람들의 관점에서 작성되어, 막 시작하는 사람의 관점이 아닌 경우도 있습니다. "이 매뉴얼은 내가 이미 이 패키지를 사용하는 방법을 알고 있다고 기대하는 것 같아"라고 생각한 적이 있다면 제가 무슨 말을 하는지 아실 겁니다. 종종 새로운 시선은 프로젝트와 가까운 사람들이 알아차리지 못하는 문서의 결함을 지적할 수 있습니다.
11. **예시 만들기**: 예시가 너무 많은 프로젝트는 없습니다. 웹 API든, 루틴 라이브러리든, Gimp와 같은 GUI 앱이든, 명령줄 도구든, 올바른 사용법에 대한 좋은 예시는 수백 페이지의 문서보다 더 명확하고 빠르게 소프트웨어의 올바른 사용법을 설명할 수 있습니다. API나 라이브러리의 경우, 도구를 사용하는 예시 프로그램을 만드세요. 이는 여러분이 작성한 코드에서 최소한의 필수적인 부분만 추출하여 만들 수도 있습니다. 도구의 경우, 일상생활에서 어떻게 사용했는지에 대한 실제 사례를 보여주세요. 시각적인 것을 선호한다면, 애플리케이션 설치 방법과 같은 중요한 프로세스의 화면 캡처를 만드는 것을 고려해 보세요.
## 커뮤니티와 함께 작업하기
오픈소스는 코드에 관한 것만이 아닙니다. 커뮤니티가 오픈소스가 작동하도록 만듭니다. 커뮤니티를 구축하는 데 도움을 줄 수 있는 방법은 다음과 같습니다.
12. **질문에 답하기**: 커뮤니티를 구축하는 가장 좋은 방법은 다른 사람들을 돕는 것입니다. 특히 막 시작하는 사람들의 질문에 답하는 것은 프로젝트가 성장하고 번성하는 데 매우 중요합니다. 초보자를 돕는 데 시간을 투자하는 것은, 비록 "RTFM(매뉴얼을 읽으세요)"이라고 간단히 대답할 수 있는 질문일지라도, 나중에 또 다른 활발한 커뮤니티 구성원을 얻는 데 도움이 됩니다. 모든 사람은 어디서든 시작하며, 프로젝트는 활력을 유지하려면 꾸준한 인력 유입이 필요합니다.
13. **블로그 게시물 작성하기**: 블로그가 있다면, 사용하고 있는 프로젝트에 대한 경험에 대해 글을 써보세요. 소프트웨어를 사용하면서 직면했던 문제와 그것을 해결하기 위해 무엇을 했는지 이야기해 주세요. 이렇게 하면 두 가지 방식으로 도움이 됩니다. 하나는 프로젝트를 주변 사람들의 마음에 계속 각인시키는 데 도움이 되고, 다른 하나는 미래에 여러분과 같은 문제를 겪고 웹에서 해결책을 검색하는 모든 사람을 위한 기록을 만드는 데 도움이 됩니다. (기술적인 모험에 대한 블로그는 나중에 해당 소프트웨어를 사용하는 직업을 찾을 때 실제 경험을 보여주는 훌륭한 방법이기도 합니다.)
14. **웹사이트 개선하기**: 웹 디자인 기술이 있고 웹사이트를 개선하여 프로젝트의 대중적인 이미지를 향상시킬 수 있다면, 이는 잘 보낸 시간입니다. 아마도 프로젝트는 그래픽 전면 개편이나 프로젝트를 식별할 로고가 필요할 수도 있습니다. 이러한 기술은 커뮤니티에 부족할 수 있습니다. 저도 제 프로젝트 웹사이트에 그래픽 디자인 지원을 받을 수 있다면 좋을 것 같습니다.
15. **기술 문서 작성하기**: 애플리케이션이나 소프트웨어가 어떻게 작동하는지 설명할 수 있다면, 그것에 대한 기술 문서를 작성할 수 있습니다. 특히 일반 대중이 읽을 수 있도록 기술 문서를 업데이트, 개편, 확장 또는 만들고자 하는 오픈소스 프로젝트라면 더욱 그렇습니다. 일반 영어로 더 많이 쓸수록 좋습니다. 가장 좋은 점은 기술 문서를 작성하기 위해 프로그래머가 될 필요가 없다는 것입니다.
무엇보다도, 주변 사람들이 논의하는 내용을 경청하세요. 절실한 필요를 알아볼 수 있는지 살펴보세요. 예를 들어, 최근 Parrot 개발자 메일링 리스트에서 기존 Trac 설치를 버리고 GitHub를 문제 티켓 시스템으로 사용하기로 결정했습니다. 일부 사람들은 티켓을 GitHub 시스템으로 변환할 방법이 없었기 때문에 이 결정에 반대했습니다. 하루 동안 논쟁이 오고 간 후, 제가 끼어들어 "제가 변환기를 작성하면 어떨까요?"라고 말했습니다. 사람들은 그 아이디어에 열광했습니다. 저는 450개 이상의 티켓에 대한 변환 프로그램을 작성하는 데 시간을 보냈고, 그래서 티켓 기록을 하나도 잃지 않았습니다. 큰 성공이었습니다. 저는 참여할 수 있었고, 핵심 개발자들은 Parrot 작업에 집중할 수 있었습니다.
16. **다른 사람들을 가르치고 돕기**: 어떤 주제에 대해 더 많이 배우는 가장 좋은 방법은 그것을 가르치려고 노력하는 것입니다. 최고의 교사는 복잡한 내용을 간단한 예시로 설명할 수 있는 사람입니다. 따라서 최고의 학습자가 되고 프로그래밍 세계에서 최고가 되려면 최고의 교사가 되기 위해 노력해야 합니다. 다른 사람들을 가르치는 것은 자신에 대해 더 나은 기분을 느끼게 하고 직업에서 더 나은 기술과 지식을 얻는 데 도움이 될 것입니다. 누군가에게 도움을 받으면 혼자 간직하지 말고 다른 사람들과 공유하세요. 세상을 더 살기 좋은 곳으로 만드세요.
@@ -122,3 +122,40 @@ Most of all, listen to what people around you discuss. See if you can recognize
16. **Teach and Help others**:
The best way to learn more about a topic is to try to teach it.
The best teacher is the one who can explain complex stuff with simple examples. So you need to try to be the best teacher to be the best learner and the best in your programming world. Teaching others will make you feel better about yourself and it will help you get better skills and knowledge in your profession. When you get help from someone don't keep it to yourself share it with others. Make the world a better place to live.
17. **Improve Accessibility**
- Audit project documentation/websites for:
- Alt text for images.
- Screen reader compatibility.
- Suggest fixes for:
- Color contrast.
- Keyboard navigation.
- Semantic HTML.
18. **Organize Community Events**
- Help organize:
- Virtual meetups or hackathons.
- "Ask Me Anything" (AMA) sessions with maintainers.
- Moderate forums/Discord/Slack to keep discussions productive.
19. **Curate Resources**
- Create an **"Awesome [Project Name]"** list with:
- Tutorials, videos, third-party tools.
- Compile a **FAQ section** from common questions in forums/issues.
20. **Social Media & Outreach**
- Manage projects Twitter/LinkedIn:
- Share updates, milestones, or contributor spotlights.
- Write **"Getting Started" threads** or tweetorials for new users.
21. **Localization & Internationalization**
- Translate UI strings (via Crowdin/Weblate).
- Adapt docs for regional contexts (e.g., date formats, idioms).
22. **Design & UX Feedback**
- Mockup UI improvements (Figma/Canva sketches).
- Report confusing workflows (e.g., "Settings menu is hard to find").
23. **Grant Writing & Fundraising**
- Apply for open-source grants (GitHub Sponsors, NLnet).
- Draft **case studies** showcasing project impact.
@@ -1,73 +1,73 @@
# .gitignore
## Understanding .gitignore
The .gitignore file is a text file that tells Git which files or folders to ignore in a project.
The `.gitignore` file is an essential component of Git's workflow. It tells Git which files and folders to ignore, preventing unnecessary or sensitive data from being tracked in your repository.
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 Use .gitignore?
## 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.
Certain files should not be included in version control because they are either:
- Temporary or system-generated (e.g., cache, build files, logs)
- Large dependencies that can be reinstalled (e.g., `node_modules`)
- Personal or sensitive configuration files (e.g., API keys, environment variables)
- IDE or editor-specific files (e.g., `.vscode/`, `.idea/`)
## 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.
Ignoring these files keeps the repository clean, reduces conflicts, and prevents security risks.
The entries in this file can also follow a matching pattern.
## Creating a .gitignore File
```
* 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
To create a `.gitignore` file:
1. In your project root directory, create a new text file named `.gitignore`.
2. List the files and folders you want to ignore, one per line.
3. Save the file.
This is an example of what the .gitignore file could look like:
### Basic Syntax for .gitignore
- `*` → Wildcard for matching multiple files.
- `/` → Specifies path relative to `.gitignore`.
- `#` → Adds comments.
### Example .gitignore File:
```sh
# Ignore Mac system files
.DS_store
.DS_Store
# Ignore node_modules folder
node_modules
# Ignore dependency folders
node_modules/
venv/
# Ignore log and cache files
*.log
.cache/
# Ignore environment files
.env
# 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:
```
## Global .gitignore (For All Projects)
To create a global `.gitignore` file (applies to all repositories):
```sh
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.
Then, edit `~/.gitignore_global` as you would a local `.gitignore`.
## How to Untrack Files Previously Committed from New Gitignore
## Removing Files from Git Tracking
To untrack a single file, ie stop tracking the file but not delete it from the system use:
If a file was already committed before adding it to `.gitignore`, you need to remove it from tracking:
- **Untrack a single file** (but keep it locally):
```sh
git rm --cached filename
```
- **Untrack all ignored files**:
```sh
git rm -r --cached .
git add .
git commit -m "Updated .gitignore"
```
To undo `git rm --cached filename`, use:
```sh
git add filename
```
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```
@@ -1,53 +1,75 @@
# WHY USING BRANCHES DURING CONTRIBUTING
## Why Use Branches When Contributing?
Git branches are an essential tool for collaboration in software development. They allow multiple developers to work on different features or bug fixes simultaneously without interfering with the main project code. By using branches, you can experiment freely, test new ideas, and merge only the best changes into the main project.
## What are branches.
## What Are Branches?
A **branch** in Git is essentially a separate line of development. It allows you to create an isolated version of the project where you can make changes without affecting the main codebase. When you're ready, you can merge your branch back into the main project.
Branches are simply pointers to a commit.
### How Branches Work
Every branch is just a pointer to a specific commit in the project history. When you create a new branch, Git duplicates the state of the current branch, allowing you to work independently. New commits are added to this branch's history without affecting the main branch.
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).
- To switch between branches, use `git checkout`.
- To combine changes from one branch into another, use `git merge`.
When you are happy with your experiments, and want to merge you experiments in main code, you run git merge
<branch name> master.
This will tell git, to add in all changes from your experiment branch into master.
## Why Use Branches?
Branches make collaboration **structured and efficient**. Without them, all changes would be made directly to the main project, leading to confusion, errors, and conflicting code.
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.
### Example: The Car Paint Job Analogy
Imagine a car manufacturing team deciding on the default color for a new car model. Initially, the car is set to be **olive green**. However, a few team members want to see how it looks in **red**.
## How it works?
- Instead of repainting the original car, they create a **prototype** with red paint.
- If the red color is approved, it replaces the original color (i.e., the branch is merged into the main project).
- If the red color is rejected, the prototype is discarded (i.e., the branch is deleted).
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.
Similarly, in Git, branches allow developers to test new features without directly modifying the main codebase.
The git branch command lets you create, list, rename, and delete branches. It doesnt 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.
## Feature Branching
Instead of having one branch per developer, it's better to create **one branch per feature**. This keeps things organized and prevents unnecessary conflicts.
## Why to use branches?
### Example: Alice & Bob's Feature Development
- **Alice** is working on **Feature A** and makes several commits.
- She then switches to **Feature C** and makes more commits.
- Meanwhile, **Bob** finishes **Feature B** and wants to start working on **Feature A**.
- Bob pulls in Alices branch, but now his branch contains **Feature A, Feature B, and some incomplete parts of Feature C**.
- When he tries to merge his branch, he faces conflicts because Feature C is unfinished.
If the question "Why do we use branching in version control like git?" still persists in your mind, here's a quick explanation:
To avoid this:
- Alice should have separate branches for **Feature A** and **Feature C**.
- Bob should have separate branches for **Feature B** and **Feature A**.
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.
This way, they can work without interfering with each other's progress.
## 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
## Creating and Managing Branches
### Create a New Branch
```sh
git branch my-new-branch
```
git branch AnyBranchName
This creates a new branch named `my-new-branch` without switching to it.
### Switch to a Branch
```sh
git checkout my-new-branch
```
This moves you to `my-new-branch`, allowing you to work on it.
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
### Create and Switch to a Branch (Shortcut)
```sh
git checkout -b my-new-branch
```
This creates and switches to the new branch in a single step.
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)
### Delete a Branch (After Merging)
```sh
git branch -d my-new-branch
```
This removes `my-new-branch` if it has already been merged.
### Force Delete a Branch (Without Merging)
```sh
git branch -D my-new-branch
```
Use this with caution! It deletes the branch even if it has unmerged changes.
## Additional Resources
- [Git Branching Guide (Atlassian)](https://www.atlassian.com/git/tutorials/using-branches)
- [Removing a Branch from Your Repository](https://github.com/jashnimje/first-contributions/blob/7dcae72208e4b42fcf834b4f189fa8ee78238077/additional-material/git_workflow_scenarios/removing-branch-from-your-repository.md)
@@ -0,0 +1,84 @@
# গিট কনফিগারেশন
প্রথমবারের মতো যখন আপনি `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` তৈরি করতে গিটকে জানতে হবে যে এর লেখক কে। সহযোগী কাজের ক্ষেত্রে, প্রকল্পের বিভিন্ন অংশের পরিবর্তন করেছেন কে এবং কবে, তা জানা খুবই গুরুত্বপূর্ণ। তাই গিটে প্রতিটি `commit`-এর সাথে ব্যবহারকারীর নাম এবং ইমেল ঠিকানা সংযুক্ত করা হয়।
এখানে কিছু উপায় আছে যার মাধ্যমে আপনি আপনার ইমেল এবং নাম `git commit` কমান্ডের সাথে যুক্ত করতে পারেন।
### গ্লোবাল কনফিগারেশন
গ্লোবাল কনফিগারেশনে সংরক্ষিত তথ্য সমস্ত গিট রিপোজিটরিতে প্রযোজ্য। এটি হল সবচেয়ে ব্যবহৃত পদ্ধতি।
গ্লোবাল কনফিগারেশনে কিছু সেট করতে, আপনি `config` কমান্ডটি এভাবে ব্যবহার করতে পারেন:
```bash
$ git config --global <variable name> <value>
```
ব্যবহারকারীর তথ্য সেট করার জন্য, এটি এভাবে হবে:
```bash
$ git config --global user.email "you@example.com"
$ git config --global user.name "Your Name"
```
### রিপোজিটরি স্তরের কনফিগারেশন
এই ধরনের কনফিগারেশন শুধুমাত্র আপনার বর্তমান রিপোজিটরিতে প্রযোজ্য। যদি আপনি কোনও নির্দিষ্ট রিপোজিটরিতে কাজ করতে চান (উদাহরণস্বরূপ, কোম্পানির প্রকল্পে), তবে এই পদ্ধতি ব্যবহার করতে পারেন।
রিপোজিটরি স্তরের কনফিগারেশন সেট করতে, `--global` বাদ দিয়ে `config` কমান্ডটি ব্যবহার করুন:
```bash
$ git config <variable name> <value>
```
ব্যবহারকারীর তথ্য সেট করার জন্য, এটি এভাবে হবে:
```bash
$ git config user.email "you@alternate.com"
$ git config user.name "Your Name"
```
### কমান্ড লাইনে কনফিগারেশন
এই ধরনের কনফিগারেশন শুধুমাত্র একটি নির্দিষ্ট কমান্ডের জন্য প্রযোজ্য। সব গিট কমান্ডে `-c` ব্যবহার করে আপনি কনফিগারেশন পরামিতি সেট করতে পারেন।
একটি কমান্ডের জন্য কনফিগারেশন পরিবর্তন করতে, গিট কমান্ডটি এভাবে ব্যবহার করুন:
```bash
$ git -c <variable-1>=<value> -c <variable-2>=<value> <command>
```
আমাদের ক্ষেত্রে, `commit` কমান্ডটি এভাবে হবে:
```bash
git -c user.name='Your Name' -c user.email='you@example.com' commit -m "Your commit message"
```
### অগ্রাধিকারের ক্রম
এই তিনটি কনফিগারেশন পদ্ধতির মধ্যে অগ্রাধিকারের ক্রম হল: `কমান্ড লাইন > রিপোজিটরি > গ্লোবাল`। এর মানে হল যদি কোনও পরিবর্তনশীল গ্লোবাল এবং কমান্ড লাইনে উভয় ক্ষেত্রেই সেট করা থাকে, তবে কমান্ড লাইনের মান ব্যবহার করা হবে।
## শুধু ব্যবহারকারীর তথ্য নয়
এখন পর্যন্ত আমরা গিট কনফিগারেশন নিয়ে আলোচনা করেছি শুধু ব্যবহারকারীর তথ্যের ক্ষেত্রে। কিন্তু গিট আরও অনেক পরামিতি কনফিগার করতে দেয়। এখানে কিছু উল্লেখযোগ্য উদাহরণ:
1. `core.editor` - কমিট মেসেজ এডিট করার জন্য ব্যবহৃত টেক্সট এডিটর,
2. `commit.template` - কমিটের জন্য প্রাথমিক টেমপ্লেট ফাইল,
3. `color.ui` - টার্মিনালে গিট মেসেজে রঙিন ফন্ট ব্যবহার করা যাবে কিনা তা নির্ধারণ করে।
আরও বিস্তারিত জানতে [git-scm.com](https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration) দেখুন।
@@ -0,0 +1,58 @@
# ওপেন সোর্স অবদানের জন্য Git অনুমতি ত্রুটি সমাধান
## সমস্যা
আমি "first-contributions" রিপোজিটরিতে অবদান রাখার চেষ্টা করার সময় একটি অনুমতি ত্রুটি পেয়েছিলাম। আমি নতুন ব্রাঞ্চ তৈরি করে এবং পরিবর্তনগুলি পুশ করার চেষ্টা করার পর:
```bash
$ git checkout -b fahimar_oss_YYYY
Switched to a new branch 'fahimar_oss_YYYY'
$ git push origin fahimar_oss_YYYY
remote: Permission to firstcontributions/first-contributions.git denied to fahimar.
fatal: unable to access 'https://github.com/firstcontributions/first-contributions.git/': The requested URL returned error: 403
```
সমস্যাটি ছিল যে, আমি মূল রিপোজিটরিটি সরাসরি ক্লোন করেছিলাম এবং সেখানে পুশ করার চেষ্টা করেছিলাম। একজন বাইরের অবদানকারী হিসেবে, আমার মূল রিপোজিটরিতে লেখার অনুমতি নেই।
## সমাধান
আমি নিম্নলিখিত উপায়ে এই সমস্যাটি সমাধান করেছি:
1. আমার রিমোট URL পরিবর্তন করে এটিকে আমার ব্যক্তিগত ফর্কে পয়েন্ট করানো:
```bash
$ git remote set-url origin https://github.com/yourname/first-contributions.git
```
2. রিমোট ঠিকভাবে আপডেট হয়েছে কিনা তা যাচাই করা:
```bash
$ git remote -v
origin https://github.com/yourname/first-contributions.git (fetch)
origin https://github.com/yourname/first-contributions.git (push)
```
3. সফলভাবে আমার ফর্কে পুশ করা:
```bash
$ git push origin fahimar_oss_YYYY
```
4. GitHub আমাকে একটি লিঙ্ক দিয়েছিল যাতে আমি আমার ব্রাঞ্চ থেকে পুল রিকোয়েস্ট তৈরি করতে পারি:
```
remote: Create a pull request for 'fahimar_oss_YYYY' on GitHub by visiting:
remote: https://github.com/fahimar/first-contributions/pull/new/fahimar_oss_YYYY
```
## প্রধান শিক্ষা
ওপেন সোর্স অবদানের জন্য সঠিক কাজের ধারাবাহিকতা হল:
1. মূল রিপোজিটরিটি আপনার GitHub অ্যাকাউন্টে ফর্ক করুন
2. আপনার ফর্কটি স্থানীয়ভাবে ক্লোন করুন
3. একটি নতুন ব্রাঞ্চে পরিবর্তন করুন
4. আপনার ফর্কে পুশ করুন
5. আপনার ফর্ক থেকে মূল রিপোজিটরিতে পুল রিকোয়েস্ট তৈরি করুন
যদি আপনি আগে মূল রিপোজিটরি ক্লোন করে থাকেন এবং আপনার ফর্ক না করে থাকেন, তবে উপরে দেখানো মতো রিমোট URL আপডেট করে এটি ঠিক করতে পারেন।
@@ -1,140 +0,0 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-old-version-tutorial/join-slack-team.png">](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
| <img alt="Git Bash" src="https://cdn.icon-icons.com/icons2/2699/PNG/512/git_scm_logo_icon_170096.png" width="200"> | 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).
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/fork.png" alt="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.
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-clone-1.png" alt="copy string" />
Open the git bash application you just downloaded. It should look like the image down below if it's on a windows machine.
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-terminal-1.png" alt="open git bash terminal" />
Go to the folder that you want to save this project on by using this command
```bash
cd <folder>
```
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-terminal-2.png" alt="cd into a folder" />
Use the string you copied in the step above to clone the repository using this command
```bash
git clone <repo-url>
```
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-clone-2.png" alt="clone the repository" />
Go to the directory where the repo is and open it up on vs code to make your changes.
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-terminal-3.png" alt="cd into the newly cloned repo" />
## Create a branch
Now create a branch by using this simple command. This command not only creates a branch for you but also lets you switch to that branch.
```bash
git checkout -b <branch-name>
```
Name your branch `<add-your-name>`. For example, "add-james-smith"
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-branch.png" alt="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
```bash
git status
```
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-status.png" alt="check the status" />
Now commit those changes:
First add the change you made to the staging area by using
```bash
git add file-name
```
Then write a commit message by sing this command
```bash
git commit -m "Add your-name to Contributors list"
```
Replace `<your-name>` with your name.
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-commit.png" alt="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
```bash
git push origin <branch-name>
```
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-push.png" alt="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.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/compare-and-pull.png" alt="create a pull request" />
Now submit the pull request.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/submit-pull-request.png" alt="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)
@@ -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/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/join-slack-team.png">](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
| <img alt="GitHub Desktop" src="https://cdn.icon-icons.com/icons2/2157/PNG/512/github_git_hub_logo_icon_132878.png" width="200"> | GitHub Command Line Interface (CLI) |
| ------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- |
To jest przewodnik dla nas, geeków terminala, którzy chcą robić wszystko w terminalu. Dzięki [Github-CLI](https://cli.github.com/), możemy to osiągnąć, pamiętając, że Twoja pierwsza kontrybucja powinna być przyjemna, satysfakcjonująca i motywować do dalszego działania\!
Ten przewodnik jest nieco trudniejszy, ponieważ w ogóle nie używamy żadnego interfejsu graficznego, ale nadal jest naprawdę fajny i na pewno możesz za nim podążać\!
Pierwszymi wymaganiami jest posiadanie:
- zainstalowanego Git (jak zainstalować [git](https://git-scm.com/downloads))
- konta Github
Teraz musimy zainstalować narzędzie `github-cli` w naszym systemie, postępując zgodnie z [oficjalną dokumentacją](https://github.com/cli/cli#installation).
Następnie musimy zalogować się w CLI, więc wprowadź to polecenie:
```bash
gh auth login
```
Postępuj zgodnie z instrukcjami i gotowe\!
-----
# Fork this repository
To jest tak proste, jak uruchomienie tego polecenia:
```bash
gh repo fork firstcontributions/first-contributions
```
**Ważne: Zostaniesz zapytany, czy chcesz również sklonować, wybierz opcję "yes".**
-----
# Create your branch
Ten krok wykonamy za pomocą git, więc wprowadź to polecenie, zastępując `name` swoim imieniem, na przykład:
```bash
git switch -c add-john-doe
```
-----
# Make necessary changes and commit those changes
Teraz możesz otworzyć plik `Contributors.md` w edytorze tekstu i dodać do niego swoje imię. Wstaw swoje imię w dowolnym miejscu między początkiem a końcem, a następnie zapisz plik.
W katalogu projektu wykonaj `git status`, a zobaczysz zmiany.
\<img align="right" width="450" src="[https://firstcontributions.github.io/assets/Readme/git-status.png](https://firstcontributions.github.io/assets/Readme/git-status.png)" alt="git status" /\>
Dodaj te zmiany do właśnie utworzonej gałęzi za pomocą polecenia `git add`:
`git add Contributors.md`
Teraz zatwierdź te zmiany za pomocą polecenia `git commit`:
`git commit -m "Add your-name to Contributors list"`
zastępując `your-name` swoim imieniem.
-----
# Push changes to github
Wypchnij swoje zmiany za pomocą polecenia `git push`:
```
git push origin -u your-branch-name
```
zastępując `your-branch-name` nazwą gałęzi, którą utworzyłeś wcześniej.
\<details\>
\<summary\> \<strong\>Jeśli podczas wypychania wystąpią błędy, kliknij tutaj:\</strong\> \</summary\>
- ### Authentication Error
     \<pre\>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/](https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/) for more information.
  fatal: Authentication failed for '[https://github.com/](https://github.com/)\<your-username\>/first-contributions.git/'\</pre\>
  Przejdź do [tutoriala GitHub](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account) dotyczącego generowania i konfigurowania klucza SSH na swoim koncie.
\</details\>
-----
# Submit your changes for review
Teraz, uruchamiając to polecenie w katalogu naszego repozytorium, możemy utworzyć pull request do przeglądu:
```bash
gh pr create --repo firstcontributions/first-contributions
```
Następnie wyślij pull request.
Możesz użyć polecenia `gh status`, aby zobaczyć swój pull request w akcji.
-----
## Where to go from here?
Gratulacje\! Właśnie ukończyłeś standardowy cykl pracy *fork -\> clone -\> edit -\> pull request*, który często napotkasz jako kontrybutor\!
Uczcij swój wkład i podziel się nim ze znajomymi i obserwującymi, przechodząc do [web app](https://firstcontributions.github.io/#social-share).
Możesz dołączyć do naszego zespołu na Slacku, jeśli potrzebujesz pomocy lub masz pytania. [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-vchl8cde-S0KstI_jyCcGEEj7rSTQiA).
Teraz zacznijmy kontrybuować do innych projektów. Zebraliśmy listę projektów z prostymi problemami, od których możesz zacząć. Sprawdź [the list of projects in the web app](https://firstcontributions.github.io/#project-list).
### [Additional material](https://www.google.com/search?q=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)
@@ -0,0 +1,116 @@
[![ઓપન સોર્સ પ્રેમ](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM)
[![લાઇસન્સ: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![ઓપન સોર્સ હેલ્પર્સ](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# પ્રથમ ફાળો
| <img alt="GitHub Desktop" src="https://cdn.icon-icons.com/icons2/2157/PNG/512/github_git_hub_logo_icon_132878.png" width="200"> | GitHub કમાન્ડ લાઇન ઈન્ટરફેસ (CLI) |
| ------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- |
આ અમારાં માટે માર્ગદર્શિકા છે, ટર્મિનલના શોખીનો માટે, જે બધું જ ટર્મિનલમાં કરવા ઈચ્છે છે, અને [GitHub-CLI](https://cli.github.com/) ની મદદથી, અમે આ હાંસલ કરી શકીએ છીએ! તમારું પ્રથમ યોગદાન મજાનું, સન્માનજનક અને પ્રેરણાદાયક હોવું જોઈએ.
આ માર્ગદર્શિકા થોડી વધુ પડકારજનક છે કારણ કે અમે કોઈપણ ગ્રાફિકલ ઈન્ટરફેસનો ઉપયોગ કરી રહ્યા નથી, પણ આ હજી પણ મજેદાર છે અને તમે ચોક્કસપણે તેને અનુસરવામાં સક્ષમ છો!
## જરૂરીતા
- Git ઇન્સ્ટોલ કરેલું હોવું જોઈએ ([Git કેવી રીતે ઇન્સ્ટોલ કરવું](https://git-scm.com/downloads))
- GitHub ખાતું હોવું જોઈએ
હવે અમારે આપણા સિસ્ટમમાં `github-cli` ટૂલ ઇન્સ્ટોલ કરવું પડશે. આ માટે [અધિકૃત દસ્તાવેજો](https://github.com/cli/cli#installation) અનુસરો.
તેના પછી, CLI માં લોગિન કરવા માટે નીચેનો આદેશ આપો:
```bash
gh auth login
```
સૂચનાઓ અનુસરો અને તમે તૈયાર છો!
# આ રીપોઝિટરી ફોર્ક કરો
આ માત્ર એક આદેશ ચલાવવાથી શક્ય છે:
```bash
gh repo fork firstcontributions/first-contributions
```
**મહત્વપૂર્ણ: તે તમને પૂછશે કે શું તમે તેને ક્લોન કરવું માંગો છો, "હા" પસંદ કરો.**
# તમારી શાખા બનાવો
આ પગલું અમે Git ની મદદથી કરીશું, માટે આ આદેશ ચલાવો (તમારું નામ બદલો, ઉદાહરણ તરીકે):
```bash
git switch -c add-john-doe
```
# જરૂરી ફેરફારો કરો અને તેમને કમિટ કરો
હવે `Contributors.md` ફાઇલને કોઈપણ ટેક્સ્ટ એડિટરમાં ખોલીને તમારું નામ ઉમેરો. પછી ફાઇલ સાચવો.
પ્રોજેક્ટ ડિરેક્ટરીમાં `git status` ચલાવો અને ફેરફારો જુઓ.
<img align="right" width="450" src="https://firstcontributions.github.io/assets/Readme/git-status.png" alt="git status" />
આ ફેરફારોને નીચેના આદેશથી ઉમેરી દો:
```bash
git add Contributors.md
```
હવે તમારાં ફેરફારોને કમિટ કરો:
```bash
git commit -m "Add your-name to Contributors list"
```
`your-name` ને તમારા નામથી બદલો.
# ફેરફારો GitHub પર અપલોડ કરો
```bash
git push origin -u your-branch-name
```
`your-branch-name` ને તમે અગાઉ બનાવેલી શાખાના નામથી બદલો.
<details>
<summary> <strong>જો પુશ કરતી વખતે ભૂલ આવે તો અહીં ક્લિક કરો:</strong> </summary>
- ### ઓથન્ટિકેશન ભૂલ
<pre>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/<your-username>/first-contributions.git/'</pre>
તમારા GitHub એકાઉન્ટમાં SSH કી કેવી રીતે ઉમેરવી તે જાણવા માટે [GitHub ની ટ્યુટોરિયલ](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account) જુઓ.
</details>
# તમારા ફેરફારોની સમીક્ષા માટે રજુ કરો
હવે નીચેનો આદેશ આપવાથી પુલ રિકવેસ્ટ બનાવી શકશો:
```bash
gh pr create --repo firstcontributions/first-contributions
```
પછી પુલ રિકવેસ્ટ સબમિટ કરો.
તમે `gh status` આદેશ વડે તમારી પુલ રિકવેસ્ટ ચકાસી શકો છો.
## હવે પછી શું?
અભિનંદન! તમે ફોર્ક -> ક્લોન -> એડિટ -> પુલ રિકવેસ્ટ ના સ્ટાન્ડર્ડ વર્કફ્લો પૂરું કર્યું છે.
તમારા યોગદાનની ઉજવણી કરો અને મિત્રો સાથે શેર કરો [વેબ એપ](https://firstcontributions.github.io/#social-share) પર જઈને.
જો તમને કોઈ પ્રશ્ન હોય અથવા મદદ જોઈતી હોય, તો તમે અમારી Slack ટીમમાં જોડાઈ શકો છો. [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)
## અન્ય સાધનો સાથે ટ્યુટોરિયલ્સ
[મુખ્ય પૃષ્ઠ પર પાછા જાઓ](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
@@ -0,0 +1,96 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![ലൈസൻസ്: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Open Source Contributors](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# ആദ്യ സംഭാവനകൾ
\| <img alt="Git Bash" src="https://cdn.icon-icons.com/icons2/2699/PNG/512/git_scm_logo_icon_170096.png" width="200"> | Git Bash പതിപ്പ് |
\| ------------------------------------------------- ------------------------------------------------- ------------- | ---------------- |
ആദ്യമായി എന്തെങ്കിലും ചെയ്യുമ്പോൾ എല്ലായ്പ്പോഴും അത് കഠിനമായി തോന്നും. പ്രത്യേകിച്ച് സഹകരിച്ച് പ്രവർത്തിക്കുമ്പോൾ തെറ്റുകൾ ചെയ്യുന്നത് ആരും ഇഷ്ടപ്പെടില്ല. പക്ഷേ **ഓപ്പൺ സോഴ്‌സ്** സഹകരണവും കൂട്ടായ പ്രവർത്തനവുമാണ്. പുതിയ സംഭാവനക്കാർക്ക് അവരുടെ **ആദ്യ സംഭാവന** നൽകുന്നത് എളുപ്പമാക്കാൻ ഞങ്ങൾ ആഗ്രഹിക്കുന്നു.
ലേഖനങ്ങൾ വായിക്കുകയോ ട്യൂട്ടോറിയലുകൾ കാണുകയോ ചെയ്യുന്നത് സഹായകരമാണ്, പക്ഷേ നേരിട്ട് ചെയ്യുന്നതിന് പകരമൊന്നുമില്ല.
ഈ പ്രോജക്റ്റ് പുതിയവർക്ക് അവരുടെ ആദ്യ സംഭാവന നൽകുന്നത് ലളിതമാക്കുകയാണ് ലക്ഷ്യം.
ഒരുപക്ഷേ നിങ്ങൾക്ക് ശാന്തമായിരുന്നാൽ നിങ്ങൾ കൂടുതൽ മികച്ച രീതിയിൽ പഠിക്കും.
നിങ്ങൾ നിങ്ങളുടെ ആദ്യ സംഭാവന നൽകാൻ ആഗ്രഹിക്കുന്നുവെങ്കിൽ, താഴെ കാണുന്ന ലളിതമായ ഘട്ടങ്ങൾ പിന്തുടരുക.
നിങ്ങളുടെ **Windows കമ്പ്യൂട്ടറിൽ Git Bash ഇല്ലെങ്കിൽ**, [ഇവിടെ നിന്ന് ഇൻസ്റ്റാൾ ചെയ്യുക](https://git-scm.com/download/win).
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/fork.png" alt="ഈ റീപോസിറ്ററി Fork ചെയ്യുക" />
## ഈ റീപോസിറ്ററി Fork ചെയ്യുക
ഈ പേജിന്റെ മുകളിലെ വലത് വശത്ത് കാണുന്ന **Fork** ബട്ടൺ അമർത്തി ഈ റീപോയെ Fork ചെയ്യുക.
ഇത് നിങ്ങളുടെ GitHub അക്കൗണ്ടിൽ ഒരു പകർപ്പ് സൃഷ്ടിക്കും.
## റീപോസിറ്ററി Clone ചെയ്യുക
ഇപ്പോൾ നിങ്ങളുടെ **Fork ചെയ്ത റീപോ** നിങ്ങളുടെ കമ്പ്യൂട്ടറിലേക്ക് Clone ചെയ്യുക.
പ്രധാനമാണ്: **ഒറിജിനൽ റീപോ** Clone ചെയ്യരുത്. നിങ്ങളുടെ Fork ചെയ്‌തത് മാത്രം Clone ചെയ്യുക.
Clone ചെയ്യാൻ “Code” അമർത്തി, താഴെ കാണുന്ന URL copy ചെയ്യുക.
```bash
git clone <repo-url>
```
പിന്നീട് നിങ്ങൾ Clone ചെയ്ത റീപോ തുറക്കാൻ git bash (അല്ലെങ്കിൽ VS Code) ഉപയോഗിക്കുക.
## ഒരു ബ്രാഞ്ച് സൃഷ്ടിക്കുക
ഒരു പുതിയ ബ്രാഞ്ച് സൃഷ്ടിക്കാൻ:
```bash
git checkout -b <branch-name>
```
ഉദാഹരണം: `add-your-name`
## ആവശ്യമായ മാറ്റങ്ങൾ വരുത്തുക
ഇപ്പോൾ `Contributors.md` ഫയൽ തുറന്ന്, ഏറ്റവും അവസാനം നിങ്ങളുടെ പേര് ചേർത്ത് **save** ചെയ്യുക.
ഉദാഹരണം:
```
[ജിതിൻ പി](https://github.com/jithin-dotcom)
```
ഫയൽ മാറ്റം വന്നിട്ടുണ്ടോ എന്ന് പരിശോധിക്കാൻ:
```bash
git status
```
## മാറ്റങ്ങൾ Commit ചെയ്യുക
```bash
git add Contributors.md
git commit -m "നിങ്ങളുടെ പേര് Contributors പട്ടികയിൽ ചേർത്തു"
```
Commit വിജയമായോ എന്ന് അറിയാൻ:
```bash
git log --oneline
```
## മാറ്റങ്ങൾ GitHub-ലേക്ക് Push ചെയ്യുക
```bash
git push origin <branch-name>
```
ഇതിന് ശേഷം, GitHub-ൽ നിങ്ങളുടെ Fork തുറക്കുമ്പോൾ **Compare & pull request** ബട്ടൺ കാണും.
അത് അമർത്തി **Pull Request** തുറക്കുക. 🎉
---
വേണോ ഞാൻ മുഴുവൻ ഗൈഡും (പിന്നിലെ pull request ഭാഗം വരെ) മലയാളത്തിലേക്ക് convert ചെയ്ത് തരട്ടേ?
@@ -0,0 +1,137 @@
[![Amor por el Código Abierto](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-old-version-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![Licencia: MIT](https://img.shields.io/badge/Άδεια-MIT-green.svg)](https://opensource.org/licenses/MIT)
[![Contribuyentes de Código Abierto](https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg)](https://www.codetriage.com/roshanjossey/first-contributions)
# Primeras Contribuciones
| <img alt="Git Bash" src="https://cdn.icon-icons.com/icons2/2699/PNG/512/git_scm_logo_icon_170096.png" width="200"> | Versión de Git Bash |
| ------------------------------------------------------------------------------------------------------------------ | --------------------- |
Es difícil. Siempre es difícil la primera vez que haces algo. Especialmente cuando colaboras, cometer errores puede ser incómodo. Pero el código abierto trata precisamente de colaboración y trabajo en conjunto. Queríamos simplificar el proceso mediante el cual nuevos colaboradores aprenden y hacen su primera contribución.
Leer artículos y ver tutoriales en video puede ayudar, pero no hay nada como aprender haciendo sin temor a equivocarte. Este proyecto busca proporcionar una guía clara y sencilla para que principiantes hagan su primera contribución. Recuerda, cuanto más relajado estés, mejor aprenderás. Si estás buscando hacer tu primera contribución, simplemente sigue estos pasos. Te prometemos que será divertido.
Si aún no tienes Git Bash en tu computadora con Windows, [descárgalo aquí](https://git-scm.com/download/win).
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/fork.png" alt="haz un fork de este repositorio" />
## Haz un fork de este repositorio
Haz clic en el botón "Fork" en la esquina superior derecha de esta página para crear una copia de este repositorio en tu cuenta.
## Clona tu repositorio
Ahora clona ese repositorio en tu computadora.
⚠️ IMPORTANTE: NO clones el repositorio original.
Ve a tu fork y clónalo.
Para hacerlo, haz clic en "Code" y copia el enlace.
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-clone-1.png" alt="copiar enlace" />
Abre la aplicación Git Bash que acabas de instalar. Debería lucir como la siguiente imagen si estás en Windows:
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-terminal-1.png" alt="abrir terminal de git bash" />
Ve a la carpeta donde quieres guardar este proyecto usando el comando:
`cd <carpeta>`
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-terminal-2.png" alt="entrar a la carpeta deseada" />
Usa el enlace copiado anteriormente para clonar tu repositorio:
`git clone <url-del-repositorio>`
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-clone-2.png" alt="clonar repositorio" />
Ve al directorio recién clonado y ábrelo en Visual Studio Code para hacer tus cambios.
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-terminal-3.png" alt="entrar al repo clonado" />
## Crear una rama
Ahora crea una nueva rama usando este comando:
```
git checkout -b <nombre-de-tu-rama>
```
Ejemplo: `add-james-smith`
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-branch.png" alt="crear rama" />
## Realiza los cambios necesarios
Abre el archivo `Contributors.md` en tu editor, ve al final del archivo y agrega tu nombre.
Ejemplo:
```md
[James Smith](https://github.com/jamessmith)
```
Para verificar los cambios:
```bash
git status
```
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-status.png" alt="ver estado" />
Ahora haz commit de los cambios:
Primero agrega el archivo:
```bash
git add Contributors.md
```
Después crea el commit:
```bash
git commit -m "Agrego mi nombre a la lista de contribuidores"
```
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-commit.png" alt="commit de cambios" />
Para verificar el commit:
```bash
git log --oneline
```
## Sube tus cambios a GitHub
```bash
git push origin <nombre-de-tu-rama>
```
<img src="https://firstcontributions.github.io/assets/cli-tool-tutorials/git-bash-windows-tutorial/gb-push.png" alt="hacer push" />
## Envía tu Pull Request
Ve a tu repositorio en GitHub. Verás un botón que dice “Compare & pull request”. Haz clic allí.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/compare-and-pull.png" alt="crear pull request" />
Completa el formulario y envía el Pull Request.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/submit-pull-request.png" alt="enviar PR" />
Pronto tus cambios serán revisados e integrados al repositorio principal. Recibirás una notificación por correo.
## ¿Y ahora qué?
¡Felicidades! Has completado el flujo de trabajo clásico _fork → clone → editar → pull request_ que es común en el mundo del open source.
Celebra tu contribución compartiéndola con tus amigos o en redes. También puedes unirte al equipo en Slack para resolver dudas:
👉 [Únete al Slack](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
### [Material adicional](../additional-material/git_workflow_scenarios/additional-material.md)
## Guías para otras herramientas
[Volver a la página principal](https://github.com/firstcontributions/first-contributions/blob/main/translations/README.es.md#material-de-apoyo-para-otras-herramientas)
@@ -0,0 +1,126 @@
[![开源之爱](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/join-slack-team.png">](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
[![许可证: 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(第一次贡献)
| <img alt="IntelliJ IDEA" src="https://upload.wikimedia.org/wikipedia/commons/9/9c/IntelliJ_IDEA_Icon.svg" width="40"> | Intellij IDEA |
| ---------------------------------------------------------------------------------------------------------------------- | ------------- |
第一次做某事总是困难的。尤其是在协作时,犯错误并不是一件舒服的事。但开源的本质就是协作与共同进步。我们希望简化新手学习与第一次参与开源项目的过程。
阅读文章和观看教程是有帮助的,但没有什么比“亲手实践又不会搞砸项目”更好的学习方式了。这个项目的目标是为新手提供指导,并简化他们第一次做出贡献的过程。记住:越放松,学习效果越好。如果你正在寻找第一次开源贡献的机会,只需按照以下简单的步骤操作。我们保证这将是一段有趣的旅程。
如果你还没有安装 IntelliJ IDEA[点击这里安装](https://www.jetbrains.com/idea/download/#section=windows)。
**注意:** 本教程使用的是 IntelliJ IDEA(版本 2019.3.2)在 Windows 10 系统上操作。教程中后续涉及的一些快捷键在 macOS 或 Linux 上可能会有所不同。
---
## Fork 这个仓库
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/fork.png" alt="fork this repository" />
点击页面右上角的 Fork 按钮 Fork 此仓库。这将在你的 GitHub 账户中创建一个此项目的副本。
GitHub 会记录你 Fork 的仓库与原始仓库之间的关系。你可以把你的副本看作是一个工作副本。
大多数顶层 GitHub 仓库(即不是 Fork 而来的)只有一小部分核心团队成员可以直接提交更改。其他所有贡献者必须 Fork 该仓库,修改后提交 Pull Request 请求将更改合并回主仓库。一旦主仓库管理员批准这些更改,它们将被合并,而你将瞬间收获名誉与财富!稍后我们会介绍如何创建 Pull Request。
---
## 克隆你的仓库
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clone this repository" />
下一步是将你的仓库克隆到本地,这样你就可以开始修改内容了。IntelliJ IDEA 需要你的仓库 URL,因此点击仓库页面上的 "Code" 按钮,然后点击“复制”图标。
**注意:** 新手经常犯的一个错误是克隆了原始仓库而不是自己的 Fork 仓库。请确认你复制的是你自己的仓库地址。
现在打开 IntelliJ IDEA。
IntelliJ IDEA 允许你检出(Git 中的 clone)一个已有的仓库,并基于下载的内容创建新项目。
在主菜单中选择 `VCS | Get from Version Control`,或者在没有打开项目时点击欢迎界面中的 `Get from Version Control`
在打开的对话框中,粘贴你仓库的远程地址(你也可以点击 “Test” 测试连接),或从左侧选择一个 VCS 托管服务。如果你已登录某个服务,它会自动列出你可克隆的仓库。
点击 “Clone”。如果你想基于克隆的源代码创建 IntelliJ 项目,在确认对话框中点击 “Yes”。Git 根目录将自动设置为项目根目录。
如果项目包含子模块,它们也会被克隆并注册为项目根。
**重要提示:** 确保克隆的是你自己的 Fork 仓库,而不是原始仓库,否则不会生效。
---
## 创建分支
在 Git 中,分支是一种强大的机制,允许你从主开发线中分离出来,比如开发一个新功能或为发布冻结某个版本等。
在 IntelliJ IDEA 中,所有与分支相关的操作都可以在 Git 分支弹出窗口中完成。点击状态栏中的 Git 小部件,或按 `Ctrl+Shift+\`` 唤出它。
当前检出的分支名称会显示在状态栏的 Git 小部件中。
在弹出窗口中选择 `New Branch`。
在弹出对话框中输入分支名称,确保勾选 “Checkout branch” 选项,这样你会自动切换到新建分支。
新分支会从当前的 HEAD 开始。如果你想从某个旧提交创建分支,可以在 `Version Control` 工具窗口的 `Log` 选项卡(快捷键 Alt+9)中选择一个提交,然后右键选择 `New Branch`。
---
## 进行必要的修改
打开 `Contributors.md` 文件,在文件中的任意位置添加你的名字。该文件使用的是 GitHub Flavored Markdown (GFM) 语法,是 Markdown 的一种扩展格式。
你可以复制其他贡献者的格式,并修改成你的名字,以确保语法正确 —— 有时语法会比较严格。
---
## 提交并推送更改到 GitHub
在 `Version Control` 工具窗口的 `Local Changes` 选项卡中,选择你要提交的文件或整个更改列表,按下 `Ctrl+K` 或点击工具栏上的 `Commit` 按钮。
在弹出的提交对话框中,会列出你自上次提交以来的所有更改文件及新增文件。
输入有意义的提交信息。
你可以按 `Ctrl+M` 打开提交历史,从中选择最近用过的提交信息。
你也可以在推送前随时修改提交信息。
按 `Ctrl+Shift+K` 或从主菜单选择 `VCS | Git | Push`。弹出的 `Push Commits` 窗口会列出当前分支所有未推送的提交。
---
## 提交 Pull Request 请求代码审查
此时你已完成了修改,但这些更改仍然只存在于你自己的仓库中。接下来我们将向原始仓库提交合并请求。
在你的 GitHub 仓库页面上,你会看到一个 “Compare & pull request” 的按钮。点击它。
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/compare-and-pull.png" alt="创建 Pull Request" />
接下来提交你的 Pull Request。
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-desktop-tutorial/submit-pull-request.png" alt="提交 Pull Request" />
不久之后,你的更改就会被合并到主仓库的 master 分支中。一旦合并成功,你会收到邮件通知。
---
## 接下来可以做什么?
恭喜!你刚刚完成了标准的 _fork -> clone -> 编辑 -> PR_ 流程,这将是你未来开源贡献中非常常见的工作流程!
庆祝一下你的首次贡献,并通过 [web app](https://firstcontributions.github.io#social-share) 与好友分享你的成就吧!
如果你有任何问题,欢迎加入我们的 Slack 团队:[加入 Slack 团队](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)
@@ -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/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](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)
# Erste Beiträge
| <img alt="Visual Studio Code" src="https://upload.wikimedia.org/wikipedia/commons/1/1c/Visual_Studio_Code_1.35_icon.png" width="40"> | Visual Studio Code |
| ------------------------------------------------------------------------------------------------------------------------------------ | ------------------ |
Es ist schwer. Es ist immer schwer, wenn man etwas zum ersten Mal macht. Vor allem, wenn man mit anderen zusammenarbeitet, ist es nicht angenehm, Fehler zu machen. Aber bei Open Source geht es gerade um Zusammenarbeit und gemeinsames Arbeiten. Wir wollten neuen Open-Source-Mitwirkenden den Einstieg erleichtern, damit sie lernen und zum ersten Mal einen Beitrag leisten können.
Das Lesen von Artikeln und das Anschauen von Tutorials kann hilfreich sein, aber nichts ist besser, als die Dinge einfach auszuprobieren, ohne etwas zu vermasseln. Dieses Projekt zielt darauf ab, Anfängern eine Anleitung zu bieten und ihnen den Weg zu ihrem ersten Beitrag zu erleichtern. Denke daran: Je entspannter Du bist, desto besser lernst Du. Wenn Du Deinen ersten Beitrag leisten möchtest, folge einfach den folgenden einfachen Schritten. Wir versprechen Dir, es wird Spaß machen.
Wenn du Visual Studio Code nicht auf deinem Computer installiert hast, [installiere es jetzt.](https://code.visualstudio.com/download).
**Anmerkung:** Dieses Tutorial wurde mit Visual Studio Code (Version 1.27.2) auf einem Windows 10-Rechner erstellt. Später in diesem Tutorial werden wir einige Tastaturkürzel verwenden. Diese können sich je nach Betriebssystem (macOS/Linux) und Tastatursprache (UK, DE usw.) unterscheiden. Du kannst Deine Liste der Tastaturkürzel durchsuchen, indem Du in der Befehlspalette nach „shortcut” suchst.
## Dieses Repository forken
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="fork this repository" />
Forke dieses Repository, indem Du oben rechts auf dieser Seite auf die Schaltfläche „Fork“ klickst. Dadurch wird eine Kopie dieses Repositorys in Ihrem GitHub-Konto erstellt.
GitHub verfolgt die Beziehung zwischen Ihrem Repository und dem Repository, von dem Sie es geforkt haben. Sie können sich Ihr Repository als Arbeitskopie vorstellen.
Die meisten Top-Level-Repositorys auf GitHub (d. h. solche, die nicht von einem anderen Repository geforkt wurden) haben ein kleines Kernteam von Personen, welche Änderungen direkt committen können. Alle anderen Mitwirkenden müssen das Repo forken und Änderungen im Fork vornehmen, dann einen Pull Request erstellen, um zu beantragen, dass ihre Änderungen wieder in das Top-Level-Repo übernommen werden. Wenn dem Administrator des Top-Level-Repos die Änderungen gefallen, werden sie übernommen und Du wirst sofort berühmt und reich! Mehr dazu später.
## Das Repository klonen
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clone this repository" />
Der nächste Schritt besteht darin, Dein Repository auf Deinen Computer zu klonen, damit Du Änderungen vornehmen kannst. VS Code benötigt die URL Deines Repositories, also klicke auf die Schaltfläche „Code“ und dann auf das Symbol „In die Zwischenablage kopieren“.
**ACHTUNG:** Ein Fehler, den neue Mitwirkende oft machen, ist, dass sie das Repository, von dem sie geforkt haben klonen an Stelle ihres eigenen. Überprüfe die Adressleiste Deines Browsers und stelle sicher, dass Du Dein Repository klonst.
Öffne nun Visual Studio Code. Die Willkommensseite von VS Code wird angezeigt. Drücke `F1`, um die Leiste zu öffnen, die unten gezeigt wird. Beachte, dass bereits ein `>` (größer als) Zeichen im Textfeld steht. Du kannst auch über `CTRL-P` zum Eingabeaufforderung gelangen und das `>`-Zeichen eingeben.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone.png" alt="Clone Popup (Command Popup)" />
Vielleicht bemerkst Du, dass bereits einige obskure Befehle aufgelistet sind. Das sind meine zuletzt verwendeten Befehle. Also kümmere Dich nicht darum.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone1.png" alt="Clone repo" />
Nun tippe `git clone`, nur `git` oder `clone` (es funktioniert wie eine Suche).
Wähle den Eintrag `Git: Clone` aus und drücke `Enter`.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone2.png" alt="Paste Repository URL in" />
Füge die URL Deines Repositories ein und drücke `Enter`. Dadurch wird der Datei-Explorer geöffnet, in dem Du auswählen kannst, wo das Git-Repository gespeichert werden soll.
**Wichtig**: Achte darauf, dass es sich um das geforkte Repository handelt und nicht um das Original, da es sonst nicht funktioniert.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-clone3.png" alt="Status popup" />
Du solltest eine Statusmeldung in der unteren rechten Ecke von Visual Studio Code sehen. Nachdem der Vorgang abgeschlossen ist, kannst Du das geklonte Repository (jetzt ein Ordner auf Deinem Computer) mit den Schaltflächen im Dialogfeld öffnen.
## Erstelle einen Branch
Öffne die Befehls-Palette erneut, indem Du `F1` drückst. Tippe `branch` ein und wähle den Befehl `create branch` aus. Im nächsten Schritt gib den Namen Deines neuen Branches ein, zum Beispiel `add-david-kroell`. Drücke `Enter`, um den Branch zu erstellen. Der Branch ist auch bereits ausgecheckt. [Was bedeutet checkout?](https://www.git-scm.com/docs/git-checkout)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-branch.png" alt="Branches Command Palette" />
## Nötige Änderungen vornehmen
Öffne `Contributors.md` in einem Texteditor und füge Deinen Namen hinzu. Achte darauf, dass Du den Namen nicht am Anfang oder am Ende der Datei hinzufügst. Speichere die Datei anschließend.
Diese Datei enthält GFM (GitHub Flavored Markdown), eine proprietäre Variante der <a href="https://en.wikipedia.org/wiki/Markdown">Markdown-Syntax</a>.
Kopiere eine der anderen Mitwirkenden-Zeilen und passe sie mit Deinem Namen an, um sicherzustellen, dass die Syntax korrekt ist - sie kann schwierig sein. Speichere die Datei, um die Änderung zu registrieren.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-changes.png" alt="Add your name" />
## Änderungen committen und zu GitHub pushen
Auf der linken Seite von VS Code befindet sich ein Menü mit 5 Symbolen. Wähle das Versionskontroll-/Quellcodeverwaltungssymbol aus.
(Shortcut: `Ctrl + Shift + G`)
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit.png" alt="Commit changes" />
Der Datei-Explorer zeigt alle Dateien an, die seit dem letzten Commit geändert wurden. Wenn Du mit der Maus über die Dateien fährst und auf das `+` (Plus) klickst, werden die Dateien zum Staging hinzugefügt.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-commit1.png" alt="Stashed Files">
Tippe etwas in die Zeile oben im Explorer und drücke das Häkchen. Die Änderungen sind jetzt in Deiner lokalen Kopie committed. Jetzt müssen die Änderungen zurück zu GitHub gepusht werden.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-push.png" alt="Stashed Files">
Klicke auf das Drei-Punkte-Symbol, um das Menü zu öffnen, in dem Du die Option `Publish Branch` auswählst. Dadurch sollte ein Dialogfeld geöffnet werden, in dem Du Deine GitHub-Anmeldeinformationen eingeben kannst.
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs-code-tutorial/vscode-2018-08-gh-auth.png" alt="Stashed Files">
## Änderungen zur Überprüfung absenden
An diesem Punkt hast Du Deine Änderung abgeschlossen, aber sie befindet sich noch nur in Deinem Repository. Dieser Schritt zeigt Dir, wie Du eine Anfrage an den Administrator des Top-Level-Repos stellen kannst, um Deine Änderung zusammenzuführen.
In Deinem Repository auf GitHub siehst Du neben der Benachrichtigung über den neuen Branch die Schaltfläche `Compare & pull request`. Klicke auf diese Schaltfläche.
<img src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="create a pull request" />
Sende jetzt den Pull Request ab.
<img src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="submit pull request" />
Ich werde nun Deine Änderungen in den Master-Branch dieses Projekts mergen. Du erhältst eine E-Mail, sobald dies geschehen ist.
## Und jetzt?
Herzlichen Glückwunsch! Du hast gerade den Standard-Workflow _fork -> clone -> edit -> PR_ abgeschlossen, den Du als Contributor häufig antreffen wirst!
Feiere Deinen Beitrag zum Projekt und teile ihn mit Deinen Freunden und Followern über unsere [Web-App](https://firstcontributions.github.io#social-share).
Du kannst dem Slack-Team beitreten, falls Du Hilfe benötigst oder Fragen hast. [Slack-Team beitreten](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
### [Weiterführende Materialien](../additional-material/git_workflow_scenarios/additional-material.md)
## Tutorials mit anderen Tools
[Zurück zur Hauptseite](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
@@ -0,0 +1,95 @@
ٹھیک ہے 👍 آپ نے جو متن دیا ہے وہ **First Contributions** گائیڈ ہے (GitKraken ایڈیٹر کے ساتھ)۔ میں اس کو اُردو میں ترجمہ کر رہا ہوں تاکہ آسانی سے سمجھ سکیں۔
---
# پہلی شراکتیں (First Contributions)
| <img alt="GitKraken" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-icon.png" width="200"> | GitKraken ایڈیشن |
| ------------------------------------------------------------------------------------------------------------------------------------- | ---------------- |
یہ مشکل ہے۔ پہلی بار کچھ کرنے پر ہمیشہ مشکل لگتا ہے۔ خاص طور پر جب آپ تعاون (collaboration) کر رہے ہوں تو غلطیاں کرنا اچھا نہیں لگتا۔ لیکن اوپن سورس کا مقصد ہی تعاون اور ایک ساتھ کام کرنا ہے۔ ہم چاہتے تھے کہ نئے لوگ آسانی سے سیکھ سکیں اور اپنی پہلی شراکت (contribution) کر سکیں۔
آرٹیکل پڑھنا اور ویڈیوز دیکھنا مددگار ہوتا ہے، لیکن اصل مزہ تب ہے جب آپ خود کر کے سیکھیں بغیر کچھ توڑے پھوڑے۔ اس پروجیکٹ کا مقصد یہ ہے کہ نئے لوگ آسانی سے اپنی پہلی شراکت کریں۔ یاد رکھیں جتنا ریلیکس رہیں گے، اتنا بہتر سیکھیں گے۔ اگر آپ پہلی بار کانٹریبیوٹ کرنا چاہتے ہیں تو نیچے دیے گئے آسان مراحل پر عمل کریں۔ یقین کریں یہ مزےدار ہوگا۔
---
## GitKraken
[GitKraken](https://www.gitkraken.com) ڈاؤن لوڈ کریں، انسٹال کریں اور کھولیں۔
آپ کو "Welcome to GitKraken" کا ڈائیلاگ باکس نظر آئے گا۔ GitHub کے ساتھ لاگ ان کریں اور GitKraken کو اپنے GitHub اکاؤنٹ تک رسائی دیں۔
(اختیاری) File -> Preferences میں جا کر اپنے پروجیکٹ کا ڈائریکٹری سیٹ کریں تاکہ وہ آپ کے مقامی ریپوزیٹریز کے ساتھ جڑ جائے۔
---
## ریپوزیٹری کو فورک کریں
اس صفحے کے اوپر دائیں طرف موجود **Fork** بٹن پر کلک کریں۔
یہ آپ کے اکاؤنٹ میں اس ریپوزیٹری کی ایک کاپی بنا دے گا۔
---
## ریپوزیٹری کو کلون کریں
GitKraken میں جائیں: File -> Clone Repo.
GitHub.com منتخب کریں۔ اپنے یوزرنیم کے نیچے **first-contributions** ریپوزیٹری دکھائی دے گی۔ اسے منتخب کریں اور آخر میں دی گئی لوکل پاتھ چیک کر لیں۔
جب سب صحیح لگے تو "Clone the repo!" پر کلک کریں۔
---
## نئی برانچ بنائیں
ٹول بار میں *branch* بٹن پر کلک کریں۔
برانچ کا نام رکھیں: "add-your-name"
مثال: `"add-william-sutton"`
---
## تبدیلیاں کریں اور Commit کریں
`Contributors.md` فائل کو کھولیں اور اپنا نام شامل کریں۔ فائل محفوظ (save) کریں۔
اب GitKraken میں تبدیلیاں نظر آئیں گی۔ اپنی تبدیلیوں کو stage کریں اور ایک اچھا commit میسج لکھیں۔
مثال: `"Add <your-name> to Contributors list"`
پھر **commit** بٹن پر کلک کریں۔
مبارک ہو 🎉 آپ نے اپنی تبدیلیاں مقامی ریپوزیٹری میں محفوظ کر لی ہیں۔
---
## تبدیلیاں GitHub پر Push کریں
ٹول بار میں *Push* بٹن پر کلک کریں۔
اپنی برانچ کو GitHub پر بھیج دیں تاکہ آپ کی تبدیلیاں وہاں بھی نظر آئیں۔
---
## Pull Request بھیجیں
GitHub پر جائیں، آپ کو "Compare & pull request" کا بٹن نظر آئے گا۔ اس پر کلک کریں۔
اب اپنی pull request سبمٹ کریں۔
آپ کی تبدیلیاں ریویو کے بعد مین برانچ میں شامل کر دی جائیں گی۔ جب ایسا ہوگا آپ کو ای میل نوٹیفکیشن ملے گا۔
---
## اگلے مراحل
مبارک ہو! آپ نے وہ مکمل ورک فلو کر لیا جو ایک عام اوپن سورس کانٹریبیوٹر کو کرنا پڑتا ہے:
**fork → clone → edit → PR**
اپنی شراکت کا جشن منائیں 🎉 اور اسے دوستوں کے ساتھ شیئر کریں۔
اگر مزید مدد چاہیے تو آپ [Slack ٹیم](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA) میں بھی شامل ہو سکتے ہیں۔
---
کیا آپ چاہتے ہیں میں اس کا **سارانس (short version)** بھی اردو میں بنا دوں تاکہ پہلی بار اوپن سورس کنٹریبیوٹ کرنے والے کو صرف بنیادی مراحل نظر آئیں؟
@@ -0,0 +1,64 @@
# ಓಪನ್ ಸೋರ್ಸ್ ಪ್ರಾಜೆಕ್ಟ್‌ಗಳಿಗೆ ಹೇಗೆ ಕೊಡುಗೆ ನೀಡುವುದು: ಆರಂಭಿಕರಿಗಾಗಿ ಸಂಪೂರ್ಣ ಮಾರ್ಗದರ್ಶಿ
**ಸಂಕ್ಷಿಪ್ತವಾಗಿ:** ನೀವು ನಿಮ್ಮ ಮೊದಲ Pull Request ಅನ್ನು ಒಂದು ಓಪನ್‌ಸೋರ್ಸ್ ಪ್ರಾಜೆಕ್ಟ್‌ಗೆ ಸಲ್ಲಿಸಲು ಕಾತರರಾಗಿದ್ದರೆ, ಈ ಸೂಚನೆಗಳನ್ನು ಅನುಸರಿಸಿ: [Readme](https://github.com/firstcontributions/first-contributions)
ಓಪನ್‌ಸೋರ್ಸ್ ಪ್ರಾಜೆಕ್ಟ್‌ಗಳಿಗೆ ಕೊಡುಗೆ ನೀಡುವುದು ಒಬ್ಬ ಪ್ರೋಗ್ರಾಮರ್ ಆಗಿ ಬೆಳೆಯಲು, ನಿಮ್ಮ ಪೋರ್ಟ್‌ಫೋಲಿಯೋವನ್ನು ನಿರ್ಮಿಸಲು ಮತ್ತು ಸಮುದಾಯಕ್ಕೆ ಹಿಂದಿರುಗಿಸಲು ಅತ್ಯುತ್ತಮ ಮಾರ್ಗಗಳಲ್ಲಿ ಒಂದು. ನೀವು ಅನುಭವಸಂಪನ್ನ ಪ್ರೋಗ್ರಾಮರ್ ಆಗಿರಲಿ ಅಥವಾ ಪ್ರಾರಂಭದಲ್ಲೇ ಇರಲಿ, ಓಪನ್‌ಸೋರ್ಸ್ ಪ್ರಾಜೆಕ್ಟ್‌ಗಳು ಕಲಿಯಲು, ಸಹಕರಿಸಲು ಮತ್ತು ಸಕಾರಾತ್ಮಕ ಪರಿಣಾಮವನ್ನುಂಟುಮಾಡಲು ಹಲವಾರು ಅವಕಾಶಗಳನ್ನು ಒದಗಿಸುತ್ತವೆ. ಈ ಮಾರ್ಗದರ್ಶಿಯಲ್ಲಿ, ಸರಿಯಾದ ಪ್ರಾಜೆಕ್ಟ್‌ನ್ನು ಹುಡುಕುವುದರಿಂದ ಹಿಡಿದು ನಿಮ್ಮ ಮೊದಲ ಕೊಡುಗೆಯನ್ನು ನೀಡುವವರೆಗಿನ ಎಲ್ಲಾ ಹಂತಗಳನ್ನು ನೋಡೋಣ.
## ಏಕೆ ಓಪನ್‌ಸೋರ್ಸ್ ಪ್ರಾಜೆಕ್ಟ್‌ಗಳಿಗೆ ಕೊಡುಗೆ ನೀಡಬೇಕು?
"ಹೇಗೆ" ಎಂಬುದರ ಮೊದಲು, "ಏಕೆ" ಎಂಬುದನ್ನು ತಿಳಿಯೋಣ:
* **ಕೌಶಲ್ಯ ಅಭಿವೃದ್ಧಿ:** ನೈಜ ಪ್ರಾಜೆಕ್ಟ್‌ಗಳ ಕೋಡ್‌ಗಳನ್ನು ನೋಡಿ ಕಲಿಯುವ ಮೂಲಕ ನಿಮ್ಮ ಪ್ರೋಗ್ರಾಮಿಂಗ್, ಡಿಬಗ್ಗಿಂಗ್ ಮತ್ತು ಸಹಕಾರದ ಕೌಶಲ್ಯಗಳು ಬೆಳೆಯುತ್ತವೆ.
* **ಪೋರ್ಟ್‌ಫೋಲಿಯೋ ನಿರ್ಮಾಣ:** ಪ್ರಸಿದ್ಧ ಪ್ರಾಜೆಕ್ಟ್‌ಗಳಲ್ಲಿ ಕೊಡುಗೆ ನೀಡುವುದು ನಿಮ್ಮ CV ಮತ್ತು GitHub ಪ್ರೊಫೈಲ್ ಅನ್ನು ಬಲಪಡಿಸುತ್ತದೆ.
* **ನೆಟ್ವರ್ಕಿಂಗ್:** ಜಗತ್ತಿನಾದ್ಯಂತದ ಡೆವಲಪರ್‌ಗಳ ಜೊತೆ ಸಂಪರ್ಕ ಬೆಳೆಸಿ, ತಜ್ಞರಿಂದ ಕಲಿಯಿರಿ ಮತ್ತು ಸಮುದಾಯದ ಭಾಗವಾಗಿರಿ.
* **ಹಿಂದಿರುಗಿಸುವುದು:** ನಾವು ಪ್ರತಿದಿನ ಬಳಸುವ ಅನೇಕ ಸಾಫ್ಟ್‌ವೇರ್‌ಗಳ ಆಧಾರ ಓಪನ್‌ಸೋರ್ಸ್ ಆಗಿದೆ. ಕೊಡುಗೆ ನೀಡುವುದು ಧನ್ಯವಾದ ಹೇಳುವ ಮಾರ್ಗ.
* **ವೃತ್ತಿ ಅವಕಾಶಗಳು:** ಅನೇಕ ಕಂಪನಿಗಳು ಓಪನ್‌ಸೋರ್ಸ್ ಅನುಭವ ಹೊಂದಿರುವ ಡೆವಲಪರ್‌ಗಳನ್ನು ಹುಡುಕುತ್ತವೆ ಏಕೆಂದರೆ ಇದು ಪ್ರೊಆಕ್ಟಿವಿಟಿ ಮತ್ತು ತಂಡದ ಕೆಲಸವನ್ನು ತೋರಿಸುತ್ತದೆ.
## ಹೇಗೆ ಪ್ರಾರಂಭಿಸಬೇಕು?
### 1. ಸರಿಯಾದ ಪ್ರಾಜೆಕ್ಟ್ ಆಯ್ಕೆಮಾಡಿ
ನಿಮ್ಮ ಆಸಕ್ತಿಗಳು ಮತ್ತು ಕೌಶಲ್ಯಗಳಿಗೆ ಹೊಂದಿಕೊಳ್ಳುವ ಪ್ರಾಜೆಕ್ಟ್‌ಗಳನ್ನು ಆರಿಸಿ:
* **GitHub ಅನ್ವೇಷಿಸಿ:** `good-first-issue`, `help-wanted` ಮುಂತಾದ ಲೇಬಲ್‌ಗಳಿರುವ ಟಾಸ್ಕ್‌ಗಳನ್ನು ಹುಡುಕಿ.
* **ಪ್ರೋಗ್ರಾಂಗಳಲ್ಲಿ ಭಾಗವಹಿಸಿ:** Google Summer of Code, Hacktoberfest ಮುಂತಾದವು ಉತ್ತಮ ಅವಕಾಶಗಳು.
* **ನೀವು ಬಳಸುವ ಉಪಕರಣಗಳು:** ನೀವು ಬಳಸುವ ಲೈಬ್ರರಿ ಅಥವಾ ಫ್ರೇಮ್‌ವರ್ಕ್‌ಗಳಲ್ಲಿ ಕೊಡುಗೆ ನೀಡಿ.
### 2. ಪ್ರಾಜೆಕ್ಟ್‌ನ್ನು ಅರ್ಥಮಾಡಿಕೊಳ್ಳಿ
* **ಡಾಕ್ಯುಮೆಂಟೇಶನ್ ಓದಿ:** README ಮತ್ತು ಕೊಡುಗೆ ಮಾರ್ಗಸೂಚಿಗಳನ್ನು ಗಮನಿಸಿ.
* **ಕೋಡ್‌ನ್ನು ಅಧ್ಯಯನ ಮಾಡಿ:** ಪ್ರಾಜೆಕ್ಟ್‌ನ ರಚನೆ ಮತ್ತು ಕೋಡಿಂಗ್ ಶೈಲಿಯನ್ನು ತಿಳಿದುಕೊಳ್ಳಿ.
* **ಸಮುದಾಯಕ್ಕೆ ಸೇರಿ:** Slack, Discord ಅಥವಾ ಫೋರಮ್‌ಗಳಲ್ಲಿ ಚರ್ಚೆಗಳಲ್ಲಿ ಭಾಗವಹಿಸಿ.
### 3. ಚಿಕ್ಕ ಹಂತಗಳಿಂದ ಪ್ರಾರಂಭಿಸಿ
* **ಬಗ್‌ಗಳನ್ನು ಸರಿಪಡಿಸಿ:** ಆರಂಭಿಕರಿಗೆ ಅನುಕೂಲಕರವಾದ issues ಹುಡುಕಿ.
* **ಡಾಕ್ಯುಮೆಂಟೇಶನ್ ಸುಧಾರಿಸಿ:** ಬಹಳ ಉಪಯುಕ್ತವಾದರೂ ಹೆಚ್ಚಾಗಿ ಗಮನಿಸದೆ ಬಿಡಲಾಗುತ್ತದೆ.
* **ಟೆಸ್ಟ್‌ಗಳನ್ನು ಬರೆಯಿರಿ:** ಕೋಡ್ ತಿಳಿಯಲು ಉತ್ತಮ ವಿಧಾನ.
### 4. ಉತ್ತಮ ಅಭ್ಯಾಸಗಳನ್ನು ಅನುಸರಿಸಿ
* **Fork ಮತ್ತು Clone ಮಾಡಿ**
* **ಪ್ರತ್ಯೇಕ branch ನಲ್ಲಿ ಕೆಲಸ ಮಾಡಿ**
* **ಸ್ವಚ್ಛ ಕೋಡ್ ಬರೆಯಿರಿ**
* **ನಿಮ್ಮ ಬದಲಾವಣೆಗಳನ್ನು ಪರೀಕ್ಷಿಸಿ**
* **Pull Request ಕಳುಹಿಸಿ:** ಸ್ಪಷ್ಟ ವಿವರಣೆ ನೀಡಿ, ಸಂಬಂಧಿತ issue‌ಗಳನ್ನು ಉಲ್ಲೇಖಿಸಿ ಮತ್ತು feedback ಸ್ವೀಕರಿಸಲು ತೆರೆದಿರಲಿ.
## ಯಶಸ್ಸಿಗೆ ಸಲಹೆಗಳು
* **ಸಮರ್ಪಕ ಸಂವಹನ ಮಾಡಿ:** ಗೌರವಪೂರ್ವಕವಾಗಿ ವರ್ತಿಸಿ ಮತ್ತು ಸ್ಪಷ್ಟವಾಗಿ ಪ್ರಶ್ನೆ ಮಾಡಿ.
* **ಸ್ಥಿರತೆಯಿಂದಿರಿ:** ಸಣ್ಣ ಕೊಡುಗೆಗಳೂ ಸಮಯದೊಂದಿಗೆ ದೊಡ್ಡ ಪರಿಣಾಮ ಬೀರುತ್ತವೆ.
* **ಫೀಡ್ಬ್ಯಾಕ್‌ನಿಂದ ಕಲಿಯಿರಿ:** ಕೋಡ್ ರಿವ್ಯೂ ಒಳ್ಳೆಯ ಕಲಿಕೆಯ ಅವಕಾಶ.
* **ಇತರರಿಗೆ ಸಹಾಯ ಮಾಡಿ:** ನೀವು ಅನುಭವ ಹೊಂದಿದ ಮೇಲೆ ಹೊಸಬರಿಗೆ ಮಾರ್ಗದರ್ಶನ ನೀಡಿ.
## ಸಾಮಾನ್ಯ ಸವಾಲುಗಳು ಮತ್ತು ಪರಿಹಾರಗಳು
* **Impostor Syndrome:** ಚಿಕ್ಕ ಕೊಡುಗೆಗಳೂ ಮುಖ್ಯ. ಎಲ್ಲರೂ ಎಲ್ಲಿಂದೋ ಆರಂಭಿಸಿದ್ದಾರೆ.
* **ಸಮಯದ ಕೊರತೆ:** ಸಣ್ಣ ಟಾಸ್ಕ್‌ಗಳಿಂದ ಪ್ರಾರಂಭಿಸಿ. ವಾರಕ್ಕೆ 30 ನಿಮಿಷ ಕೂಡ ಸಾಕು.
* **ದೊಡ್ಡ ಕೋಡ್‌ಬೇಸ್‌ ಅನ್ನು ನಾವಿಗೇಟ್ ಮಾಡುವುದು:** ಒಂದೊಂದೇ ಘಟಕ concentrate ಮಾಡಿ, documentation ಓದಿ, ಪ್ರಶ್ನೆಗಳನ್ನು ಕೇಳಿ.
## ಸಮಾರೋಪ
ಓಪನ್‌ಸೋರ್ಸ್‌ಗೆ ಕೊಡುಗೆ ನೀಡುವುದು ವೈಯಕ್ತಿಕ ಮತ್ತು ವೃತ್ತಿಪರ ಬೆಳವಣಿಗೆಗೆ ದೊಡ್ಡ ಅವಕಾಶ. ಸಣ್ಣ ಹಂತಗಳಿಂದ ಆರಂಭಿಸಿ, ನಿಯಮಿತವಾಗಿರಿ, ಸಮುದಾಯದೊಂದಿಗೆ ಸಂವಹನ ಮಾಡಿ — ಹೀಗೆ ನಿಮ್ಮ ಕೌಶಲ್ಯಗಳನ್ನು ಬೆಳೆಸುತ್ತಾ ಪರಿಣಾಮಕಾರಿ ಕೊಡುಗೆಗಳನ್ನು ನೀಡಬಹುದು. ಪ್ರತಿಯೊಂದು ಕೊಡುಗೆಯೂ ಮಹತ್ವದ್ದೇ. ಇಂದೇ ಪ್ರಾರಂಭಿಸಿ — ನಿಮಗೆ ಇಷ್ಟವಾದ ಪ್ರಾಜೆಕ್ಟ್ ಹುಡುಕಿ, ಮೊದಲ ಕೊಡುಗೆ ನೀಡಿ ಮತ್ತು ಜಾಗತಿಕ ಓಪನ್‌ಸೋರ್ಸ್ ಚಳುವಳಿಯ ಭಾಗವಾಗಿರಿ!
@@ -0,0 +1,94 @@
# ஓபன் சோர்ஸிற்குப் பயனளிக்க எப்படி: ஒரு விரிவான வழிகாட்டி (குவிகட்டிய தொடக்கத்திற்காக)
**TL;DR** - நீங்கள் ஓபன் சோர்ஸ் திட்டத்தில் உங்கள் முதல் புல் ரிக்வஸ்டை செய்ய விரும்பினால், [Readme](https://github.com/firstcontributions/first-contributions) லுள்ள வழிமுறைகளைப் பின்பற்றுங்கள். நான் ஒரு சிறிய பிழையை திருத்தும் பங்களிப்பை என் முதல் பங்களிப்பாகச் செய்கிறேன்.
ஓபன் சோர்ஸிற்குப் பயனளிப்பது ஒரு மென்பொருள் டெவலப்பராக வளரவும், உங்கள் போர்ட்ஃபோலியோவை உருவாக்கவும், சமூகத்திற்குப் பங்களிக்கவும் சிறந்த வழிகளில் ஒன்றாகும். நீங்கள் அனுபவம் வாய்ந்த நிரலாளராக இருந்தாலும், அல்லது புதியதாக இருந்தாலும், ஓபன் சோர்ஸ் உங்களுக்கு நிறைய கற்றல், இணைப்பு, மற்றும் தாக்கம் செலுத்தும் வாய்ப்புகளை வழங்குகிறது.
இந்த வழிகாட்டியில், சரியான திட்டத்தைத் தேர்ந்தெடுப்பதிலிருந்து உங்கள் முதல் பங்களிப்பைச் செய்வது வரை, ஓபன் சோர்ஸில் பங்களிப்பதற்கான அனைத்து முக்கிய விஷயங்களையும் ஆராய்வோம்.
---
## ஏன் ஓபன் சோர்ஸில் பங்களிக்க வேண்டும்?
"எப்படி" என்பதைப் பார்க்கும் முன், "ஏன்" என்பதை ஆராய்வோம். ஓபன் சோர்ஸில் பங்களிப்பது பல நன்மைகளை வழங்குகிறது:
- **திறமைகளை மேம்படுத்துதல்** – உண்மையான புரொஜெக்ட் கோடுகளைப் பார்க்க வாய்ப்பு கிடைக்கும், எங்கேயும் சேர முடியாத அனுபவம் கிடைக்கும்.
- **போர்ட்ஃபோலியோ உருவாக்கம்** – பிரபலமான ஓபன் சோர்ஸ் திட்டங்களில் பங்களிப்பது உங்கள் ரெஸ்யூமேயை மெருகூட்டும்.
- **நெட்வொர்க்கிங்** – உலகளாவிய டெவலப்பர்களுடன் இணைவது, புதிய விஷயங்களைப் பழகுவது.
- **சமூகத்திற்குப் பங்களிக்க** – நாம் தினமும் பயன்படுத்தும் மென்பொருள்களுக்கு உதவிக்கரம் நீட்டும் வாய்ப்பு.
- **வேலை வாய்ப்புகள்** – ஓபன் சோர்ஸ் அனுபவம் கொண்டவர்களை பல நிறுவனங்கள் விரும்பி பணியமர்த்துகின்றன.
---
## ஓபன் சோர்ஸில் பங்களிக்க எப்படி தொடங்கலாம்?
### 1. சரியான திட்டத்தைத் தேர்ந்தெடுங்கள்
உங்களுக்குப் பொருத்தமான திட்டத்தை கண்டுபிடிப்பது முக்கியம். இதைப் பற்றிச் சில வழிகள்:
- **GitHub-ஐ ஆராயுங்கள்** – ["good-first-issue"](https://github.com/search?q=label%3Agood-first-issue) போன்ற தொடக்க நபர்களுக்கான குறிச்சொற்களைப் பயன்படுத்தி தேடுங்கள்.
- **ஓபன் சோர்ஸ் நிகழ்ச்சிகளைப் பின்பற்றுங்கள்** – Google Summer of Code, Hacktoberfest போன்றவை சிறந்த தொடக்க புள்ளிகள்.
- **உங்களுக்குப் பழக்கமான கருவிகளைத் தேர்வு செய்யுங்கள்** – நீங்கள் பயன்படுத்தும் புத்தகங்கள், libraries, frameworks ஆகியவற்றில் பங்களிக்கலாம்.
---
### 2. திட்டத்தைப் புரிந்துகொள்ளுங்கள்
பங்களிக்க முன்பாக, திட்டத்தை முழுமையாகப் புரிந்துகொள்ள முயற்சி செய்யுங்கள்:
- **README மற்றும் வழிமுறைகளை வாசிக்கவும்** – பங்களிப்பு வழிகாட்டி, கோட்பாடு (code of conduct) போன்றவற்றைப் பாருங்கள்.
- **கோட்பணியை ஆராயுங்கள்** – கோப்புகளின் அமைப்பு, கோடிங் ஸ்டைல் போன்றவற்றை அறிந்து கொள்ளுங்கள்.
- **சமூகத்தில் ஈடுபடுங்கள்** Forums, Slack, Discord போன்ற இடங்களில் கலந்துரையாடுங்கள்.
---
### 3. சிறிய பங்களிப்புகளுடன் தொடங்குங்கள்
முதலில் எளிதான விடயங்களில் பங்களிக்கலாம்:
- **பிழைகளை சரிசெய்யுங்கள்** "good-first-issue" அல்லது "beginner-friendly" போன்ற குறிச்சொற்களைப் பயன்படுத்தி சரிபாருங்கள்.
- **ஆவணங்களை மேம்படுத்துங்கள்** – Documentation முக்கியமான பங்களிப்பு வழியாக இருக்கலாம்.
- **Unit Testing எழுதுங்கள்** Code coverage அதிகரிக்க இது உதவும்.
---
### 4. சிறந்த நடைமுறைகளைப் பின்பற்றுங்கள்
ஒரு நிரல்பாக பங்களிக்கும்போது, திட்ட விதிமுறைகளைப் பின்பற்றுங்கள்:
- **Fork & Clone செய்யுங்கள்** – உங்கள் கணக்கில் repository-ஐ fork செய்து, அதை local க்கு clone செய்யுங்கள்.
- **Branch-ஐ உருவாக்குங்கள்** – தனியான branch-ல் வேலை செய்யுங்கள்.
- **சுத்தமான கோட்களை எழுதுங்கள்** – திட்டத்திற்கேற்ப coding style-ஐ பின்பற்றுங்கள்.
- **Test செய்யுங்கள்** – உங்கள் மாற்றங்கள் ஏதாவது பிரச்சனை ஏற்படுத்துகிறதா என்று சரிபாருங்கள்.
- **Pull Request (PR) சமர்ப்பியுங்கள்** – PR-க்கு சரியான விளக்கம், issue reference, மற்றும் தயார் இருக்கும் மனப்பான்மை ஆகியவற்றுடன் சமர்ப்பியுங்கள்.
---
## ஓபன் சோர்ஸில் வெற்றி பெற சில குறிப்புகள்
**தெளிவாக தொடர்புகொள்ளுங்கள்** – கேள்விகள் கேளுங்கள், புல்ல ரிக்வஸ்டுக்கு மறுமொழி கொடுப்பவர்களுக்கு நன்றி சொல்லுங்கள்.
**தொடர்ச்சியாக பங்களியுங்கள்** – சிறிய சிறிய பங்களிப்புகள் கூட பெரிய தாக்கத்தை ஏற்படுத்தும்.
**விமர்சனத்திலிருந்து கற்றுக்கொள்ளுங்கள்** Code review மூலம் மேம்படுங்கள்.
**மற்றவர்களுக்கு உதவுங்கள்** – புல்ல ரிக்வஸ்டுகளை மதிப்பாய்வு செய்யுங்கள், புதியவர்களை வழிநடத்துங்கள்.
---
## பொதுவான சவால்கள் & அதை சமாளிக்க வழிகள்
**Imposter Syndrome (நான் போதுமான திறமையுள்ளவரா? 🤔)**
➡️ எல்லோருக்கும் இது வரும். சிறிய பங்களிப்புகளாலும் பெரிய தாக்கத்தை ஏற்படுத்தலாம்.
**நேரம் இல்லாமை**
➡️ ஒரு வாரத்திற்கும் 30 நிமிடங்கள் செலுத்தினாலும், நீங்கள் மெல்ல வளர முடியும்.
**பெரிய கோட்பணியை புரிந்துகொள்வது கடினம்**
➡️ டாக்குமென்டேஷனை வாசியுங்கள், ஒரு பிரிவில் கவனம் செலுத்துங்கள், Debugging tool-களை பயன்படுத்துங்கள்.
---
## முடிவுரை
ஓபன் சோர்ஸில் பங்களிப்பது வளர்ச்சிக்கு மிக நல்ல வழியாகும். சிறிய செயல்களில் தொடங்குங்கள், தொடர்ந்து பங்களியுங்கள், சமூகத்தில் ஈடுபடுங்கள். ஒவ்வொரு பங்களிப்பும் ஓபன் சோர்ஸை மேம்படுத்த உதவுகிறது.
🚀 **தொடங்க தயார்?**
உங்களுக்கு பிடித்த திட்டத்தை தேடுங்கள், உங்கள் முதல் பங்களிப்பைச் செய்யுங்கள், மற்றும் உலகளாவிய ஓபன் சோர்ஸ் இயக்கத்தில் சேருங்கள்! 🎉
@@ -0,0 +1,73 @@
# ఓపెన్ సోర్స్‌కు ఎలా సహకరించాలి: ప్రారంభకులకు సమగ్ర మార్గదర్శి
TL;DR మీరు ఓపెన్ సోర్స్ ప్రాజెక్ట్‌కి మీ మొదటి పుల్ అభ్యర్థనను చేయాలనుకుంటున్నట్లయితే, [Readme](https://github.com/firstcontributions/first-contributions)లోని సూచనలను అనుసరించండి.
డెవలపర్‌గా ఎదగడానికి, మీ పోర్ట్‌ఫోలియోను రూపొందించడానికి మరియు కమ్యూనిటీకి తిరిగి ఇవ్వడానికి ఓపెన్ సోర్స్‌కు సహకారం అందించడం అనేది అత్యంత బహుమతినిచ్చే మార్గాలలో ఒకటి. మీరు అనుభవజ్ఞుడైన ప్రోగ్రామర్ అయినా లేదా ఇప్పుడే ప్రారంభించినా, ఓపెన్ సోర్స్ తెలుసుకోవడానికి, సహకరించడానికి మరియు ప్రభావం చూపడానికి అంతులేని అవకాశాలను అందిస్తుంది. ఈ గైడ్‌లో, సరైన ప్రాజెక్ట్‌ను కనుగొనడం నుండి మీ మొదటి సహకారం అందించడం వరకు ఓపెన్ సోర్స్‌కు సహకరించడం గురించి మీరు తెలుసుకోవలసిన ప్రతిదానిని మేము మీకు తెలియజేస్తాము.
## ఓపెన్ సోర్స్‌కి ఎందుకు సహకరించాలి?
"ఎలా"లోకి ప్రవేశించే ముందు, "ఎందుకు" అనేదాన్ని అన్వేషిద్దాం. ఓపెన్ సోర్స్‌కు సహకారం అందించడం వలన అనేక ప్రయోజనాలను అందిస్తుంది:
* నైపుణ్యాభివృద్ధి: ఓపెన్ సోర్స్ ప్రాజెక్ట్‌లు మిమ్మల్ని వాస్తవ ప్రపంచ కోడ్‌బేస్‌లకు బహిర్గతం చేస్తాయి, మీ కోడింగ్, డీబగ్గింగ్ మరియు సహకార నైపుణ్యాలను మెరుగుపరచడంలో మీకు సహాయపడతాయి.
* పోర్ట్‌ఫోలియో బిల్డింగ్: ప్రసిద్ధ ప్రాజెక్ట్‌లకు విరాళాలు మీ రెజ్యూమ్ మరియు GitHub ప్రొఫైల్‌ను మెరుగుపరుస్తాయి, తద్వారా మీరు సంభావ్య యజమానులకు ప్రత్యేకంగా నిలుస్తారు.
* నెట్‌వర్కింగ్: మీరు ప్రపంచవ్యాప్తంగా ఉన్న డెవలపర్‌లతో కనెక్ట్ అవుతారు, నిపుణుల నుండి నేర్చుకుంటారు మరియు గ్లోబల్ కమ్యూనిటీలో భాగం అవుతారు.
* గివింగ్ బ్యాక్: ఓపెన్ సోర్స్ మనం రోజూ ఉపయోగించే చాలా సాఫ్ట్‌వేర్‌లకు శక్తినిస్తుంది. మీరు ఆధారపడే సాధనాలు మరియు సాంకేతికతలకు మద్దతు ఇవ్వడానికి సహకారం అందించడం ఒక మార్గం.
* కెరీర్ అవకాశాలు: చాలా కంపెనీలు ఓపెన్ సోర్స్ అనుభవంతో డెవలపర్‌లను చురుకుగా కోరుకుంటాయి, ఎందుకంటే ఇది చొరవ మరియు జట్టుకృషిని ప్రదర్శిస్తుంది.
## ఓపెన్ సోర్స్ కంట్రిబ్యూషన్‌లతో ఎలా ప్రారంభించాలి
### 1. సరైన ప్రాజెక్ట్‌ను ఎంచుకోండి
సరైన ప్రాజెక్ట్‌ను కనుగొనడం చాలా ముఖ్యం. మీ ఆసక్తులు, నైపుణ్యం స్థాయి మరియు లక్ష్యాలకు అనుగుణంగా ఉండే ప్రాజెక్ట్‌ల కోసం చూడండి. వాటిని ఎలా కనుగొనాలో ఇక్కడ ఉంది:
* GitHubని అన్వేషించండి: GitHub యొక్క అన్వేషణ పేజీని ఉపయోగించండి లేదా "గుడ్-ఫస్ట్-ఇష్యూ" లేదా "హెల్ప్-వాంటెడ్" వంటి అంశాల కోసం శోధించండి.
* ఓపెన్ సోర్స్ ప్రోగ్రామ్‌లను తనిఖీ చేయండి: గూగుల్ సమ్మర్ ఆఫ్ కోడ్ లేదా హ్యాక్‌టోబర్‌ఫెస్ట్ వంటి ప్రోగ్రామ్‌లు ప్రారంభకులకు గొప్పవి.
* మీ సాధనాలను అనుసరించండి: మీరు ఇప్పటికే ఉపయోగిస్తున్న లైబ్రరీలు, ఫ్రేమ్‌వర్క్‌లు లేదా సాధనాలకు సహకరించండి.
### 2. ప్రాజెక్ట్‌ను అర్థం చేసుకోండి
సహకరించే ముందు, ప్రాజెక్ట్‌ను అర్థం చేసుకోవడానికి సమయాన్ని వెచ్చించండి:
* డాక్యుమెంటేషన్‌ను చదవండి: README ఫైల్, సహకార మార్గదర్శకాలు మరియు ప్రవర్తనా నియమావళితో ప్రారంభించండి.
* కోడ్‌బేస్‌ను అన్వేషించండి: ప్రాజెక్ట్ నిర్మాణం మరియు కోడింగ్ శైలితో మిమ్మల్ని మీరు పరిచయం చేసుకోండి.
* సంఘంలో చేరండి: కమ్యూనిటీ కోసం ఒక అనుభూతిని పొందడానికి ఫోరమ్‌లు, స్లాక్ లేదా డిస్కార్డ్‌పై చర్చల్లో పాల్గొనండి.
### 3. చిన్నగా ప్రారంభించండి
విశ్వాసాన్ని పెంపొందించడానికి చిన్న, నిర్వహించదగిన పనులతో ప్రారంభించండి:
* బగ్‌లను పరిష్కరించండి: "మంచి-మొదటి సమస్య" లేదా "బిగినర్స్-ఫ్రెండ్లీ" అని లేబుల్ చేయబడిన సమస్యల కోసం చూడండి.
* డాక్యుమెంటేషన్‌ను మెరుగుపరచండి: డాక్యుమెంటేషన్ అప్‌డేట్‌లు తరచుగా విస్మరించబడతాయి కానీ చాలా విలువైనవి.
* పరీక్షలు రాయండి: పరీక్షలను జోడించడం అనేది కోడ్‌బేస్ గురించి తెలుసుకోవడానికి మరియు సహకరించడానికి ఒక గొప్ప మార్గం.
### 4. ఉత్తమ పద్ధతులను అనుసరించండి
సహకరించేటప్పుడు, ప్రాజెక్ట్ మార్గదర్శకాలకు కట్టుబడి ఉండండి:
* ఫోర్క్ మరియు క్లోన్: రిపోజిటరీని ఫోర్క్ చేసి మీ స్థానిక మెషీన్‌కు క్లోన్ చేయండి.
* ఒక శాఖను సృష్టించండి: మీ మార్పుల కోసం ప్రత్యేక శాఖలో పని చేయండి.
* క్లీన్ కోడ్ వ్రాయండి: ప్రాజెక్ట్ యొక్క కోడింగ్ ప్రమాణాలను అనుసరించండి మరియు స్పష్టమైన, సంక్షిప్త కోడ్‌ను వ్రాయండి.
* మీ మార్పులను పరీక్షించండి: మీ మార్పులు ఇప్పటికే ఉన్న కార్యాచరణను విచ్ఛిన్నం చేయలేదని నిర్ధారించుకోండి.
* ఒక పుల్ అభ్యర్థన (PR) సమర్పించండి: స్పష్టమైన PR వివరణ, సూచన సంబంధిత సమస్యలను వ్రాయండి మరియు అభిప్రాయానికి సిద్ధంగా ఉండండి.
## ఓపెన్ సోర్స్‌లో విజయం కోసం చిట్కాలు
ప్రభావవంతంగా కమ్యూనికేట్ చేయండి: అన్ని పరస్పర చర్యలలో గౌరవప్రదంగా మరియు వృత్తిపరంగా ఉండండి. అవసరాల గురించి అస్పష్టంగా ఉన్నప్పుడు ప్రశ్నలు అడగండి. సమీక్షకులకు వారి సమయం మరియు అభిప్రాయానికి ధన్యవాదాలు. సమీక్ష ప్రక్రియలో ఓపికగా ఉండండి
స్థిరంగా ఉండండి: రెగ్యులర్ కంట్రిబ్యూషన్‌లు, చిన్నవి కూడా, కాలక్రమేణా పెద్ద ప్రభావాన్ని చూపుతాయి.
అభిప్రాయం నుండి నేర్చుకోండి: కోడ్ సమీక్షలు నేర్చుకునే అవకాశం. అభిప్రాయాన్ని స్వీకరించండి మరియు మీ నైపుణ్యాలను మెరుగుపరచండి.
తిరిగి ఇవ్వండి: మీరు సౌకర్యవంతంగా ఉన్న తర్వాత, PRలను సమీక్షించడం, ప్రశ్నలకు సమాధానం ఇవ్వడం లేదా కొత్తవారికి మార్గదర్శకత్వం చేయడం ద్వారా ఇతరులకు సహాయం చేయండి.
## సాధారణ సవాళ్లు మరియు వాటిని ఎలా అధిగమించాలి
* ఇంపోస్టర్ సిండ్రోమ్: చాలా మంది ప్రారంభకులు తమకు సహకరించడానికి తగినంత నైపుణ్యం లేదని భావిస్తారు. గుర్తుంచుకోండి, ప్రతి ఒక్కరూ ఎక్కడో ఒకచోట ప్రారంభించబడతారు మరియు చిన్న విరాళాలు కూడా ముఖ్యమైనవి.
* సమయాన్ని కనుగొనడం: చిన్న, నిర్వహించదగిన పనులతో ప్రారంభించండి. వారానికి 30 నిమిషాలు కూడా తేడా రావచ్చు.
* పెద్ద కోడ్‌బేస్‌లను నావిగేట్ చేయడం: అభ్యాస ప్రక్రియను విచ్ఛిన్నం చేయండి: - డాక్యుమెంటేషన్‌ను పూర్తిగా చదవడం ద్వారా ప్రారంభించండి - ఒక సమయంలో ఒక భాగాన్ని అర్థం చేసుకోవడంపై దృష్టి పెట్టండి - కోడ్ అమలును ట్రేస్ చేయడానికి డీబగ్గింగ్ సాధనాలను ఉపయోగించండి - స్పష్టత కోసం అడగడానికి వెనుకాడకండి
## తీర్మానం
ఓపెన్ సోర్స్‌కు సహకరించడం అనేది అపారమైన వ్యక్తిగత మరియు వృత్తిపరమైన వృద్ధిని అందించే ప్రయాణం. చిన్నగా ప్రారంభించడం ద్వారా, స్థిరంగా ఉండటం మరియు సంఘంతో సన్నిహితంగా ఉండటం ద్వారా, మీరు మీ నైపుణ్యాలను మెరుగుపరుచుకుంటూ అర్ధవంతమైన సహకారాన్ని అందించవచ్చు. గుర్తుంచుకోండి, ఓపెన్ సోర్స్ సహకారంతో అభివృద్ధి చెందుతుంది మరియు ప్రతి సహకారం-ఎంత చిన్నదైనా-మెరుగైన డిజిటల్ ప్రపంచాన్ని నిర్మించడంలో సహాయపడుతుంది. మునిగిపోవడానికి సిద్ధంగా ఉన్నారా? మిమ్మల్ని ఉత్తేజపరిచే ప్రాజెక్ట్‌ను కనుగొనండి, మీ మొదటి సహకారాన్ని అందించండి మరియు ఈరోజే గ్లోబల్ ఓపెన్ సోర్స్ ఉద్యమంలో చేరండి!
## చివరి సమాధా
@@ -70,3 +70,4 @@ Give Back: Once youre comfortable, help others by reviewing PRs, answering qu
Contributing to open source is a journey that offers immense personal and professional growth. By starting small, staying consistent, and engaging with the community, you can make meaningful contributions while honing your skills. Remember, open source thrives on collaboration, and every contribution—no matter how small—helps build a better digital world. Ready to take the plunge? Find a project that excites you, make your first contribution, and join the global open source movement today!
Open source is more than just code — its about people, collaboration, and continuous learning. By taking small, consistent steps and engaging with the community, youll not only grow as a developer but also make meaningful contributions to projects used by millions.
@@ -0,0 +1,71 @@
# Cum sa contribuiti la proiectele Open Source: Un ghid detaliat pentru incepatori
Pe scurt: Daca sunteti nerabdator/nerabdatoare sa creati primul Pull Request pe un proiect Open Source, folositi instructiunile de aici: [Readme](https://github.com/firstcontributions/first-contributions)
Contributiile la proiectele Open Source reprezinta una dintre cele mai bune metode de a te dezvolta ca programator/programatoare, a-ti dezvolta portofoliul si a da ceva inapoi comunitatii. Fie ca esti un programator senior sau doar ai inceput, proiectele Open Source ofera foarte multe oportunitati de a invata, colabora si a avea un impact pozitiv. In acest ghid, vom trece prin tot ceea ce trebuie sa stiti pentru a contribui la proiectele Open Source, de la a gasi proiectul protrivit si pana la a realiza prima contributie.
## De ce sa contribuiti la proiectele Open Source?
Inainte sa vorbim despre "cum", sa exploram "de ce". Contribuirea la proiectele Open Source ofera numeroase beneficii:
* Dezvoltarea abilitatilor: Proiectele Open Source va expun la cod sursa din proiecte reale, ajutandu-va la imbunatatirea abilitatilor dvs. de programare, depanare si colaborare.
* Construirea unui Portofoliu: Contributiile la proiectele bine cunoscute va pot imbogati CV-ul si profilul dvs. de pe Github, ajutandu-va sa iesiti in evidenta in fata potentialilor angajatori.
* Networking (Colaborarea, socializarea cu scop profesional): Va veti conecta cu dezvoltatori din intreaga lume, veti invata de la experti si veti face parte la randul dvs. din aceasta comunitate globala.
* Sa dai inapoi (ca multumire): Proiectele Open Source stau la baza multor aplicatii/programe software pe care le folosim zilnic. Contributiile sunt un mod de a sustine uneltele si tehnologiile pe care va bazati/de care depindeti.
* Oportunitati de cariera: Multe companii cauta in mod activ programatori cu experienta pe proiecte Open Source deoarece astfel se demonstreaza initiativa, proactivitatea si lucrul in echipa.
## Cum sa incepeti sa contribuiti pe proiectele Open Source
### 1. Alegeti Proiectul potrivit
Identificarea proiectului potrivit este cruciala. Cautati proiecte care se aliniaza intereselor, nivelurilor abilitatilor si telurilor dvs.. Le puteti gasi intr-unul din modurile urmatoare:
* Explorati Github: Folositi pagina Github Explore sau cautati topicurile precum "necesita-ajutor", "ajutor-cerut", "good-first-issue", "help-wanted" etc.
* Cautati programe dedicate Open Source: Programe ca Google Summer of Code, Hacktoberfest si altele sunt bune pentru incepatori.
* Urmariti proiectele dedicate uneltelor/programelor tale (favorite): Contribuie la librarii, frameworks, unelte sau programe pe care deja le folositi.
### 2. Intelegeti proiectul
Inainte sa contribuiti, este indicat sa dedicati timp pentru a intelege proiectul:
* Cititi documentatia: Incepeti cu fisierul README, cele mai bune practici, reguli si indicatii pentru contributii si regulamentul de conduita.
* Exploreaza codul sursa: Familiarizati-va cu structura proiectului si stilul de programare (indentari, conventii de nume, etc.).
* Alaturati-va comunitatii: Participati la discutiile de pe forumuri, Slack sau Discord pentru a va acomoda mai usor in comunitate.
### 3. Incepeti cu pasi mici
Incepeti cu pasi mici, sarcini de lucru pe care le puteti dezvolta, care va vor ajuta sa deveniti mai increzator/increzatoare, precum:
* Repararea defectelor: Cauta "issues" ((cerinte de) sarcini de lucru) pe pagina dedicata, care au etichete precum "sarcina-buna-de-inceput", "pentru-incepatori", "incepatori", "good-first-issue", "beginner-friendly" etc.
* Imbunatatiti documentatia: Actualizarile documentatiei sunt adesea trecute cu vederea, insa aduc multa plus-valoare.
* Scrieti teste: Adaugarea de teste (teste unitare, teste de integrare, etc.) este un mod foarte bun de a contribui si a invata mai bine codul sursa.
### 4. Folositi cele mai bune practici
Cand contribuiti, este bine sa respectati indicatiile pentru cele mai bune practici:
* Bifurca si Cloneaza: Bifurcati (fork) si clonati codul sursa (depozitul) pe masina dvs. locala.
* Creati o ramura: Lucrati pe o ramura separata pentru a face modificarile dvs..
* Scrieti cod curat: Urmariti standardele de a scrie cod sursa si scrieti cod clar, curat, citibil, concis.
* Testati modificarile: Asigurati-va ca modificarile dvs. nu vor afecta functionalitatea existenta.
* Creati un Pull Request (cerere de unificare cod sursa intre doua ramuri): Faceti o cerere de unificare a versiunii dvs. de cod sursa cu cel existent pe alta ramura (de obicei cea principala), unde trebuie sa aveti o descriere clara a PR-ului, referentiati alte sarcini de lucru corelate si fiti deschisi la feedback.
## Sfaturi pentru a avea succes in proiectele Open Source
Comunicati eficient si eficace: Fiti respectuosi si comportati-va in mod profesional in toate interactiunile. Puneti intrebari cand nu sunteti siguri de cerinte. Aveti rabdare in timpul procesului de evaluare/revizuire.
Fiti consistenti: Contributiile regulate, chiar si cele mici, pot avea un impact mare in timp.
Invatati din feedback: Evaluarile de cod sursa sunt un prilej de invatare. Acceptati rezultatele acestor evaluari si va veti imbunatati abilitatile.
Dati inapoi (ceva comunitatii): Odata ce sunteti comfortabil(a) cu procesul de PR, ajutati-i si pe altii in acest proces, raspundeti-le la intrebari sau chiar fiti mentor pentru incepatori.
## Provocari comune si cum sa le depasiti
* Sindromul Impostorului: Multi incepatori simt ca nu au destule abilitati pentru a contribui. Retineti ca toti au inceput de undeva si ca pana si contributiile mici conteaza.
* Gasirea timpului necesari: Incepeti cu sarcini de lucru mici, pe care le puteti face. Pana si 30 de minute pe saptamana pot face o diferenta.
* Navigarea unui depozit mare de cod sursa: Impartiti procesul de invatare: Incepeti prin a citi in detaliu documentatia - Concentrati-va pe intelegerea unei singure componente la un moment dat - Folositi toate uneltele pentru depanare de care dispuneti - Nu ezitati sa puneti intrebari pentru clarificari
## Concluzie
Contributia la proiectele Open Source este o calatorie/aventura/un proces care va ofera imense posibilitati de dezvoltare personala si profesionala. Incepand cu pasi mici, ramanand consistenti si interactionand cu comunitatea, puteti face contributii de impact in timp ce va imbunatatiti abilitatile. Tineti minte ca proiectele Open Source se dezvolta prin colaborare si ca fiecare contributie - indiferent de cat de mica ar fi - ajuta la imbunatatirea mediului digital. Sunteti gata sa incepeti? Gasiti un proiect care va atrage, realizati prima contributie si alaturati-va miscarii globale Open Source astazi!
+1 -1
View File
@@ -114,7 +114,7 @@ Urime! Ti sapo ke kompletuar procesin _fork -> clone -> edit -> PR_ që do ta ha
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).
Nëse dëshiron më shumë praktikë, shiko [kontributet e kodit](https://github.com/roshanjossey/code-contributions)
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).
+3 -1
View File
@@ -118,11 +118,13 @@ git push -u origin your-branch-name
## Որտեղ գնալ այստեղից?
Շնորհավորում եմ Դուք հենց նոր ավարտեցիք ստանդարտ _fork -> clone -> edit -> pull request_ աշխատանքային հոսքը, որը հաճախ կհանդիպեք որպես ներդրող!
Նշեք ձեր ներդրումը և կիսվեք այն ձեր ընկերների և հետևորդների հետ՝ գնալով [վեբ հավելված](https://firstcontributions.github.io/#social-share).
Եթե ցանկանում եք ավելի շատ փորձել, ստուգեք [կոդի ներդրումները](https://github.com/roshanjossey/code-contributions).
Եթե ցանկանում եք ավելի շատ փորձ ձեռք բերել, տեսեք [ծածկագրի ներդրումները](https://github.com/roshanjossey/code-contributions)։
Հիմա եկեք սկսենք ձեր ներդրումն ունենալ այլ նախագծերում: Մենք կազմել ենք հեշտ խնդիրներ ունեցող նախագծերի ցանկ, որոնցից կարող եք սկսել: Ստուգեք [վեբ հավելվածի նախագծերի ցանկը](https://firstcontributions.github.io/#project-list).
+2 -1
View File
@@ -144,10 +144,11 @@ Pull Request জমা দিয়ক
আপোনাৰ অৱদান উদযাপন কৰক আৰু আপোনাৰ বন্ধু আৰু অনুসাৰকসকলৰ সৈতে ইয়াক শেয়াৰ কৰক [web app](https://firstcontributions.github.io/#social-share).
আপুনি আমাৰ Slack দলত যোগদান কৰিব পাৰে যদি আপোনাৰ সহায়ৰ প্ৰয়োজন হয় বা কোনো প্ৰশ্ন থাকে। [Join slack team](https://join.slack.com/t/firstcontributors/shared_invite/zt-2vqegkew0-ZuzGM1LO33C6Ts4nZyat1Q).
যদি আপুনি অধিক অনুশীলন কৰিব বিচাৰে, [code contributions](https://github.com/roshanjossey/code-contributions) পৰীক্ষা কৰক।
এতিয়া আপোনাক আন প্ৰকল্পত অৱদান কৰিবলৈ আৰম্ভ কৰা যাক। আমি সহজ সমস্যাসমূহ সহ কিছু প্ৰকল্পৰ তালিকা সংকলন কৰিছো যাৰ সহায়ত আপুনি আৰম্ভ কৰিব পাৰে। [ৱেব এপত প্ৰকল্পসমূহৰ তালিকা পৰীক্ষা কৰক](https://firstcontributions.github.io/#project-list).
### [অতিৰিক্ত সামগ্ৰী](additional-material/git_workflow_scenarios/additional-material.md)
## অন্য সঁজুলিসমূহ ব্যৱহাৰ কৰি টিউট'ৰিয়েলসকল
-1
View File
@@ -1,5 +1,4 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](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)
-1
View File
@@ -115,7 +115,6 @@ git push origin <add-your-branch-name>
### [Допълнителни материали](../additional-material/git_workflow_scenarios/additional-material.md)
## Уроци за иползването на други приложения
| <a href="../gui-tool-tutorials/github-desktop-tutorial.md"><img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="100"></a> | <a href="../gui-tool-tutorials/github-windows-vs2017-tutorial.md"><img alt="Visual Studio 2017" src="https://upload.wikimedia.org/wikipedia/commons/c/cd/Visual_Studio_2017_Logo.svg" width="100"></a> | <a href="../gui-tool-tutorials/gitkraken-tutorial.md"><img alt="GitKraken" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-icon.png" width="100"></a> | <a href="../gui-tool-tutorials/github-windows-vs-code-tutorial.md"><img alt="VS Code" src="https://upload.wikimedia.org/wikipedia/commons/1/1c/Visual_Studio_Code_1.35_icon.png" width=100></a> | <a href="../gui-tool-tutorials/sourcetree-macos-tutorial.md"><img alt="Sourcetree App" src="https://wac-cdn.atlassian.com/dam/jcr:81b15cde-be2e-4f4a-8af7-9436f4a1b431/Sourcetree-icon-blue.svg" width=100></a> | <a href="../gui-tool-tutorials/github-windows-intellij-tutorial.md"><img alt="IntelliJ IDEA" src="https://upload.wikimedia.org/wikipedia/commons/thumb/9/9c/IntelliJ_IDEA_Icon.svg/512px-IntelliJ_IDEA_Icon.svg.png" width=100></a> |
+1 -1
View File
@@ -121,7 +121,7 @@ git push origin -u <your-new-branch-name>
আপনার অবদানের আনন্দ উপভোগ করুন এবং [ওয়েব অ্যাপ](https://firstcontributions.github.io/#social-share)-এর মাধ্যমে বন্ধু ও অনুসরণকারীদের সাথে শেয়ার করুন।
যদি আপনি আরও অনুশীলন করতে চান, তাহলে [কোড অবদানগুলি](https://https://github.com/roshanjossey/code-contributions) চেকআউট করুন।
যদি আপনি আরও অনুশীলন করতে চান, তাহলে [কোড অবদানগুলি](https://github.com/roshanjossey/code-contributions) চেকআউট করুন।
এখন আপনি অন্যান্য প্রজেক্টগুলোতেও অবদান রাখতে পারেন। আপনার সুবিধার্থে আমরা সহজ সমস্যা সম্বলিত প্রজেক্টগুলোর একটি তালিকা তৈরি করেছি। ওয়েব অ্যাপে [প্রজেক্টগুলোর তালিকা](https://firstcontributions.github.io/#project-list) দেখুন।
+1 -2
View File
@@ -1,5 +1,4 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](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)
@@ -108,7 +107,7 @@ Enhorabona! Acabes de completar el procés de treball principal que et trobaràs
Ara, celebra la teva contribució i comparteix-la amb els teus amics i seguidors anant a [la web](https://firstcontributions.github.io/#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).
Si vols contribuir al projecte, pots començar amb aquesta [guia per contribuir al codi](https://github.com/roshanjossey/code-contributions).
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://firstcontributions.github.io/#project-list).
+105 -59
View File
@@ -1,120 +1,166 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[![Open Source Love](https://firstcontributions.github.io/open-source-badges/badges/open-source-v1/open-source.svg)](https://github.com/firstcontributions/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)
# Erste Beiträge
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="Repository forken" />
# First Contributions
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.
Dieses Projekt zielt darauf ab, Anfängern den Einstieg zu erleichtern und sie bei ihrem ersten Beitrag zu unterstützen. Wenn du deinen ersten Beitrag leisten möchten, befolge die folgenden Schritte.
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 nicht weißt wie man das Terminal/CMD bedient, [hier findest du Anleitungen für GUI Tools.](#Anleitungen-für-andere-Tools)_
Wenn du Git noch nicht installiert hast, [installiere es](https://help.github.com/articles/set-up-git/)
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="Forke dieses Repository" />
## Repository forken
#### Wenn du Git nicht auf deinem System installiert hast, [installiere es](https://...github.com/en/get-started/quickstart/set-up-git).
Forke das Repository durch das Anklicken der Schaltfläche "Fork". Dadurch erhältst du deine eigene Version des Projektes in deinem Profil.
## Forke dieses Repository
## Repository klonen
Forke dieses Repository indem du auf den Fork Button oben auf dieser Seite klickst.
Dies wird eine Kopie dieses Repository's in deinem Account erstellen.
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="Repository klonen" />
## Klone das Repository
Klone das Repository auf deinen Computer. Klicke auf die Schaltfläche "Clone or download" und anschließend auf das "copy to clipboard"-Symbol.
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="Klone dieses Repository" />
Öffne eine Kommandozeile und gib den folgenden git-Befehl ein:
Klone jetzt das geforkte Repository auf deinen Computer. Gehe zu deinem Github Account, öffne das geforkte Repository, drücke auf den Code Button, dann auf den SSH Tab und dann drücke auf das _copy url to clipboard_ icon.
```
git clone "Deine kopierte URL"
Öffne ein Terminal Fenster und führe den folgenden Git Befehl aus:
```bash
git clone "kopierte url"
```
Statt 'Deine kopierte URL' (ohne Anführungszeichen) füge die Repository-URL aus dem vorherigen Schritt ein.
wobei "kopierte url" (ohne die Anführungszeichen) die url zu diesem Repository ist (deine Fork von diesem Projekt). Im vorherigen Schritt siehst du wie du diese erhälst .
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/copy-to-clipboard.png" alt="URL kopieren" />
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/copy-to-clipboard.png" alt="URL in die Zwischenablage kopieren" />
Beispiel:
Zum Beispiel:
```
git clone https://github.com/dein-Name/first-contributions.git
```bash
git clone git@github.com:das-bist-du/erster-Beitrag.git
```
An der Stelle 'dein-Name' muss dein GitHub-Nutzername stehen. Mit diesem Befehl kopierst du den Inhalt deines first-contributions-Repository von GitHub auf deinen Computer.
wobei `das-bist-du` dein Github Nutzername ist. Hier kopierst du den Inhalt des first-contributions Repository's auf Github auf deinen Computer.
## Erstelle einen Branch
## Erstelle einen Zweig
Wechsle zum Repository-Verzeichnis auf deinem Computer (falls du es nicht schon getan hast).
Wechsle zum Repository Ordner (wenn du nicht bereits dort bist):
```
```bash
cd first-contributions
```
Erstelle nun einen Branch mit dem Befehl `git checkout`:
Erstelle nun einen Zweig, indem du den `git switch` Befehl benutzst:
```
git checkout -b <add-dein-Name>
```bash
git switch -c dein-neuer-zweig-name
```
Beispiel:
Zum Beispiel:
```
git checkout -b add-max-mustermann
```bash
git switch -c add-alonzo-church
```
(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.)
<details>
<summary> <strong>Wenn du auf irgendeinen Fehler bei der Nutzung von git switch stößt, drücke hier:</strong> </summary>
## Mache die nötigen Änderungen und committe sie
Wenn die Fehlermeldung "Git: `switch` is not a git command. See `git help`" erscheint, liegt dies wahrscheinlich daran das du eine veraltete Version von Git nutzt.
Ö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:
In diesem Fall versuche stattdessen `git checkout` zu nutzen:
```bash
git checkout -b dein-neuer-zweig-name
```
</details>
## Make necessary changes and commit those changes
Öffne nun die Datei `Contributors.md` in einem Texteditor und füge deinen Namen hinzu. Füge ihn nicht ganz am Anfang oder am Ende hinzu, sondern irgendwo dazwischen, mittendrin. Speichere jetzt die Datei.
<img align="right" width="450" src="https://firstcontributions.github.io/assets/Readme/git-status.png" alt="git status" />
Wenn du in den Projektordner gehst und den Befehl `git status`, ausführst werden dir die Änderungen angezeigt.
Füge diese Änderungen nun zu dem Zweig hinzu den du gerade erstellt hast, indem du den Befehl `git add` ausführst.
```bash
git add Contributors.md
```
Nun committest du deine Änderungen mit `git commit`:
Jetzt commite diese Änderungen mit dem `git commit` Befehl:
```
git commit -m "Add <dein-Name> to Contributors list"
```bash
git commit -m "Add your-name to Contributors list"
```
Ersetze `<dein-Name>` mit deinem Namen.
ersetze `your-name` mit deinem Namen.
## Pushe die Änderung zu GitHub
## Änderungen auf Github pushen
Pushe die Änderungen mit `git push`:
Übertrage deine Änderungen mit `git push`:
```
git push origin <add-dein-Name>
```bash
git push -u origin dein-zweig-name
```
Ersetze `<add-dein-Name>` mit dem Namen des Branches, den du zuvor erstellt hast.
ersetze `dein-zweig-name` mit dem Namen des Zweiges den du vorhin erstellt hast.
## Sende deine Änderungen zum Review
<details>
<summary> <strong>Solltest du auf irgendwelche Fehler beim Pushen stoßen, drücke hier:</strong> </summary>
Wenn du jetzt zu deinem Repository auf GitHub gehst, siehst du einen Knopf `Compare & pull request`. Klicke darauf.
- ### Authentifizierungs Fehler
<pre>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/<your-username>/first-contributions.git/'</pre>
Gehe zu [GitHub's tutorial](https://...github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account) wie du einen ssh Key zu deinem Account hinzufügst und konfigurierst.
Außerdem, kannst du 'git remote -v' ausführen um deine Remote Addresse anzuzeigen.
<img style="float: right;" src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="Erstelle einen pull request" />
Wenn es so aussieht:
<pre>origin https://github.com/your-username/your_repo.git (fetch)
origin https://github.com/your-username/your_repo.git (push)</pre>
Erstelle einen Pull Request indem du auf die Schaltfläche `Create pull request` klickst.
ändere es mit diesem Befehl:
```bash
git remote set-url origin git@github.com:dein-nutzername/dein_repo.git
```
Ansonsten wirst du noch immer aufgefordert Passwort und Benutzername einzugeben und bekommst einen Authentifizierungs Fehler.
</details>
<img style="float: right;" src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="Pull Request senden" />
## Reiche deine Änderungen für ein Review ein
Roshan Jossey wird nun deine Änderungen in den Master Branch dieses Projekts mergen. Du erhältst eine E-Mail, sobald dies geschehen ist.
Wenn du jetzt zu deinem Repository auf Github gehts, wirst du einen `Compare & pull request` Knopf sehen. Drücke diesen Knopf.
## Wie geht es weiter?
<img style="float: right;" src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="erstelle eine Pull-Request" />
Glückwunsch! Du hast so eben den Standard-Workflow _Fork -> Clone -> Edit -> Pull Request_ beendet, der dir als Mitwirkender häufig begegnen wird.
Jetzt, reiche deine Pull-Request ein.
Feiere deinen Beitrag zum Projekt und teile ihn mit deinen Freunden und Followern über unsere [Web-App](https://firstcontributions.github.io/#social-share).
<img style="float: right;" src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="Reiche deine Pull-Request ein" />
Wenn Du noch mehr üben möchtest, schau Dir das [Code-Contributions Repository] (https://github.com/roshanjossey/code-contributions) an.
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).
Bald werde ich alle deine Änderungen in den Haupt-Zweig dieses Projektes mergen. Du wirst eine Benachrichtigungs Email bekommen sobald die Änderungen gemerged wurden.
## Tutorials mit anderen Tools
## Was nun?
Gratulation! Du hast gerade den Standard _Forken -> Klonen -> Bearbeiten -> Pull-Request_ Workflow durchgeführt, dem du als Beitragender oft begegnen wirst!
Feier deinen Beitrag und teile in mit deinen Freunden und Followern indem du hier drückst [web app](https://firstcontributions.github.io/#social-share).
Wenn du gerne mehr Übung hättest, schau dir [code contributions](https://github.com/roshanjossey/code-contributions) an.
Jetzt los gehts, mit Beiträgen zu anderen Projekten. Wir haben eine Liste von Projekten mit leichten Fehlern für Einsteiger bereitgestellt. Schau dir [die Liste der Projekte in der Web-App an](https://firstcontributions.github.io/#project-list) an.
### [Zusätzliches Material](../additional-material)
## Anleitungen für andere Tools
| <a href="../gui-tool-tutorials/github-desktop-tutorial.md"><img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="100"></a> | <a href="../gui-tool-tutorials/github-windows-vs2017-tutorial.md"><img alt="Visual Studio 2017" src="https://upload.wikimedia.org/wikipedia/commons/c/cd/Visual_Studio_2017_Logo.svg" width="100"></a> | <a href="../gui-tool-tutorials/gitkraken-tutorial.md"><img alt="GitKraken" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-icon.png" width="100"></a> | <a href="../gui-tool-tutorials/github-windows-vs-code-tutorial.md"><img alt="VS Code" src="https://upload.wikimedia.org/wikipedia/commons/1/1c/Visual_Studio_Code_1.35_icon.png" width=100></a> | <a href="../gui-tool-tutorials/sourcetree-macos-tutorial.md"><img alt="Sourcetree App" src="https://wac-cdn.atlassian.com/dam/jcr:81b15cde-be2e-4f4a-8af7-9436f4a1b431/Sourcetree-icon-blue.svg" width=100></a> | <a href="../gui-tool-tutorials/github-windows-intellij-tutorial.md"><img alt="IntelliJ IDEA" src="https://upload.wikimedia.org/wikipedia/commons/thumb/9/9c/IntelliJ_IDEA_Icon.svg/512px-IntelliJ_IDEA_Icon.svg.png" width=100></a> |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [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) |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [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) |
<p>Dieses Projekt wird unterstützt von:</p>
<p>
<a href="https://www.digitalocean.com/">
<img src="https://opensource.nyc3.cdn.digitaloceanspaces.com/attribution/assets/SVG/DO_Logo_horizontal_blue.svg" width="201px">
</a>
</p>
+44 -12
View File
@@ -9,11 +9,11 @@
Este proyecto tiene como objetivo simplificar y guiar la forma en que los principiantes hacen su primera contribución. Si está buscando hacer su primera contribución, siga los pasos a continuación.
#### *Si eres un neófit@ con la linea de comandos, [](#Tutoriales-usando-otras-herramientas)*
#### *Si no estás familiarizado con la línea de comandos, [aquí hay tutoriales usando herramientas con Interfaz Gráfica (GUI)](#tutoriales-usando-otras-herramientas)*
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="fork de este repositorio" />
En caso de no tener instalado Git en tu equipo, te dejo una para [guia]( https://git-scm.com/book/es/v2/Inicio---Sobre-el-Control-de-Versiones-Instalaci%C3%B3n-de-Git) para instalarlo.
En caso de no tener instalado Git en tu equipo, te dejo una [guia]( https://git-scm.com/book/es/v2/Inicio---Sobre-el-Control-de-Versiones-Instalaci%C3%B3n-de-Git) para instalarlo.
## Has un "Fork" de este repositorio
@@ -23,15 +23,15 @@ Presiona el boton "fork" de este repositorio en la parte superior derecha de la
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clonar este repositorio" />
Ahora clona el repositorio al que le hiciste un fork previamente, el URL del repositorio deberia estar asi `https://github.com/<tu-usuario>/first-contributions`. Entra en tu cuenta de Github, y has click en el botón `clone or download` y luego has clic en el ícono para `copy`.
Ahora clona el repositorio al que le hiciste un fork previamente, el URL del repositorio deberia estar asi `https://github.com/<tu-usuario>/first-contributions`. Entra en tu cuenta de Github, y has click en el botón `Code` y luego en la pestaña SSH y luego haz clic en el icono de _copiar al portapapeles_.
Abre tu terminal y ejecuta el siguiente comando:
Abre tu terminal y ejecuta el siguiente comando git:
```
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 se veria algo asi `https://github.com/<tu-usuario>/first-contributions.git`(tu *fork* a este proyecto).
Donde "la url del repositorio que copiaste" (sin las comillas dobles) es la *url* a este repositorio (tu *fork* a este proyecto), se veria algo asi `https://github.com/<tu-usuario>/first-contributions.git` .
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/copy-to-clipboard.png" alt="copiar URL al portapapeles" />
@@ -39,7 +39,7 @@ Por ejemplo:
```
git clone https://github.com/<tu-usuario>/first-contributions.git
```
Donde `<tu-usuario>` es tu usuario de GitHub. Con este comando estas copiando loslos contenidos del repositorio *first-contributions* de GitHub a tu equipo.
Donde `<tu-usuario>` es tu nombre de usuario de GitHub. Con este comando estas copiando los contenidos del repositorio *first-contributions* de GitHub a tu equipo.
## Crea una rama (*Branch*)
@@ -49,19 +49,28 @@ 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`:
Ahora crea una rama (*branch*) usando el comando `git checkout` o `git switch`:
```
git checkout -b <dale un nombre>
git switch -c <dale un nombre>
```
Por ejemplo:
```
git checkout -b add-julio-jaramillo
git switch -c add-julio-jaramillo
```
<details>
<summary> <strong>Si obtienes algún error usando git switch, haz clic aquí:</strong> </summary>
Si aparece el mensaje de error "Git: `switch` no es un comando git. Consulta `git help`", es probable que estés usando una versión anterior de git.
En este caso, intenta usar git checkout en su lugar.
</details>
## Haz los cambios necesarios y has un "Commit" de 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.
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. Ahora guarda el archivo.
<img align="right" width="450" src="https://firstcontributions.github.io/assets/Readme/git-status.png" alt="git status" />
@@ -82,12 +91,35 @@ reemplazando `<nombre>` con tu nombre.
## Haz un "Push" de tus cambios a GitHub
Mandar un *push* de tus cambios usando el comando `git push`:
Envía tus cambios usando el comando `git push`:
```
git push origin <nombre-rama>
git push -u origin <nombre-rama>
```
Reemplaza `<nombre-rama>` con el nombre de la rama que creaste anteriormente.
<details>
<summary> <strong>Si obtienes algún error al enviar (Push), haz clic aquí:</strong> </summary>
- ### Error de Autenticación
<pre>remote: El soporte para la autenticación de contraseña se eliminó el 13 de agosto de 2021. Utiliza un token de acceso personal en su lugar.
remote: Consulta [https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/](https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/) para obtener más información.
fatal: Fallo en la autenticación para '[https://github.com/](https://github.com/)<tu-usuario>/first-contributions.git/'</pre>
Ve al [tutorial de GitHub](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account) sobre cómo generar y configurar una clave SSH en tu cuenta.
Además, es posible que desees ejecutar `git remote -v` para verificar tu dirección remota.
Si se ve algo como esto:
<pre>origin [https://github.com/tu-usuario/tu_repo.git] (fetch)
origin [https://github.com/tu-usuario/tu_repo.git] (push)</pre>
cámbialo usando este comando:
```bash
git remote set-url origin git@github.com:tu-usuario/tu_repo.git
```
De lo contrario, aún se te pedirá un nombre de usuario y contraseña y obtendrás un error de autenticación.
</details>
## 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.
@@ -104,9 +136,9 @@ Pronto estaré combinando tus cambios (haciendo *merge*) con la rama master de e
¡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://firstcontributions.github.io/#social-share).
Festeja tu contribución y compártela con tus amigos y seguidores yendo a la [web app](https://firstcontributions.github.io/#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).
Si deseas más práctica, consulta [code contributions](https://github.com/roshanjossey/code-contributions).
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://firstcontributions.github.io/#project-list).
+27 -2
View File
@@ -1,5 +1,4 @@
[![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)
# <div dir="rtl">مساهمتك الأولى</div>
@@ -114,6 +113,31 @@ git push origin "add-your-name"
<div dir="rtl">إستبدل <code>&#60;add-your-name&#62;</code> بإسم الفرع اللي انت لسة عامله .</div>
<details dir="rtl">
<summary> <strong>لو عندك مشكلة وانت بتعمل <bdi>push</bdi> غالبا هتكون <bdi>Authentication error</bdi></strong> </summary>
- ### Authentication Error
<pre>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/<your-username>/first-contributions.git/'</pre>
أسهل طريقة لحل المشكلة انك تعمل <bdi>ssh key</bdi> وتحطه علي <bdi>GitHub</bdi>
[GitHub's Tutorial - Create an ssh key](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)
[GitHub's tutorial - adding ssh key to your account](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
بكده هتكون <bdi>authenticated</bdi> و مش هيكون عندك مشكلة لما تعمل <bdi>push</bdi>
تقدر تتاكد انك بترفع علي الريبو الصح لما تكتب في ال
```bash
git remote -v
```
لو ظهرلك كده:
<pre>origin https://github.com/your-username/your_repo.git (fetch)
origin https://github.com/your-username/your_repo.git (push)</pre>
يبقي معندكش مشكلة
غير كده تقدر تغير ال <bdi>remote address</bdi> كده
```bash
git remote set-url origin git@github.com:your-username/your_repo.git
```
</details>
<br>
<h2 id="سلم-تغيراتك-للمراجعة"><a name="سلم-تغيراتك-للمراجعة" href="#سلم-تغيراتك-للمراجعة"></a><div dir="rtl">سلم تغيراتك للمراجعة</div></h2>
@@ -138,7 +162,8 @@ git push origin "add-your-name"
احتفل بأول مساهمة ليك، أعمل شير مع صحابك ومتابعينك عن طريق زيارة <a href="https://firstcontributions.github.io/#social-share">الموقع دة. </a>
</div>
<div dir="rtl">ممكن تنضم للفريق على Slack لو حابب تساعد او عندك أسئلة. ></div>
<div dir="rtl">إذا كنت ترغب في المزيد من التدريب <a href="https://github.com/roshanjossey/code-contributions">مساهمات </a></div>
<br>
-3
View File
@@ -1,5 +1,4 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](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)
@@ -117,8 +116,6 @@ Well done! Ye jus' completed th' standard _fork -> clone -> edit -> PR_ workflow
Celebrate yer contribution 'n share it wit' yer hearties 'n followers by goin' t' [web app](https://firstcontributions.github.io/#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://firstcontributions.github.io/#project-list).
### [Additional material](../additional-material/git_workflow_scenarios/additional-material.md)
+2 -3
View File
@@ -1,5 +1,4 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](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)
@@ -83,7 +82,7 @@ Ahora haz un *commit* sobre estos cambios ejecutando el comando `git commit`:
```
git commit -m "Add <tu-nombre> to Contributors list"
```
cambiando `<tu-nombre>` por tu nombre.
Cambiando `<tu-nombre>` por tu nombre.
## Sube (*Push*) tus cambios a GitHub
@@ -111,7 +110,7 @@ Pronto estaré fusionando tus cambios (haciendo *merge*) con la rama master de e
Celebra tu contribución y compártela con tus amigos y seguidores yendo a [web app](https://firstcontributions.github.io/#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).
Si quieres más práctica, echa un vistazo a [contribuciones de código](https://github.com/roshanjossey/code-contributions).
Ahora empieza a contribuir en 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).
+1 -1
View File
@@ -1,6 +1,6 @@
# የመጀመሪያ አስተዋጽዖዎች
ይህ ፕሮጀክት ጀማሪዎች የመጀመሪያ አስተዋፅዖቸውን እንዲያደርጉ መንገዱን ለማቅለል እና ለመምራት ያለመ ነው። የመጀመሪያውን አስተዋፅዖ ማድረግ ከፈለጉ ከታች ያሉትን ደረጃዎች ይከተሉ።
ይህ ፕሮጀክት ጀማሪዎች የመጀመሪያ አስተዋፅዖቸውን እንዲያደርጉ መንገዱን ለማቅለል እና ለመምራት ያለመ ነው። የመጀመሪያ አስተዋፅዖዎን ማድረግ ከፈለጉ ከታች ያሉትን ደረጃዎች ይከተሉ።
_በትእዛዝ መስመሩ ካልተመቻችሁ [የጂአይ መሳሪያዎችን በመጠቀም መማሪያ ይኸውና](#መማሪያዎች-ሌሎች-መሳሪያዎችን-በመጠቀም)_
+61 -26
View File
@@ -10,27 +10,27 @@ C'est toujours compliqué la première fois que l'on fait quelque chose. La peur
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.
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="embrancher ce repertoire" />
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="forker ce repertoire" />
Si vous n'avez pas git sur votre ordinateur, [ installez-le ]( https://help.github.com/articles/set-up-git/ ).
Si vous n'avez pas encore Git installé sur votre machine, [ installez-le ]( https://help.github.com/articles/set-up-git/ ).
## Embranchez ce répertoire (aussi appelé un Fork)
## Faire un fork de ce dépôt
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.
Forkez ce dépôt en cliquant sur le bouton *fork* en haut de cette page.
Cela créera une copie de ce dépôt dans votre propre compte GitHub
## Clonez ce répertoire
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clonez ce répertoire" />
Maintenant, clonez ce répertoire sur votre ordinateur. Cliquez sur le bouton clone puis cliquez sur l'icône *copier dans le presse-papier*.
Maintenant, clonez ce répertoire sur votre ordinateur. Allez sur votre compte GitHub, ouvrez le dépôt forké, cliquez sur le bouton *Code*, puis sur longlet *SSH* et enfin sur licône *copier dans le presse-papiers*.
Ouvrez une invite de commande (si vous êtes sous Windows) ou un terminal (si vous êtes sous MacOS ou Linux) et exécutez les commandes git suivantes :
Ouvrez une invite de commande (si vous êtes sous Windows) ou un terminal (si vous êtes sous MacOS ou Linux) et exécutez la commande git suivante :
```
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.
où "l'url que vous venez de copier" (sans les guillemets) est l'url du dépôt forké. Revoir les étapes précédentes pour obtenir lURL exacte.
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/copy-to-clipboard.png" alt="copier l'URL dans le presse-papier" />
@@ -38,7 +38,7 @@ Par exemple :
```
git clone https://github.com/votre-nom-d-utilisateur/first-contributions.git
```
`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.
`votre-nom-d-utilisateur` est votre nom d'utilisateur GitHub. Ici vous êtes en train de copier le contenu du dépôt `first-contributions` depuis GitHub sur votre ordinateur.
## Créez une branche
@@ -56,42 +56,77 @@ 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.)
(Le nom de la branche n'a pas besoin de contenir le terme *add*, mais il est mieux de l'inclure car l'objectif de cette branche est d'ajouter votre nom à une liste.)
## Effectuez les modifications nécessaires et engagez-les
<details> <summary> <strong>Si vous rencontrez une erreur avec git switch, cliquez ici :</strong> </summary>
Si le message "Git: switch is not a git command. See git help" saffiche, cest probablement parce que vous utilisez une ancienne version de Git.
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` :
Dans ce cas, essayez plutôt :
```
git checkout -b nom-de-ta-nouvelle-branche
```
</details>
## Effectuez les modifications nécessaires et enregistrez-les
Ouvrez le fichier `Contributors.md` dans un éditeur de texte, ajoutez-y votre nom, et enregistrez-le. Ne lajoutez pas au début ou à la fin du fichier, mais quelque part au milieu.
<img align="right" width="450" src="https://firstcontributions.github.io/assets/Readme/git-status.png" alt="git status" />
Si vous ouvrez l'invite de commande et que 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`:
Maintenant faites un commit de ces modifications avec la commande `git commit`:
```
git commit -m "Add <votre-nom> to Contributors list"
```
en remplaçant `<votre-nom>` par votre nom.
## Poussez les modifications vers GitHub
## Envoyez les modifications vers GitHub
Poussez vos modifications avec la commande `git push` :
```
git push origin <add-votre-nom>
git push -u origin <nom-de-votre-branche>
```
en remplaçant `<add-votre-nom>` avec le nom de la branche précédemment créée.
en remplaçant `<nom-de-votre-branche>` avec le nom de la branche précédemment créée.
## Soumettez vos changements pour révision
<details> <summary> <strong>Si tu obtiens une erreur au moment de pousser, clique ici :</strong> </summary>
Si vous visitez votre répertoire sur Github, vous verrez un bouton `Compare & pull request`. Cliquez sur ce bouton.
- ### Erreur dauthentification
<pre>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/<ton-nom-utilisateur>/first-contributions.git/'</pre>
Suivez le tutoriel GitHub pour générer et configurer une clé SSH sur votre compte.
<img style="float: right;" src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="create a pull request" />
Vous pouvez également exécuter git remote -v pour vérifier votre adresse distante.
Maintenant soumettez la demande de tirage.
Si elle ressemble à ceci :
<img style="float: right;" src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="submit pull request" />
<pre>origin https://github.com/ton-nom-utilisateur/ton_repo.git (fetch) origin https://github.com/ton-nom-utilisateur/ton_repo.git (push)</pre>
Modifiez-la avec cette commande :
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.
```
git remote set-url origin git@github.com:ton-nom-utilisateur/ton_repo.git
```
Sinon, vous continuerez de devoir entrer votre mot de passe et vous obtiendrez une erreur dauthentification.
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.
</details>
## Soumettez votre contribution pour révision
Si vous vous rendez sur votre répertoire sur Github, vous verrez un bouton `Compare & pull request`. Cliquez dessus.
<img style="float: right;" src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="créer une pull request" />
Soumettez ensuite la *pull request*.
<img style="float: right;" src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="soumettre une pull request" />
Je fusionnerai bientôt vos modifications dans la branche principale du projet.
Vous recevrez un e-mail de confirmation une fois que ce sera fait.
La branche main de votre dépôt forké ne subira pas de modification. Pour que votre dépôt soit synchronisé avec le mien, suivez les étapes suivantes.
## Gardez votre embranchement synchronisé avec ce répertoire
@@ -113,13 +148,13 @@ Ici nous cherchons toutes les modifications dans mon embranchement (upstream rem
```
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 :
Ici nous appliquons toutes les modifications que vous avez récupéré à 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.
Avertissement: Cette fois, vous poussez les modifications au répertoire distant appelé origin.
A ce niveau j'ai fusionné votre branche `<add-votre-nom>` avec ma branche main, et vous avez fusionné ma branche main avec votre branche main. Votre branche `<add-votre-nom>` n'est plus utile, donc vous pouvez la supprimer :
A cet instant j'ai fusionné votre branche `<add-votre-nom>` avec ma branche main, et vous avez fusionné ma branche main avec votre branche main. Votre branche `<add-votre-nom>` n'est plus utile, donc vous pouvez la supprimer :
```
git branch -d <add-votre-nom>
```
+4 -4
View File
@@ -49,7 +49,7 @@ git clone https://github.com/this-is-you/first-contributions.git
cd first-contributions
```
Τώρα δημιουργείστε ένα νέο παρακλάδι χρησιμοποιώντας την εντολή `git switch` :
Τώρα δημιουργήστε ένα νέο παρακλάδι χρησιμοποιώντας την εντολή `git switch` :
```
git switch -c your-new-branch-name
@@ -63,7 +63,7 @@ git switch -c add-alonzo-church
(Το όνομα του παρακλαδιού δεν χρειάζεται να περιέχει την λέξη _add_ αλλά είναι λογικό να την συμπεριλάβουμε μιας και ο σκοπός του παρακλαδιού είναι να προσθέσουμε το όνομα μας σε μια λίστα.)
## Πραγματοποιήστε τις αλλαγές και αποθηκεύστετες (add & commit)
## Πραγματοποιήστε τις αλλαγές και αποθηκεύστε τες (add & commit)
Τώρα ανοίξτε το αρχείο `Contributors.md` με έναν επεξεργαστή κειμένου. Χρειάζεται να είστε εξοικειωμένοι με την Markdown, μια ελαφριά γλώσσα σήμανσης. Δείτε στο [cheat sheet](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet) για το πως να χρησιμοποιήσετε την Markdown.
@@ -107,13 +107,13 @@ git push origin <add-your-name>
όπου `<add-your-name>` αντικαταστήστε με το όνομα του παρακλαδιού(branch) που δημιουργήσατε προηγουμένως
## Υποβάλλετε τις αλλαγές σας για έλεγχο
## Υποβάλετε τις αλλαγές σας για έλεγχο
Εάν πάτε στο αποθετήριο (repository) στο github θα δείτε ένα κουμπί με τίτλο `Compare & pull request`. Κάντε κλικ σε αυτό το κουμπί.
<img style="float: right;" src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="create a pull request" />
Τώρα υποβάλλετε το pull request.
Τώρα υποβάλετε το pull request.
<img style="float: right;" src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="submit pull request" />
+5 -24
View File
@@ -1,7 +1,7 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](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)
# પ્રથમ યોગદાન
પ્રથમ વખત કંઈક કરવું થોડું મુશ્કેલ છે. ખાસ કરીને જ્યારે તમે જુથ સાથે મળીને કામ કરી રહ્યા હોવ, ત્યારે ભૂલો કરવી એ સારી વાત નથી. પરંતુ એકબીજા સાથે મળીને અને એક જ સાથે કામ કરવું એ જ તો ઓપેન સોર્સ છે. અમે તમારું પ્રથમ ઓપન સોર્સ કોન્ટ્રિબ્યુશન / યોગદાન સરળ બનાવાનો પ્રયત્ન કરીશુ.
@@ -14,27 +14,22 @@
જો તમારા કમ્પ્યુટર પર Git ઇન્સ્ટોલ નથી, [ તો Git ઈન્સ્ટોલ કરો](https://help.github.com/articles/set-up-git/)
## રિપોઝીટરીને ફોર્ક કરો
ફોર્ક(કાંટા) બટન પર ક્લિક કરવાથી આ રિપોઝીટરી ફોર્ક થાય છે, આ તમારા GitHub એકાઉન્ટમાં આ રિપોઝીટરીની એક નકલ (કોપી) બનાવશે.
## રિપોઝીટરી ક્લોન કરો
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clone this repository" />
હવે તમે આ રેપો તમારા કમ્પ્યુટરમાં ક્લોન કરો (અર્થાત ડાઉનલોડ કરો). તમારા GitHub એકાઉન્ટ પર જાવ, કોડ બટન પર ક્લિક કરો અને પછી `copy to clipboard` આઇકોન પર ક્લિક કરો. આનાથી એ રેપોજીટરીનો યુઆરએલ કોપી થશે.
તમારા કમ્પ્યુટર પર એક ટર્મિનલ / કમાંડ પ્રોમ્પ્ટ ખોલો અને નીચે દર્શાવ્યા મુજબ git આદેશ ચલાવો:
```
git clone "યુઆરએલ જે તમે હમણાં જ નકલ(ક્લોન) કરી"
```
જ્યાં "યુઆરએલ જે તમે હમણાં જ કોપી કર્યું છે" (અવતરણ ચિહ્નો સિવાય) એ આ રિપોઝીટરી(આ પ્રોજેક્ટનો તમારો ફૉર્ક) ની URL ના સંગ્રહ માટે છે. તેની URL ને મેળવવા માટે પાછલા પગલાં જુઓ. તેમને કોપી કરેલ યુઆરએલ સાથે બદલી કાઢો.
ઉદાહરણ તરીકે:
@@ -45,19 +40,16 @@ git clone https://github.com/આ-તમે-છો/first-contributions.git
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/copy-to-clipboard.png" alt="copy URL to clipboard" />
'આ-તમે-છો' તમારા GitHub એકાઉન્ટનું `username` છે. અહીં તમે તમારા કમ્પ્યુટરમાં GitHub થી first-contributions રિપોને કોપી કરી રહ્યા છો અથવા તેના એક સ્થાનિક / લોકલ કોપી બનાવી રહ્યા છે.
## એક બ્રાંચ બનાવો
તમારા કમ્પ્યુટર પર બનાવેલ રિપોઝીટરીની કોપીનાં ફોલ્ડર / ડિરેક્ટરીમાં જાવ (જો હજુ સુધી તમે ત્યાં ન હોવ તો નીચે આપેલ Command(આદેશ) ચલાવો)
```
cd first-contributions
```
હવે 'git checkout' command(આદેશ) નો ઉપયોગ કરીને એક નવી શાખા(Branch) બનાવો. નવી શાખા(Branch) બનાવવા માટે -b વિકલ્પનો ઉપયોગ થાય છે.
```
@@ -70,25 +62,20 @@ git checkout -b <તમારી-શાખા-નામ-ઉમેરો>
git checkout -b add-alonzo-church
```
(શાખા(Branch)ના નામમાં 'add' ઉમેરવાની જરૂર નથી, પરંતુ તેમાં શામેલ કરવું યોગ્ય છે કારણ કે શાખા(Branch)નો હેતુ એક નામ છે, જે નામ ઉમેરવાનું છે.)
## આવશ્યક ફેરફારો કરો અને તે ફેરફારોને કમીટ કરો-
હવે 'Contributors.md` ફાઇલને એક ટેક્સ્ટ એડિટરમાં ખોલો અને તેમા તમારુ નામ લખો. ફાઇલની શરૂઆત અથવા અંતે ઉમેરવાને બદલે, તેને મધ્યમાં ગમે ત્યાં રાખો. હવે, ફાઇલને સેવ કરો.
<img align="right" width="450" src="https://firstcontributions.github.io/assets/Readme/git-status.png" alt="git status" />
જો તમે પ્રોજેક્ટની ડાઈરેક્ટરીમા જશો અને કમાન્ડ પ્રોમ્પ્ટમાં `git status` નિર્દેશ ચલાવશો, તો તમે કરેલા પરિવર્તન જોઈ શક્શો. તે પરિવર્તન બનાવવામાં આવેલ શાખા(Branch)માં ઉમેરવા માટે 'git add` કમાન્ડ વાપરો.
```
git add Contributors.md
```
હવે તમારા પોતાના ફેરફારોને 'git commit' આદેશનો ઉપયોગ કરી કમીટ કરો.
```
@@ -97,8 +84,8 @@ git commit -m "Add <તમારુ-નામ> to Contributors list"
<તમારુ નામ> ની જગ્યાએ તમારું નામ દાખલ કરો
##
તમારા ફેરફારો ને Github માં પુશ કરો (ધકેલો).
`git push` ઉપયોગ કરીને તમારા પરિવર્તન ને પુશ કરો
@@ -111,7 +98,6 @@ git push origin <તમારી-શાખા-નામ-ઉમેરો>
## તમારા ફેરફારોના રીવ્યુ માટે સબમિટ કરો
જો તમે તમારા github એકાઉન્ટ પર તમારી રિપો માં જાવ તો Compare & pull request નો ઓપ્શન હશે. તેને દબાવો.
<img style="float: right;" src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="create a pull request" />
@@ -121,23 +107,18 @@ git push origin <તમારી-શાખા-નામ-ઉમેરો>
<img style="float: right;" src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="submit pull request" />
ટૂંક સમયમાં હું તમારા ફેરફારો માટે આ પ્રોજેક્ટની માસ્ટર શાખામાં મર્જ ક્રી દઇશ. તમને એક મેલ આવશે જ્યારે તમારા ફેરફારો મર્જ થશે.
## હવે, અહીંથી ક્યાં જવું ?
અભિનંદન!:tada: તમે હમણાં જ સ્ટાન્ડર્ડ `fork -> clone -> edit -> pull request` વર્કફ્લો પૂર્ણ કર્યો છે. જેનો તમે વારંવાર સહયોગકર્તા (contributor) તરીકે સામનો કરશો!
તમારા પ્રથમ યોગદાનની ઉજવણી કરો અને [વેબ એપ્લિકેશન](https://firstcontributions.github.io/#social-share) પર જઈને તમારા મિત્રો અને ફોલોઅર્સ સાથે શેર કરો.
જો તમને કોઈ મદદની જરૂર હોય અથવા તમારી કોઈ સમસ્યા હોય તો તમે અમારી સ્લેક ટીમમા જોડાઈ શકો છો. [સ્લેક ટીમ જોઈન કરો.](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA)
જો તમને વધુ પ્રેક્ટિસ જોઈતી હોય, તો [કોડ યોગદાન ચેકઆઉટ](https://github.com/roshanjossey/code-contributions) કરો.
ચાલો, હવે તમને અન્ય પ્રોજેક્ટ્સમાં કંટ્ર્રીબ્યુટ કરવામા મદદ કરુ. અમે તમારા માટે એક યાદી બનાવી છે જેમા ખૂબ સરળ issues(મુદ્દાઓ) છે વેબ એપમા પ્રોજેક્ટ્સ ની સૂચિ જુઓ.](https://firstcontributions.github.io/#project-list)
## અન્ય સાધનોનો ઉપયોગ કરીને ટ્યુટોરીયલ્સ
| <a href="../gui-tool-tutorials/github-desktop-tutorial.md"><img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="100"></a> | <a href="../gui-tool-tutorials/github-windows-vs2017-tutorial.md"><img alt="Visual Studio 2017" src="https://upload.wikimedia.org/wikipedia/commons/c/cd/Visual_Studio_2017_Logo.svg" width="100"></a> | <a href="../gui-tool-tutorials/gitkraken-tutorial.md"><img alt="GitKraken" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-icon.png" width="100"></a> | <a href="../gui-tool-tutorials/github-windows-vs-code-tutorial.md"><img alt="VS Code" src="https://upload.wikimedia.org/wikipedia/commons/1/1c/Visual_Studio_Code_1.35_icon.png" width=100></a> | <a href="../gui-tool-tutorials/sourcetree-macos-tutorial.md"><img alt="Sourcetree App" src="https://wac-cdn.atlassian.com/dam/jcr:81b15cde-be2e-4f4a-8af7-9436f4a1b431/Sourcetree-icon-blue.svg" width=100></a> | <a href="../gui-tool-tutorials/github-windows-intellij-tutorial.md"><img alt="IntelliJ IDEA" src="https://upload.wikimedia.org/wikipedia/commons/thumb/9/9c/IntelliJ_IDEA_Icon.svg/512px-IntelliJ_IDEA_Icon.svg.png" width=100></a> |
| --- | --- | --- | --- | --- | --- |
| [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) |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [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) |
-1
View File
@@ -1,5 +1,4 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](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)
+36 -5
View File
@@ -26,17 +26,17 @@ Sekarang kloning repositori yang sudah Anda _fork_ ke komputer Anda. Pergi ke ak
Buka sebuah terminal dan jalankan perintah git berikut:
```
git clone "url yang telah disalin"
git clone "url yang telah Anda 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.
bagian "url yang telah Anda disalin" (tanpa tanda petik) adalah url ke repositori ini (proyek yang telah Anda _fork_ ini). Lihat langkah sebelumnya untuk mendapatkan url.
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/copy-to-clipboard.png" alt="copy URL to clipboard" />
Sebagai contoh:
Contohnya:
```
git clone https://github.com/ini-adalah-anda/first-contributions.git
git clone git@github.com:ini-adalah-anda/first-contributions.git
```
bagian `ini-adalah-anda` adalah nama pengguna GitHub Anda. Di sini Anda menyalin konten dari repositori first-contributions di GitHub ke komputer Anda.
@@ -55,12 +55,25 @@ Sekarang buatlah sebuah _branch_ menggunakan perintah `git checkout`:
git checkout -b <tambahkan-nama-branch-baru>
```
Sebagai contoh:
Contohnya:
```
git checkout -b add-alonzo-church
```
<details>
<summary> <strong>Jika kamu mendapatkan beberapa kesalahan menggunakan <i>git switch</i>, klik disini:</strong> </summary>
Jika pesan error: "Git: `switch` is not a git command. See `git help`" muncul, kemungkinan besar Anda menggunakan versi git yang lama.
Dalam kasus ini, coba gunakan `git checkout` sebagai gantinya:
```bash
git checkout -b your-new-branch-name
```
</details>
## Buat Perubahan Yang Diperlukan Lalu _Commit_ (Simpan) Perubahan Tersebut
Sekarang buka berkas `Contributors.md` menggunakan teks editor, tambahkan nama Anda ke dalamnya. Jangan menambahkan pada awal atau akhir dari berkas. Simpan dimana saja di antaranya. Sekarang simpan berkasnya.
@@ -102,8 +115,19 @@ ganti bagian `<tambahkan-nama-cabang-baru>` dengan nama cabang yang sebelumnya A
fatal: Authentication failed for 'https://github.com/<your-username>/first-contributions.git/'</pre>
Buka [tutorial GitHub](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account) untuk menghasilkan dan mengkonfigurasi sebuah kunci SSH ke akun Anda.
Jika kelihatannya seperti ini:
<pre>origin https://github.com/your-username/your_repo.git (fetch)
origin https://github.com/your-username/your_repo.git (push)</pre>
Buat perubahan dengan perintah:
<pre>git remote set-url origin git@github.com:your-username/your_repo.git</pre>
Jika tidak, Anda akan tetap dimintai nama pengguna dan kata sandi serta mendapatkan kesalahan autentikasi.
</details>
## Kirim Perubahan Untuk Diperiksa
Jika Anda membuka repositori Anda di GitHub, Anda akan melihat sebuah tombol `Compare & pull request`. Tekan tombol tersebut.
@@ -133,3 +157,10 @@ Sekarang mari kita mulai dengan berkontribusi di proyek lain. Kami sudah menyusu
| <a href="../gui-tool-tutorials/github-desktop-tutorial.md"><img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="100"></a> | <a href="../gui-tool-tutorials/github-windows-vs2017-tutorial.md"><img alt="Visual Studio 2017" src="https://upload.wikimedia.org/wikipedia/commons/c/cd/Visual_Studio_2017_Logo.svg" width="100"></a> | <a href="../gui-tool-tutorials/gitkraken-tutorial.md"><img alt="GitKraken" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-icon.png" width="100"></a> | <a href="../gui-tool-tutorials/github-windows-vs-code-tutorial.md"><img alt="VS Code" src="https://upload.wikimedia.org/wikipedia/commons/1/1c/Visual_Studio_Code_1.35_icon.png" width=100></a> | <a href="../gui-tool-tutorials/sourcetree-macos-tutorial.md"><img alt="Sourcetree App" src="https://wac-cdn.atlassian.com/dam/jcr:81b15cde-be2e-4f4a-8af7-9436f4a1b431/Sourcetree-icon-blue.svg" width=100></a> | <a href="../gui-tool-tutorials/github-windows-intellij-tutorial.md"><img alt="IntelliJ IDEA" src="https://upload.wikimedia.org/wikipedia/commons/thumb/9/9c/IntelliJ_IDEA_Icon.svg/512px-IntelliJ_IDEA_Icon.svg.png" width=100></a> |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [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) |
<p>Proyek ini didukung oleh:</p>
<p>
<a href="https://www.digitalocean.com/">
<img src="https://opensource.nyc3.cdn.digitaloceanspaces.com/attribution/assets/SVG/DO_Logo_horizontal_blue.svg" width="201px">
</a>
</p>
+1 -1
View File
@@ -1,5 +1,5 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](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)
+3 -6
View File
@@ -1,5 +1,4 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](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)
@@ -124,17 +123,15 @@ git push -u origin your-branch-name
첫 기여에 대한 소식을 친구들 및 팔로워에게 [웹 앱](https://firstcontributions.github.io/#social-share)을 통해 공유해보세요.
도움이 필요하거나 질문이 있다면 저희 slack 팀에 참여할 수 있습니다. → [slack 팀 참여하기](https://firstcontributors.slack.com/join/shared_invite/zt-29qhyr9lt-Bi7WLbgGIFqV7aCEG_grvg#/shared-invite/email)
이제 다른 프로젝트에도 기여해보세요! 지금 바로 시작할 수 있는 난이도가 낮은 이슈들로 가득찬 목록이 있습니다. [웹앱의 프로젝트 목록](https://firstcontributions.github.io/#project-list)에서 확인해보세요.
### [추가 자료](../additional-material/translations/Korean/additional-material.ko.md)
## 다른 도구들을 사용한 튜토리얼
| <a href="gui-tool-tutorials/github-desktop-tutorial.md"><img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="100"></a> | <a href="gui-tool-tutorials/github-windows-vs2017-tutorial.md"><img alt="Visual Studio 2017" src="https://upload.wikimedia.org/wikipedia/commons/c/cd/Visual_Studio_2017_Logo.svg" width="100"></a> | <a href="gui-tool-tutorials/gitkraken-tutorial.md"><img alt="GitKraken" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-icon.png" width="100"></a> | <a href="gui-tool-tutorials/github-windows-vs-code-tutorial.md"><img alt="VS Code" src="https://upload.wikimedia.org/wikipedia/commons/2/2d/Visual_Studio_Code_1.18_icon.svg" width=100></a> | <a href="gui-tool-tutorials/sourcetree-macos-tutorial.md"><img alt="Sourcetree App" src="https://wac-cdn.atlassian.com/dam/jcr:81b15cde-be2e-4f4a-8af7-9436f4a1b431/Sourcetree-icon-blue.svg" width=100></a> | <a href="gui-tool-tutorials/github-windows-intellij-tutorial.md"><img alt="IntelliJ IDEA" src="https://upload.wikimedia.org/wikipedia/commons/thumb/9/9c/IntelliJ_IDEA_Icon.svg/512px-IntelliJ_IDEA_Icon.svg.png" width=100></a> |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [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) |
| <a href="../gui-tool-tutorials/github-desktop-tutorial.md"><img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="100"></a> | <a href="../gui-tool-tutorials/github-windows-vs2017-tutorial.md"><img alt="Visual Studio 2017" src="https://upload.wikimedia.org/wikipedia/commons/c/cd/Visual_Studio_2017_Logo.svg" width="100"></a> | <a href="../gui-tool-tutorials/gitkraken-tutorial.md"><img alt="GitKraken" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-icon.png" width="100"></a> | <a href="../gui-tool-tutorials/github-windows-vs-code-tutorial.md"><img alt="VS Code" src="https://upload.wikimedia.org/wikipedia/commons/2/2d/Visual_Studio_Code_1.18_icon.svg" width=100></a> | <a href="../gui-tool-tutorials/sourcetree-macos-tutorial.md"><img alt="Sourcetree App" src="https://wac-cdn.atlassian.com/dam/jcr:81b15cde-be2e-4f4a-8af7-9436f4a1b431/Sourcetree-icon-blue.svg" width=100></a> | <a href="../gui-tool-tutorials/github-windows-intellij-tutorial.md"><img alt="IntelliJ IDEA" src="https://upload.wikimedia.org/wikipedia/commons/thumb/9/9c/IntelliJ_IDEA_Icon.svg/512px-IntelliJ_IDEA_Icon.svg.png" width=100></a> |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [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) |
<p>This project is supported by:</p>
<p>
+49 -13
View File
@@ -1,5 +1,4 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](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)
@@ -8,11 +7,13 @@
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.
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 atlieka savo pirmąjį indėlį. Prisiminkite: kuo labiau atsipalaidavę esate, tuo geriau mokotės. Jei norite atlikti pirmąjį indėlį, atlikite toliau pateiktus paprastus veiksmus. Mes pažadame, tai bus smagu.
_Jei nesate pratę dirbti su komandine eilute, [čia rasite vadovą, naudojantį GUI įrankius.](#tutorials-using-other-tools)_
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="fork this repository" />
Jei neturite instaliuoto git, [ instaliuokite čia ]( https://help.github.com/articles/set-up-git/).
#### Jei neturite instaliuoto git, [instaliuokite čia](https://help.github.com/articles/set-up-git/).
## Kopijuokite (fork) šią saugyklą
@@ -28,9 +29,9 @@ Dabar klonuokite šią saugyklą į savo kompiuterį. Spustelėkite klonavimo my
Atidarykite terminalą ir paleiskite šią git komandą:
```
git clone "kopijuota nuoroda"
git clone "kątik nukopijuota nuoroda"
```
kur "kopijuota nuoroda" (be citatos ženklų) yra url nuoroda jūsų saugyklai. Peržiūrėkite ankstesnius veiksmus, kad gautumėte url nuorodą.
kur "kątik nukopijuota nuoroda" (be citatos ženklų) yra url nuoroda jūsų saugyklai (jūsų projekto kopijai). Peržiūrėkite ankstesnius veiksmus, kad gautumėte url nuorodą.
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/copy-to-clipboard.png" alt="copy URL to clipboard" />
@@ -47,20 +48,35 @@ Pakeiskite kompiuterio saugyklos katalogą (jei dar to nepadarėte anksčiau):
```
cd first-contributions
```
Dabar sukurkite šaką naudodami komandą `git checkout`:
Dabar sukurkite šaką naudodami komandą `git branch`:
```
git checkout -b <add-tavo-vardas>
git branch -c <tavo-sakos-vardas>
```
Pavyzdžiui:
```
git branch -c add-vardenis-pavardenis
```
(Saugyklos pavadinime neprivalo būti žodžio *add*, bet mes jį naudojame, kadangi šios šakos (branch) paskirtis yra įtraukti savo vardą į sąrašą.)
<details>
<summary> <strong>Jei gavote klaidos pranešimą naudodami git switch, spauskite čia:</strong> </summary>
Jei klaidos pranešimas yra "Git: `switch` is not a git command. See `git help`", tikėtinai naudojate seną git versiją.
Tokiu atveju bandykite `git checkout`:
```bash
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šą.)
</details>
## 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:
Dabar atidarykite failą `Contributors.md` teksto redaktoriuje ir pridėkite prie jo savo vardą. Nedėkite jo į failo pradžią ar pabaigą - įrašykite jį bet kur kitur faile. Galiausiai, 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
```
@@ -75,9 +91,31 @@ pakeisdami `<tavo-vardas>` savo vardu.
Išsiųskite pakeitimus komanda `git push`:
```
git push origin <add-tavo-vardas>
git push origin <tavo-sakos-vardas>
```
pakeisdami `<tavo-vardas>` anskčiau sukurtos šakos (branch) vardu.
pakeisdami `<tavo-sakos-vardas>` anskčiau sukurtos šakos (branch) vardu.
<details>
<summary> <strong>Jei gaunate klaidos pranešimą išsaugodami pakeitimus, spauskite čia:</strong> </summary>
- ### Autentifikacijos klaida
<pre>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/<your-username>/first-contributions.git/'</pre>
[GitHub vadovas](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account) padės jums sugeneruoti ir sukonfiguruoti SSH raktą savo paskyroje.
Taip pat, galbūt norėsite pabandyti 'git remote -v', skirtą patikrintite savo nuotolinį adresą (remote address).
Jei jis atrodo taip ar panašiai:
<pre>origin https://github.com/your-username/your_repo.git (fetch)
origin https://github.com/your-username/your_repo.git (push)</pre>
pakeiskite jį, naudodami komandą:
```bash
git remote set-url origin git@github.com:your-username/your_repo.git
```
Kitu atveju jūsų vis tiek sulauksite klausimo apie savo vartotojo vardą ir slaptažodį ir sulauksite autentifikacijos klaidos.
</details>
## Pateikite pakeitimus peržiūrai
@@ -95,8 +133,6 @@ Netrukus projekto autorius sujungs visus jūsų šakos pakeitimus su šio projek
Džiaukitės ir atkreipkite dėmesį į savo įnašą pasidalindami šia žinia su draugais [interneto aplikacijoje](https://firstcontributions.github.io/#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://firstcontributions.github.io/#project-list).
### [ Papildoma medžiaga ](../additional-material/git_workflow_scenarios/additional-material.md)
-1
View File
@@ -1,5 +1,4 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](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)
+162
View File
@@ -0,0 +1,162 @@
[![Open Source Love](https://firstcontributions.github.io/open-source-badges/badges/open-source-v1/open-source.svg)](https://github.com/firstcontributions/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)
# First Contributions
Нээлттэй эх код баазад өөрийн хувь нэмрээ оруулах хүсэл програмч болгонд байдаг байх. Харин яг хаанаас эхлэхээ мэдэхгүй үе тохиолдох нь элбэг. Иймд, бид хэд шиг будилсан хөгжүүлэгч нарт ядаж хийх үйлдлийн зохих дарааллыг нь таниулчих зорилгоор энэхүү төсөл нь эхэлжээ. Та ч бас нээлттэй эх код баазад өөрийн нэмрээ оруулмаар байгаа бол доорх алхмуудыг дагаад хийгээрэй.
_Терминалтай ажиллах дургүй бол [GUI ашигласан хичээл рүү ороорой.](#tutorials-using-other-tools)_
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="fork this repository" />
#### Компьютер дээрээ git суулгаагүй бол [энд дарж суулгана уу.](https://docs.github.com/en/get-started/quickstart/set-up-git).
## Энэ рэпог форклох
Та энэ хуудасны дээд хэсэгт орших fork товчийг дарснаар энэ рэпоны хуулбар таны хаягт үүсэх юм.
## Энэ рэпог хувилах
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clone this repository" />
Форк хийчихсэн рэпогоо компьютер дээрээ суулгахын тулд хлээд Гитхаб хаяг дээрээ очоод, форклосон рэпогоо олоод, code гэсэн товчин даар дараад, SSH хэсэг дээр дарж, _хуулах_ товчлуур дээр дарах хэрэгтэй.
Дараа нь, терминалаа нээгээд доорх үйлдлийг хийнэ:
```bash
git clone "саяны хуулсан линк"
```
"саяны хуулсан линк" хэсгийн оронд эхний алхам дээр хуулсан линкээ наана.
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/copy-to-clipboard.png" alt="copy URL to clipboard" />
Жишээ нь:
```bash
git clone git@github.com:таны-гитхаб-хаяг/first-contributions.git
```
`таны-гитхаб-хаяг` гэсний оронд Гитхабын хэрэглэгчийн нэрээ бичнэ. Ингэснээр та өөрийн хаяг дээрээ үүсгэсэн энэхүү рэпоны хуулбарыг өөрийн компьютер дээрээ хувилан авч чадлаа.
## Шинэ бранч үүсгэх
Дараа нь, хувилсан рэпоныхоо фолдер луу шилжинэ:
```bash
cd first-contributions
```
`git switch` үйлдлийг ашиглан шинэ бранч үүсгэнэ:
```bash
git switch -c шинэ-бранчийн-нэр
```
Жишээ нь:
```bash
git switch -c add-alonzo-church
```
<details>
<summary> <strong>git switch үйлдлийг хийхэд ямар нэгэн алдаа гарсан бол энд дар:</strong> </summary>
Дараах алдаа гарсан бол Гит програмын чинь хувилбар нийцэхгүй байна гэсэн үг: "Git: `switch` is not a git command. See `git help`"
Дээрх тохиолдолд `git checkout` үйлдлийг хэрэглээд үзээрэй:
```bash
git checkout -b шинэ-бранчийн-нэр
```
</details>
## Код баазад өөрчлөлт хийгээд өөрчлөлтөө коммит хийх
`Contributors.md` файлыг дурын текст эдитор дээр нээгээд өөрийн нэрээ нэмээрэй. Файлын эхэнд болон сүүлд нэмэхгүй л байхад болно.
<img align="right" width="450" src="https://firstcontributions.github.io/assets/Readme/git-status.png" alt="git status" />
Дараа нь, үндсэн фолдер луу шилжээд `git status` үйдлийг хийвэл танд таны өөрчилсөн файлууд харагдана.
Харагдаж буй өөрчлөлтүүдээ эхлээд бранчдаа `git add` үйлдлийг ашиглан нэмнэ:
```bash
git add Contributors.md
```
Дараа нь `git commit` үйлдлийг ашиглан коммит хийнэ (`your-name` гэснийг нэмсэн нэрээрээ солихоо мартуузай):
```bash
git commit -m "Add your-name to Contributors list"
```
## Гитхаб руу пушлэх
Дараа нь, `git push` үйлдлийг ашиглан саяны коммитоо пушлэнэ (`your-branch-name` гэснийг үүсгэсэн бранчийнхаа нэрээр солихоо мартуузай):
```bash
git push -u origin your-branch-name
```
<details>
<summary> <strong>Пушлэх үйлдэл дээр ямар нэгэн алдаа заавал энд дарж харах:</strong> </summary>
- ### Нэвтрэх эрхийн алдаа
<pre>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/<your-username>/first-contributions.git/'</pre>
Хэрэв дээрх янзаар алдаа зааж байвал шинэ SSH түлхүүр үүсгэн хаягтайгаа холбох хэрэгтэй гэсэн үг бөгөөд хэрхэн холбохыг [энд дарж харна уу](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account).
Мөн, аль рэпотой холбогдсон байгаагаа 'git remote -v' үйлдлээр шалгачихад гэмгүй.
Хэрэв дээрх үйлдлийн хариу доорх маягаар байвал:
<pre>origin https://github.com/таны-хэрэглэгчийн-нэр/таны-рэпо-нэр.git (fetch)
origin https://github.com/таны-хэрэглэгчийн-нэр/таны-рэпо-нэр.git (push)</pre>
дараах үйлдлээр өөрчлөх хэрэгтэй:
```bash
git remote set-url origin git@github.com:таны-хэрэглэгчийн-нэр/таны-рэпо-нэр.git
```
Ингэснээр та нууц үгээр биш хаягтай чинь холбогдсон SSH түлхүүрээр нэвтэрч эхэлнэ.
</details>
## Нэгтгэх хүсэлт илгээх
Гитхаб дээрх рэпо руу очмогц `Compare & pull request` товчлуур харагдах болно. Уг товчлуур дээр дарснаар шинэ нэгтгэх хүсэлт (pull request) үүсгэх хуудас гарч ирнэ.
<img style="float: right;" src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="create a pull request" />
Дараа нь нэгтгэх хүсэлтээ илгээнэ.
<img style="float: right;" src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="submit pull request" />
Таны хүсэлтийг бид хүлээн аваад автоматаар код бааздаа нэгтгэсэн байх болно. Энэ талаар бүртгэлтэй и-мейл хаяг дээр чинь мэдэгдэл ирнэ.
## Одоо яг яах билээ?
Нээлттэй эх код баазад өөрийн нэмрээ оруулахын тулд ерөнхийд нь мөрдөх ёстой _fork -> clone -> edit -> pull request_ гэсэн дарааллыг та одоо мэддэг боллоо.
Нээлттэй эхэд нэмэр оруулж эхлэх анхны алхамаа хийсэн талаараа [энд дарж](https://firstcontributions.github.io/#social-share) нөхөдтэйгөө хуваалцана уу.
Өшөө дасгал ажиллахын тулд [энд дар](https://github.com/roshanjossey/code-contributions).
Нээлттэй эх код баазтай янз бүрийн төслүүдийн жагсаалтыг [энд дарж харна уу](https://firstcontributions.github.io/#project-list).
### [Нэмэлт материал](docs/additional-material/git_workflow_scenarios/additional-material.md)
## Өөр програмууд ашигласан хичээлүүд
| <a href="docs/gui-tool-tutorials/github-desktop-tutorial.md"><img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="100"></a> | <a href="docs/gui-tool-tutorials/github-windows-vs2017-tutorial.md"><img alt="Visual Studio 2017" src="https://upload.wikimedia.org/wikipedia/commons/c/cd/Visual_Studio_2017_Logo.svg" width="100"></a> | <a href="docs/gui-tool-tutorials/gitkraken-tutorial.md"><img alt="GitKraken" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-icon.png" width="100"></a> | <a href="docs/gui-tool-tutorials/github-windows-vs-code-tutorial.md"><img alt="VS Code" src="https://upload.wikimedia.org/wikipedia/commons/1/1c/Visual_Studio_Code_1.35_icon.png" width=100></a> | <a href="docs/gui-tool-tutorials/sourcetree-macos-tutorial.md"><img alt="Sourcetree App" src="https://wac-cdn.atlassian.com/dam/jcr:81b15cde-be2e-4f4a-8af7-9436f4a1b431/Sourcetree-icon-blue.svg" width=100></a> | <a href="docs/gui-tool-tutorials/github-windows-intellij-tutorial.md"><img alt="IntelliJ IDEA" src="https://upload.wikimedia.org/wikipedia/commons/thumb/9/9c/IntelliJ_IDEA_Icon.svg/512px-IntelliJ_IDEA_Icon.svg.png" width=100></a> |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [GitHub Desktop](docs/gui-tool-tutorials/github-desktop-tutorial.md) | [Visual Studio 2017](docs/gui-tool-tutorials/github-windows-vs2017-tutorial.md) | [GitKraken](docs/gui-tool-tutorials/gitkraken-tutorial.md) | [Visual Studio Code](docs/gui-tool-tutorials/github-windows-vs-code-tutorial.md) | [Atlassian Sourcetree](docs/gui-tool-tutorials/sourcetree-macos-tutorial.md) | [IntelliJ IDEA](docs/gui-tool-tutorials/github-windows-intellij-tutorial.md) |
<p>Энэ төслийг дэмжсэн:</p>
<p>
<a href="https://www.digitalocean.com/">
<img src="https://opensource.nyc3.cdn.digitaloceanspaces.com/attribution/assets/SVG/DO_Logo_horizontal_blue.svg" width="201px">
</a>
</p>
-1
View File
@@ -1,5 +1,4 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](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)
+1 -2
View File
@@ -1,5 +1,4 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](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)
# ਪਹਿਲਾ ਯੋਗਦਾਨ
@@ -104,7 +103,7 @@ git push origin <add-your-branch-name>
ਆਪਣੇ ਯੋਗਦਾਨ ਦਾ ਜਸ਼ਨ ਮਨਾਓ ਅਤੇ ਜਾ ਕੇ ਇਸ ਨੂੰ ਆਪਣੇ ਦੋਸਤਾਂ ਅਤੇ ਪੈਰੋਕਾਰਾਂ ਨਾਲ ਸਾਂਝਾ ਕਰੋ। [ਵੈੱਬ ਐਪ](https://firstcontributions.github.io/#social-share).
ਤੁਹਾਨੂੰ ਸਾਡੀ ਸਲੈਕ ਟੀਮ ਵਿਚ ਸ਼ਾਮਲ ਹੋ ਸਕਦਾ ਹੈ ਜੇ ਤੁਹਾਨੂੰ ਕਿਸੇ ਮਦਦ ਦੀ ਜ਼ਰੂਰਤ ਹੈ ਜਾਂ ਕੋਈ ਪ੍ਰਸ਼ਨ ਹੈ। [ਟੀਮ ਵਿਚ ਸ਼ਾਮਲ ਹੋ](https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA).
ਜੇਕਰ ਤੁਸੀਂ ਹੋਰ ਅਭਿਆਸ ਚਾਹੁੰਦੇ ਹੋ, ਤਾਂ [ਕੋਡ ਯੋਗਦਾਨਾਂ](https://github.com/roshanjossey/code-contributions) ਨੂੰ ਚੈੱਕਆਉਟ ਕਰੋ।
ਆਓ ਹੁਣ ਤੁਹਾਨੂੰ ਹੋਰ ਪ੍ਰੋਜੈਕਟਾਂ ਵਿੱਚ ਯੋਗਦਾਨ ਪਾਉਣ ਲਈ ਸ਼ੁਰੂਆਤ ਕਰੀਏ. ਅਸੀਂ ਪ੍ਰੋਜੈਕਟਾਂ ਦੀ ਇੱਕ ਸੂਚੀ ਤਿਆਰ ਕੀਤੀ ਹੈ ਜਿਸ ਨਾਲ ਤੁਸੀਂ ਅਸਾਨ ਮੁੱਦਿਆਂ ਨੂੰ ਸ਼ੁਰੂ ਕਰ ਸਕਦੇ ਹੋ। [ਪ੍ਰੋਜੈਕਟਾਂ ਦੀ ਸੂਚੀ](https://firstcontributions.github.io/#project-list).
+99 -93
View File
@@ -1,142 +1,148 @@
<div dir="rtl">
<a href="https://github.com/ellerbrock/open-source-badges/"><img src="https://badges.frapsoft.com/os/v1/open-source.svg?v=103" alt="Open Source Love"></a><a href="https://opensource.org/licenses/MIT"><img src="https://img.shields.io/badge/License-MIT-green.svg"></a><a href="https://www.codetriage.com/roshanjossey/first-contributions" rel="nofollow"> <img src="https://camo.githubusercontent.com/8e53aecabdd0316ce198fe932798bb0f8754b30f/68747470733a2f2f7777772e636f64657472696167652e636f6d2f726f7368616e6a6f737365792f66697273742d636f6e747269627574696f6e732f6261646765732f75736572732e737667" alt="Open Source Helpers"></a><a href="https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA"> <img align="left" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png"></a>
</div>
<div dir="rtl" lang="ps">
#<div dir="rtl">لومړی ګډون <div dir="rtl">
***
<div dir="rtl">
د دې پروژې موخه دا ده ترڅو نویو پېل کوونکو ته په خلاصو سرچینو پروژو (Open Source Projects) کې د ګډون لاره وښئ که چېرې تاسو غواړی خپل لومړی ګډون پیل کړئ لاندې قدمونه پر مخ یوسئ.
<a href="https://github.com/ellerbrock/open-source-badges/">
<img src="https://badges.frapsoft.com/os/v1/open-source.svg?v=103" alt="Open Source Love" />
</a>
<a href="https://opensource.org/licenses/MIT">
<img src="https://img.shields.io/badge/License-MIT-green.svg" alt="MIT License" />
</a>
<a href="https://www.codetriage.com/roshanjossey/first-contributions">
<img src="https://www.codetriage.com/roshanjossey/first-contributions/badges/users.svg" alt="Open Source Helpers" />
</a>
<a href="https://join.slack.com/t/firstcontributors/shared_invite/zt-1hg51qkgm-Xc7HxhsiPYNN3ofX2_I8FA">
<img align="left" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png" alt="Join Slack Team" />
</a>
که د کمانډ لاین سره راحت نه یاست [ کولای شی تصویر بڼه دلته پرمخ یوسئ](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
---
<b>که چېرې مو git نه وي انسټال کړی [له دغه ځایه یې درښکته او انسټال یې کړئ](https://help.github.com/articles/set-up-git/) </b>
## لومړی ګډون
</div>
**د دې پروژې هدف دا دی چې نویو ګډونوالو ته په خلاصو سرچینو پروژو (Open Source Projects) کې د ګډون اسانه طریقه وښيي.**
که غواړئ خپله لومړنۍ مرسته وکړئ، لاندې ګامونه تعقیب کړئ.
**که د کمانډ لاین (CLI) سره راحت نه یاست،**
[کولی شئ تصویري لارښود دلته وګورئ](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
**که مو Git انسټال نه وي،**
[له دې ځایه یې ښکته او نصب کړئ](https://help.github.com/articles/set-up-git/).
## دا ذخیره (repository) فورک کړئ
<img align="left" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="fork this repository" />
###<div dir="rtl">دا ذخیره (repository) فورک کړئ:</div>
***
<p align="right" dir="rtl">
د دې پاڼې په سر کې د فورک تڼئ پر کلیک سره تاسو کولای شئ دا repository فورک کړئ، فورک به د دې repository یوه کاپي ستاسو د کیټ هب په اکونټ کې جوړه کړي.
</p>
- د دې پاڼې په سر کې د Fork تڼۍ کلیک کړئ.
- فورک کول به د دې ذخیرې یوه کاپي ستاسو د GitHub اکاونټ ته انتقال کړي.
<br clear="all"/>
## دا ذخیره (repository) کلون کړئ
###<div dir="rtl">دا ذخیره (repository) کلون کړئ:</div>
***
<img align="left" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clone this repository" />
<p align="right" dir="rtl">اوس فورک کړل شوې ریپوزیټوري کلون یعنې ښکته کړئ د دې کار د ترسره کولو لپاره خپل اکونټ ته لاړ شی د کوډ پر تڼۍ کلیک وکړئ او د ریپوزیټوري لینک کاپي کړئ.</p>
- خپل اکاونټ ته لاړ شئ او د فورک شوې ذخیرې لینک د **Code** تڼۍ څخه کاپي کړئ.
<p align="right" dir="rtl">ترمینل یا CMD خلاص کړئ او لاندې د کیټ کمنډ رن کړئ</p>
```git
git clone "د ریپوزیټوري کاپي کړل شوی لینک"
```
<p align="right" dir="rtl">د بیلکې په توګه</p>
<br clear="all"/>
```git
git clone https://github.com/MasihKarimi/first-contributions.git
```
<p align="right" dir="rtl">په پورته لینک کې د MasihKarimi پرځای باید ستاسو د کیټ هب د اکونټ نوم وي</p>
- ترمینل یا CMD خلاص کړئ او دا کمانډ اجرا کړئ:
<p align="right" dir="rtl">د پورته قدمونو په اخیستلو سره تاسو د “first-contributions” ذخیره یا ریپوزیټوري خپل کمپیوټر ته ښکته کوۍ.</p>
###<div dir="rtl">نوې څانګه یا برانچ جوړ کړئ:</div>
***
<p align="right" dir="rtl">‌اوس د first-contributions پروژه په خپل کوډ ایډیټر کې پرانيزی او په ترمینل کې د لاندې کیټ کمنډ په رن کولو سره نوی برانچ یا څانګه جوړه کړئ.</p>
```git
git switch -c د څانګې نوم
```
<p align="right" dir="rtl">د بیلکې په توګه</p>
```git
git switch -c add-Masih-Karimi
```bash
git clone https://github.com/YourUsername/first-contributions.git
```
<p align="right" dir="rtl">add-Masih-Karimi زما د څانګې نوم دی تاسو کولائ شئ خپل نوم غوره کړئ</p>
**یادونه:** دلته `YourUsername` باید ستاسو د GitHub اکاونټ نوم وي.
###<div dir="rtl">اړین بدلونونه راوړئ او دا بدلونونه ترسره یا commit کړئ:</div>
***
## نوې څانګه (branch) جوړ کړئ
<p align="right" dir="rtl">اوس د contributors.md فایل راخلاص کړئ او خپل نوم مو وراضافه کړئ نوم مو د فایل په شروغ یا اخر کې مه اضافه کوئ په منځ کې یې اضافه کړئ او فایل ذخیره کړئ</p>
- د first-contribution پروژه په خپل کوډ ایډیټر کې خلاصه کړئ.
- ترمینل کې دا کمانډ اجرا کړئ ترڅو نوې څانګه جوړه کړئ. ددې لپاره چې زمونږ د بدلونونو لپاره خپله څانګه وي او له نورو سره شریکه نشي. دې څانګې کې به مونږ ایډیټ کوو او بیا به یې له عمومي څانګې سره یوځای کوو.
```bash
git switch -c your-branch-name
```
your-branch-name ستاسو د څانګې نوم دی. کولای شئ چې هر نوم تاسې ټاکلی شئ.
## اړین بدلونونه راوړئ او commit کړئ
- د `Contributors.md` فایل خلاص کړئ او خپل نوم پکې اضافه کړئ کې).
- فایل ذخیره کړئ.
<img align="left" width="450" src="https://firstcontributions.github.io/assets/Readme/git-status.png" alt="git status" />
<p align="right" dir="rtl">اوس که چېرې ټرمینل ته ولاړ شئ او د git status کمنډ رن کړئ تاسو کولائ شئ وګورئ چې په کوم فایل کې مو بدلونونه راوستي دي</p>
<p align="right" dir="rtl">په دې برخه کې د git add کمنډ په مرسته خپل بدلونونه خپل نوي جوړې کړل شوې څانګې ته اضافه کړئ:</p>
- ترمینل ته لاړ شئ او دا کمانډ اجرا کړئ ترڅو وګورئ کوم فایلونه مو بدل کړي دي:
```git
git add contributors.md
```bash
git status
```
<p align="right" dir="rtl">اوس اضافه کړل شوي بدلونونه د لاندې کمنډ په مرسته ترسره یا commit کړئ:</p>
```git
git commit -m “Add Masih Karimi to Contributors List”
- بدلونونه ذخیره کړئ:
```bash
git add Contributors.md
```
<p align="right" dir="rtl">د Masih Karimi پر ځای مو خپل نوم ولیکئ</p>
###<div dir="rtl">بدلونونه کیټ هب ته پورته یا push کړئ:</div>
***
<p align="right" dir="rtl"> په دې برخه کې د git push کمنډ په مرسته خپل بدلونونه کیټ هب ته پورته کړئ </p>
<p align="right" dir="rtl"> د بېلګې په توګه </p>
- اوس مو بدلونونه کمټ Commit کړئ:
```git
git push origin -u add-Masih-Karimi
```bash
git commit -m "message"
```
<p align="right" dir="rtl">هېر نه کړئ چې د add-Masih-Karimi پر ځای د خپلې څانګې نوم ورکړئ</p>
د مسیج پر ځای تاسې هر څه لیکلی شئ. بهتره دا ده چې تاسې په دې ځای کې ولیکئ چې کوم بدلونونه مو پروژې کې راوستل.
## بدلونونه GitHub ته push کړئ
- خپل بدلونونه کیټ هب ته پورته کړئ:
```bash
git push origin -u your-branch-name
```
د your-branch-name پر ځای باید تاسې په دقیق ډول سره د خپلې څانګې نوم ورکړئ. هغه نوم چې لږ مخکې مو انتخاب کړی وه.
<details align="right" dir="rtl">
<summary> <strong>که چېرې په دې لړ کې د کومې ستونزې سره مخ شوئ دا ځاې کېکاږئ</strong> </summary>
<summary><strong>که چېرې په دې لړ کې د کومې ستونزې سره مخ شوئ دا ځای کېکاږئ</strong></summary>
- ### د تصدیق کولو تېروتنه
<pre>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/<your-username>/first-contributions.git/'</pre>
[په دې کیټ هب ښونه کې زده کړئ چې څنګه پورته ستونزه حل کړئ](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
که چېرته ستاسې ستونزه داسي وي.
<div dir="ltr">
<pre>
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/&lt;your-username&gt;/first-contributions.git/
</pre>
<div>
[نو بیا دلته زده کړئ چې دا ستونزه څنګه حل کړئ](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
</details>
## خپل بدلونونه د بیاکتنې لپاره وسپارئ
- خپل GitHub اکاونټ کې دې ریپوزیټوري ته لاړ شئ.
- د **Compare & pull request** تڼۍ به ووینئ. پر هغې کلیک وکړئ.
###<div dir="rtl">خپل بدلونونه د بیاکتنې لپاره وسپارئ</div>
***
<p align="right" dir="rtl"> اوس که چېرې دې ریپوزیټوري ته په خپل کیټ هب اکونټ کې ورشئ تاسو به یو یوه تنۍ د Compare & pull request متن سره ووینۍ. دا تنۍ کیکاږئ</p>
<img style="float: right;" src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="create a pull request" />
<p align="right" dir="rtl">اوس د pull غوښتنه وسپارئ</p>
- اوس د pull request غوښتنه وسپارئ.
<img style="float: right;" src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="submit pull request" />
<p align="right" dir="rtl">له دې ورسته به زه ستاسو راوستي بدلونه د اصلي یا main څانګې سره یوځای کړم او ستاسو نوم به د ګډون کوونکو لیست ته اضافه کړل شي.</p>
- له دې وروسته به ستاسو بدلونه د اصلي یا main څانګې سره یوځای شي او ستاسو نوم به د ګډون کوونکو لیست ته اضافه کړل شي.
###<div dir="rtl">له دې ځایه وروسته چېرته ولاړ شئ:</div>
***
<p align="right" dir="rtl"></p>
<p align="right" dir="rtl">
<b>بریا!! </b>!! تاسو په بریالیتوب سره د فورک، کلون ، ایډټ او پول غوښتنې چارې ترسره کړې ، د دې چارو سره به مو د یو ګډون کوونکي په توګه همیش سر او کار وي.
</p>
## له دې وروسته څه وکړئ؟
<p align="right" dir="rtl">
خپل لومړئ ګډون مو ولمانځئ او له خپلو ملګرو سره یې <a href="https://firstcontributions.github.io/#social-share"> شریک کړئ</a>
تاسو په بریالیتوب سره د فورک، کلون، ایډیټ، او pull request مرحلې بشپړې کړې. تاسې له دې نه وروسته کولی شئ چې په خلاص-سرچېنه پروژو کې په همدې طریقه برخه واخلئ.
</p>
- خپل لومړئ ګډون ولمانځئ او له خپلو ملګرو سره یې [شریک کړئ](https://firstcontributions.github.io/#social-share).
- که کومه ستونزه یا پوښتنه لرئ، کولای شئ زموږ د Slack ټیم سره یوځای شئ.
- اوس کولای شئ په نورو پروژو کې هم ګډون وکړئ. [دلته د پروژو لیست وګورئ](https://firstcontributions.github.io/#project-list).
<p align="right" dir="rtl">که چېرې کومه ستونزه او پوښتنه لرئ کولائ شئ زموږ د سلک slack ټیم سره یوځائ شئ</p>
## <a href="additional-material/git_workflow_scenarios/additional-material.md">اضافي مواد</a>
<p align="right" dir="rtl">
اوس راځئ په نورو پروژو کې ګډون وکړئ موږ د هغو پروژو لیست جمتو کړئ دئ چې تاسو کولائ شئ په آسانی ګډون پکې وکړئ <a href="https://firstcontributions.github.io/#project-list"> د پروژو لیست دلته وګورئ</a>
</p>
###<div align="right" dir="rtl"> <a align="right" dir="rtl" href="additional-material/git_workflow_scenarios/additional-material.md">اضافي مواد</a>
</div>
###<div align="right" dir="rtl"> د نورو وسیلو په کارولو سره درسونه</div>
***
## د نورو وسیلو په کارولو سره درسونه
| <a href="gui-tool-tutorials/github-desktop-tutorial.md"><img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="100"></a> | <a href="gui-tool-tutorials/github-windows-vs2017-tutorial.md"><img alt="Visual Studio 2017" src="https://upload.wikimedia.org/wikipedia/commons/c/cd/Visual_Studio_2017_Logo.svg" width="100"></a> | <a href="gui-tool-tutorials/gitkraken-tutorial.md"><img alt="GitKraken" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-icon.png" width="100"></a> | <a href="gui-tool-tutorials/github-windows-vs-code-tutorial.md"><img alt="VS Code" src="https://upload.wikimedia.org/wikipedia/commons/1/1c/Visual_Studio_Code_1.35_icon.png" width=100></a> | <a href="gui-tool-tutorials/sourcetree-macos-tutorial.md"><img alt="Sourcetree App" src="https://wac-cdn.atlassian.com/dam/jcr:81b15cde-be2e-4f4a-8af7-9436f4a1b431/Sourcetree-icon-blue.svg" width=100></a> | <a href="gui-tool-tutorials/github-windows-intellij-tutorial.md"><img alt="IntelliJ IDEA" src="https://upload.wikimedia.org/wikipedia/commons/thumb/9/9c/IntelliJ_IDEA_Icon.svg/512px-IntelliJ_IDEA_Icon.svg.png" width=100></a> |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [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) |
</div>
-107
View File
@@ -1,107 +0,0 @@
[![Open Source Love](https://firstcontributions.github.io/open-source-badges/badges/open-source-v1/open-source.svg)](https://github.com/firstcontributions/open-source-badges)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](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)
<p align="right">
# لومړنۍ مرستې
د دې پروژې موخه دا ده چې د پیل کونکو لپاره د دوی لومړنۍ مرسته کولو لاره ساده او لارښود کړي. که تاسو د خپلې لومړۍ مرستې په لټه کې یاست، لاندې مرحلې تعقیب کړئ.
_که تاسو د کمانډ لاین (CLI) سره راحته نه یاست ، [دا لارښوونې وکاروئ ترڅو پوه شئ چې د GUI وسیلو کارولو څرنګوالی](#د-نورو-وسیلو-کارولو-لارښوونې)._
<img align="left" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="fork this repository" />
#### که تاسو git نصب نلرئ [له دې ځایه نصب کړئ](https://help.github.com/articles/set-up-git/).
## د دې ریپوزیتوری فورک کړئ
د دې پاڼې په سر کې د Fork تڼۍ په کلیک کولو سره دا ذخیره فورک کړئ.
دا به ستاسو په حساب کې د دې ذخیره کاپي رامینځته کړي.
## فورک شوی ریپازیتوری کلون Clone کړئ
<img align="left" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clone this repository" />
اوس خپل ماشین ته د فورک شوي ذخیره کلون کړئ. خپل GitHub حساب ته لاړ شئ، د فورک شوي ریپازیتوری خلاص کړئ، د Code تڼۍ باندې کلیک وکړئ او بیا د کلپ بورډ ته د Copy To Clipboard باندې کلیک وکړئ.
بیا یو ټرمینل خلاص کړئ او لاندې کمانډ چل کړئ:
```
git clone "url you just copied"
```
چیرته چې "url you just copied" (پرته د نرخ نښه) د دې ریپازیتوری url دی (ستاسو د دې پروژې فورک). د url ترلاسه کولو لپاره مخکیني ګامونه وګورئ.
<img align="left" width="300" src="https://firstcontributions.github.io/assets/Readme/copy-to-clipboard.png" alt="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` فایل په متن ایډیټر کې خلاص کړئ، خپل نوم پکې اضافه کړئ. دا د فایل په پیل یا پای کې مه اضافه کړئ. په منځ کې هر ځای کېږدئ. اوس، فایل ذخیره کړئ.
<img align="left" width="450" src="https://firstcontributions.github.io/assets/Readme/git-status.png" alt="git status" />
که تاسو د پروژې موقعیت ته لاړ شئ او د `git status` کمانډ اجرا کړئ ، نو تاسو به وګورئ چې بدلونونه شتون لري.
د `git add` کمانډ په کارولو سره دا بدلونونه په هغه څانګه کې اضافه کړئ چې تاسو یې رامینځته کړی:
```
git add Contributors.md
```
اوس دا بدلونونه د `git commit` کمانډ په کارولو سره ترسره کړئ:
```
git commit -m "Add <your-name> to Contributors list"
```
<your-name> د خپل نوم سره بدل کړئ.
## GitHub ته بدلونونه فشار (Push) وکړئ
د 'git push' کمانډ په کارولو سره خپل بدلونونه فشار (Push) وکړئ:
```
git push origin <add-your-branch-name>
```
د `your-branch-name` بدلول د هغه څانګې نوم سره چې تاسو مخکې جوړ کړی:
## خپل بدلونونه د بیاکتنې لپاره وسپارئ
که تاسو په GitHub کې خپل ریپازیتوری ته لاړ شئ، نو تاسو به د `Compare & pull request` تڼۍ وګورئ. په هغه تڼۍ کلیک وکړئ.
<img style="float: left;" src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="create a pull request" />
اوس د پلولو غوښتنه (Pull Request) وسپارئ.
<img style="float: left;" src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="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)
## د-نورو-وسیلو-کارولو-لارښوونې
| <a href="gui-tool-tutorials/github-desktop-tutorial.md"><img alt="GitHub Desktop" src="https://desktop.github.com/images/desktop-icon.svg" width="100"></a> | <a href="gui-tool-tutorials/github-windows-vs2017-tutorial.md"><img alt="Visual Studio 2017" src="https://upload.wikimedia.org/wikipedia/commons/c/cd/Visual_Studio_2017_Logo.svg" width="100"></a> | <a href="gui-tool-tutorials/gitkraken-tutorial.md"><img alt="GitKraken" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/gitkraken-tutorial/gk-icon.png" width="100"></a> | <a href="gui-tool-tutorials/github-windows-vs-code-tutorial.md"><img alt="VS Code" src="https://upload.wikimedia.org/wikipedia/commons/1/1c/Visual_Studio_Code_1.35_icon.png" width=100></a> | <a href="gui-tool-tutorials/sourcetree-macos-tutorial.md"><img alt="Sourcetree App" src="https://wac-cdn.atlassian.com/dam/jcr:81b15cde-be2e-4f4a-8af7-9436f4a1b431/Sourcetree-icon-blue.svg" width=100></a> | <a href="gui-tool-tutorials/github-windows-intellij-tutorial.md"><img alt="IntelliJ IDEA" src="https://upload.wikimedia.org/wikipedia/commons/thumb/9/9c/IntelliJ_IDEA_Icon.svg/512px-IntelliJ_IDEA_Icon.svg.png" width=100></a> |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [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) |
| | | | | | |
</p>
+1 -1
View File
@@ -163,7 +163,7 @@ git push origin --delete <add-your-name>
Ниже несколько популярных репозиториев, где вы можете найти задания для новичков. Вперёд, перейдите в репозитории, чтобы узнать больше.
| [![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) | [<img width="100" src="https://upload.wikimedia.org/wikipedia/commons/a/a7/React-icon.svg">](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) | [<img width="100" src="https://camo.githubusercontent.com/0f302c808c8457f6460913e33aed3478124612c2/687474703a2f2f6c65696e696e67656e2e6f72672f696d672f6c65696e696e67656e2e6a7067">](https://github.com/technomancy/leiningen/issues?q=is%3Aopen+is%3Aissue+label%3ANewbie) | [<img width="100" src="https://images.plot.ly/plotly-documentation/thumbnail/numpy-logo.jpg">](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://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) | [<img width="100" src="https://upload.wikimedia.org/wikipedia/commons/a/a7/React-icon.svg">](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) | [<img width="100" src="https://leiningen.org/img/leiningen.jpg">](https://github.com/technomancy/leiningen/issues?q=is%3Aopen+is%3Aissue+label%3ANewbie)(https://github.com/technomancy/leiningen/issues?q=is%3Aopen+is%3Aissue+label%3ANewbie) | [<img width="100" src="https://images.plot.ly/plotly-documentation/thumbnail/numpy-logo.jpg">](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) |
+2 -3
View File
@@ -1,5 +1,4 @@
[![Open Source Love](https://firstcontributions.github.io/open-source-badges/badges/open-source-v1/open-source.svg)](https://github.com/firstcontributions/open-source-badges)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](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)
@@ -78,7 +77,7 @@ git checkout -b உங்கள்-கிளையின்-பெயர்
## தேவையான மாற்றங்களைச் செய்து அந்த மாற்றங்களை commit செய்யுங்கள்
இப்போது *text editor* அல்லது *notepad* இல் `Contribitors.md` கோப்பைத் திறந்து, அதில் உங்கள் பெயரைச் சேர்க்கவும். கோப்பின் தொடக்கத்திலோ அல்லது முடிவிலோ இதைச் சேர்க்க வேண்டாம். இடையில் எங்கும் வைக்கவும். இப்போது, ​​கோப்பை சேமிக்கவும்.
இப்போது *text editor* அல்லது *notepad* இல் `Contributors.md` கோப்பைத் திறந்து, அதில் உங்கள் பெயரைச் சேர்க்கவும். கோப்பின் தொடக்கத்திலோ அல்லது முடிவிலோ இதைச் சேர்க்க வேண்டாம். இடையில் எங்கும் வைக்கவும். இப்போது, ​​கோப்பை சேமிக்கவும்.
<img align="right" width="450" src="https://firstcontributions.github.io/assets/Readme/git-status.png" alt="git status" />
@@ -141,7 +140,7 @@ GitHub இல் உள்ள உங்கள் களஞ்சியத்த
உங்கள் பங்களிப்பைக் கொண்டாடுங்கள் மற்றும் உங்கள் நண்பர்கள் மற்றும் பின்தொடர்பவர்களுடன் [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)..
உங்களுக்கு மேலும் பயிற்சி தேவைப்பட்டால், [code contributions](https://github.com/roshanjossey/code-contributions) என்னும் செயலை சரிபார்க்கலாம்.
இப்போது மற்ற திட்டங்களுக்கு பங்களிப்பதன் மூலம் தொடங்குவோம். நீங்கள் தொடங்கக்கூடிய எளிதான சிக்கல்களுடன் திட்டங்களின் பட்டியலை நாங்கள் தொகுத்துள்ளோம். பாருங்கள் [the list of projects in the web app](https://firstcontributions.github.io/#project-list).
+7 -19
View File
@@ -1,38 +1,26 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](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 సాధనాలను ఉపయోగించి ట్యుటోరియల్స్ ఉన్నాయి.](#ఇతర-సాధనాలను-ఉపయోగించి-ట్యుటోరియల్స్)*
మొదటిసారి ఓపెన్ సోర్స్ కొరకు సహకరించాలి అనుకునే ప్రారంభకులకు పద్దతులను సులభతరం చేయడం ఈ ప్రాజెక్ట్ **ముఖ్య ఉద్దేశం**
మీరు మొదటిసారి ఒపెన్ సోర్స్ ప్రాజెక్ట్ లకొరకు కాంట్రిబ్యూట్ చేయాలి అనుకుంటే కింది సూచనలు పాటించండి.
మీరు `గిట్(git)`వర్షన్ కట్రోల్ సిస్టమ్ తో సౌకర్యవంతంగా లేకపోతే [ఇక్కడ GUI సాధనాలను ఉపయోగించి ట్యుటోరియల్స్ ఉన్నాయి.](#ఇతర-సాధనాలను-ఉపయోగించి-ట్యుటోరియల్స్)*
#### *మీకు కమాండ్ లైన్‌తో సౌకర్యంగా లేకపోతే, [ఇక్కడ GUI సాధనాలను ఉపయోగించి ట్యుటోరియల్స్ ఉన్నాయి.](#ఇతర-సాధనాలను-ఉపయోగించి-ట్యుటోరియల్స్)*
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="fork this repository" />
మీ కంప్యూటర్ లో `GIT` లేకపోతే, [గిట్ వర్షన్ కంట్రోల్ సిస్టమ్ ను ఇన్స్టాల్ చేయండి](https://help.github.com/articles/set-up-git/).
#### మీ కంప్యూటర్లో git లేకపోతే, [దాన్ని ఇన్స్టాల్ చేయండి](https://docs.github.com/en/get-started/quickstart/set-up-git).
## ఈ రిపోజిటరీని ఫోర్క్ చెయ్యండి
## ఈ రిపోజిటరీని ఫోర్క్ చయండి
ఈ రిపోజిటరీని ఫోర్క్ చెయ్యండి ఈ పేజీ ఎగువ భాగంలో ఫోర్క్ బటన్ పై క్లిక్ చేయడం ద్వారా క్లిక్ చేయండి.
ఈ రిపోజిటరీని ఫోర్క్ చయండి ఈ పేజీ ఎగువ భాగంలో ఫోర్క్ బటన్పై క్లిక్ చేయడం ద్వారా.
ఇది మీ ఖాతాలో ఈ రిపోజిటరీ కాపీని సృష్టిస్తుంది.
## రిపోజిటరీని క్లోన్ చెయ్యండి
## రిపోజిటరీని క్లోన్ చయండి
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clone this repository" />
File diff suppressed because one or more lines are too long
+2 -2
View File
@@ -5,7 +5,7 @@
# İlk katkı
Zor gelir... Herhangi bir işi ilk kez yapmak daima zor gelir. Özellikle başkalarıyla ortak çalışıyorsanız, hata yapmak içinize sinmez. Ancak "Açık Kaynakın" temelinde işbirliği ve birlikte çalışma yatmakta. Biz, açık kaynak projelere ilk kez katkıda bulunacak kişilerin bu süreci öğrenmesini ve ilk katkılarını sunmalarını kolaylaştırmayı istiyoruz.
Zor gelir... Herhangi bir işi ilk kez yapmak daima zor gelir. Özellikle başkalarıyla ortak çalışıyorsanız, hata yapmak içinize sinmez. Ancak "Açık Kaynağın" temelinde işbirliği ve birlikte çalışma yatmakta. Biz, açık kaynak projelere ilk kez katkıda bulunacak kişilerin bu süreci öğrenmesini ve ilk katkılarını sunmalarını kolaylaştırmayı 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ı takip etmeniz yeterli olacaktır. Söz veriyoruz, eğlenceli olacak.
@@ -13,7 +13,7 @@ Makale okumak ve eğitim videoları izlemek yardımcı olabilir, fakat bir işi
Eğer bilgisayarınızda git kurulu değil ise, [ yükleyin ]( https://help.github.com/articles/set-up-git/ ).
## Projeyi "çatallama"
## Projeyi "forklama"
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.
-3
View File
@@ -1,5 +1,4 @@
[![Open Source Love](https://firstcontributions.github.io/open-source-badges/badges/open-source-v1/open-source.svg)](https://github.com/firstcontributions/open-source-badges)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](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)
@@ -118,8 +117,6 @@ git push -г origin <your-branch-name>
Відзначте свій внесок і поділіться ним із друзями та читачами, перейшовши до [веб-програми](https://firstcontributions.github.io/#social-share).
Ви можете приєднатися до нашої команди Slack, якщо вам потрібна допомога або якщо виникнуть запитання. [Приєднайтеся до команди Slack](https://firstcontributors.slack.com/join/shared_invite/zt-29qhyr9lt-Bi7WLbgGIFqV7aCEG_grvg#/shared-invite/email).
Тепер давайте почнемо робити внески в інші проекти. Ми склали список проектів із простими проблемами, з яких ви можете почати. Перегляньте [список проектів у веб-додатку](https://firstcontributions.github.io/#project-list).
### [Додаткові матеріали](additional-material/git_workflow_scenarios/additional-material.md)
-1
View File
@@ -125,7 +125,6 @@ Tabriklayman! Siz hozirgina contributor sifatida tez-tez uchraydigan standard is
Hissangizni nishonlang va [web app](https://firstcontributions.github.io/#social-share)ga o'tish orqali do'stlaringizga va ergashuvchilaringizga ulashing.
Agar koʻproq mashq qilishni istasangiz, [kod hissalarini](https://github.com/roshanjossey/code-contributions) tekshiring.
-3
View File
@@ -1,5 +1,4 @@
[![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.svg?v=103)](https://github.com/ellerbrock/open-source-badges/)
[<img align="right" width="150" src="https://firstcontributions.github.io/assets/Readme/join-slack-team.png">](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)
@@ -116,8 +115,6 @@ Chúc mừng! Bạn vừa hoàn thành quy trình tiêu chuẩn copy (fork) -> S
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 dự án (project) khác, chúng tôi đã tổng hợp một danh sách các dự án có các vấn đề đơn giản mà bạn có thể bắt đầu. Hãy kiểm tra [danh sách dự án trong ứng dụng web](https://firstcontributions.github.io/#project-list).
### [Tài liệu bổ sung](../additional-material/git_workflow_scenarios/additional-material.md)
+1 -1
View File
@@ -86,7 +86,7 @@ git push origin <add-your-name>
`<add-your-name>` 替換為之前新建的分支名稱。
<details>
<summary> <strong>如果在 push(發佈)程中出 error(錯誤),點擊這裡</strong> </summary>
<summary> <strong>如果在 push(發佈)程中出 error(錯誤),點擊這裡</strong> </summary>
- ### Authentication Error
<pre>remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead.
+1
View File
@@ -81,4 +81,5 @@
| <img alt="Tükmençe" title="Türkmençe" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/tm.svg" width="22"> | [Türkmençe](README.tm.md) |
| <img alt="հայերեն" title="հայերեն" src="https://cdn.statically.io/gh/hjnilsson/country-flags/master/svg/am.svg" width="22"> | [հայերեն](README.arm.md) |
| <img title="አማርኛ dili" alt="አማርኛ ቋንቋ" src="https://cdn.statically.io/flags/et.svg" width="22"> | [አማርኛ ቋንቋ](translations/README.et.md) |
| <img title="Монгол хэл" alt="Монгол хэл" src="https://cdn.statically.io/flags/mn.svg" width="22"> | [Монгол хэл](README.mn.md) |
| <img alt="Kurdî" title="Kurdî (Kurdish)" src="https://upload.wikimedia.org/wikipedia/commons/3/35/Flag_of_Kurdistan.svg" width="22"> | Kurdî |
-63
View File
@@ -1,63 +0,0 @@
Heres a normalized version of the text without GitHub command examples:
---
# પ્રથમ યોગદાન
આ પ્રોજેક્ટનો ઉદ્દેશ નવા સ્રોતકર્તાઓને તેમની પ્રથમ યોગદાન આપવાની પદ્ધતિને સરળ બનાવવાનો અને માર્ગદર્શન આપવાનો છે. જો તમે તમારી પ્રથમ યોગદાન આપવા માગો છો, તો નીચેના પગલાંઓને અનુસરો.
#### *જો તમે કમાન્ડ લાઈન સાથે નવા છો, તો અન્ય સાધનોના ઉપયોગ માટે ટ્યુટોરીયલ પર જાઓ.*
જો તમારા કમ્પ્યુટરમાં Git સ્થાપિત ન હોય, તો તેને સ્થાપિત કરવા માટેની માર્ગદર્શિકા જોવા માટે લિંક્પ્રदान કરો.
## આ રિપોઝિટરીનો "ફોર્ક" કરો
પૃષ્ઠના જમણાંમાં "ફોર્ક" બટન પર ક્લિક કરો. તે કરવાથી, આ રિપોઝિટરીની એક નકલ તમારા GitHub એકાઉન્ટમાં બનાવાઈ છે.
## કોપી કરેલા રિપોઝિટરીનો "ક્લોન" કરો
હવે, તમે જે રિપોઝિટરીનો ફોર્ક કર્યો છે, તે ક્લોન બનાવો.
તમારા ટર્મિનલને ખોલો અને આડેધોરને અનુસરો.
## એક શાખા બનાવો
તમારા કમ્પ્યુટરમાં રિપોઝિટરીના ડિરેક્ટરીમાં જાઓ. હવે શાખા બનાવો.
## જરૂરી ફેરફાર કરો અને તે ફેરફારોનો "કમિટ" કરો
ફાઇલને ટેક્સ્ટ એડિટરમાં ખોલો અને તમારું નામ ઉમેરો. ફાઇલને સાચવો.
જો તમે પ્રોજેક્ટના ડિરેક્ટરીમાં જાઓ, તો તમે ફેરફારો જોઈ શકશો. ફાઇલને તેમાં ઉમેરો.
હવે આ ફેરફારોને કમિટ કરો.
## GitHub પર તમારાં ફેરફારોનો "પુષ" કરો
તમારા ફેરફારોને મોકલવા માટેનું પગલું પૂર્ણ કરો.
## તમારા ફેરફારોને સમીક્ષ માટે મોકલો
જો તમે તમારા GitHub પરના રિપોઝિટરીમાં જાઓ, તો તમને બટન દેખાશે. આ બટન પર ક્લિક કરો.
હવે *પુલ રિક્વેસ્ટ* મોકલો.
જલદી જ હું તમારા ફેરફારોને આ પ્રોજેક્ટની માસ્ટર શાખામાં જોડવા જઇ રહ્યો છું. જ્યારે ફેરફારો જોડાશે ત્યારે તમને સૂચના મળશે.
## આગામી પગલાં શું છે?
અભિનંદન! તમે યોગદાન આપવાની પ્રક્રિયા પૂરી કરી છે.
તમારા યોગદાનનો ઉત્સવ મનાવો અને તેને શેર કરો.
જો તમને મદદની જરૂર હોય કે તમારી પાસે કોઈ પ્રશ્ન હોય, તો તમારે જોડાવા માટેનાં વિકલ્પો ઉપલબ્ધ છે.
હવે બીજા પ્રોજેક્ટમાં યોગદાન આપવાનું શરૂ કરો. અમે સરળ *ઇશ્યુઝ* સાથેના પ્રોજેક્ટોની યાદી એકત્રિત કરી છે.
### વધુ સામગ્રી માટે અમારું વેબપેજ જુઓ.
## અન્ય સાધનોના ઉપયોગ કરતા ટ્યુટોરીયલ
---
Feel free to let me know if you need further modifications!