BM: Baca dalam Bahasa Melayu
World 12: Career Quest
Your first open-source PR
You will learn: the steps to suggest a fix to someone else's project.
The problem
You love a free notes app. Its README has a typo. You are not on their team. Can you still fix it?
Tap the line with the typo.
0 of 1 found
Try it
Open source code is public. Anyone can suggest a change. The project’s keepers, called maintainers, decide what goes in. Who does what?
Drag a card into a box. Or tap the card, then tap the box.
Watch
Tap every issue made for first-timers.
0 of 2 found
Maintainers mark easy tasks with a label: good first issue: A label for an easy issue that a newcomer can pick up.. Start there. Big rewrites can wait.
Try it
Projects keep their house rules in CONTRIBUTING.md: The house rules for helpers: how to report, change and send work.. Read this one. Then follow rule 1 on issue #42.
Contributing to QuickNotes
Thanks for helping!
- Ask in the issue before you start.
- One small change per pull request.
- Write clear commit messages, like
docs: fix typo. - Be kind. We are all volunteers.
Hint
Open Issues, then #42. Comment with a question, like: Can I take this one?Try it
Put the whole journey in order. You met forks in World 4 and pull requests in World 5.
First step at the top. Put these in order. Use the arrows, or drag.
- Reply kindly to the review
- Push the branch to your fork
- Open a pull request
- Fork the project to your account
- Clone your fork
- Make a new branch
- Make one small change and commit it
Hint
You can’t clone a fork that doesn’t exist yet. And the PR comes after the push.Try it
Your fix is committed on a branch called fix-readme-typo. Build the command that sends it to your fork.
Tap the pieces in the right order.
Hint
After cloning your fork,origin is your fork.Check
A maintainer replies: “Thanks! Can you fix the same typo in docs/setup.md too?” What do you do?
Pick one answer.
Watch
Tap each point on the timeline.
One PR is a great start. Tap your path from here.
You did it!
You can now suggest a fix to any open-source project.
Go deeper (optional)
Many repos have a contribute page that lists their good first issues. Try github.com/OWNER/REPO/contribute. Your PR may sit for days. Maintainers are often volunteers, so be patient. Some projects ask you to sign a contributor agreement first. CONTRIBUTING.md will say so.
Bahasa Melayu
Anda suka satu aplikasi nota percuma. README-nya ada salah taip. Anda bukan ahli pasukan mereka. Bolehkah anda tetap membaikinya?
Kod sumber terbuka (open source) boleh dilihat semua orang. Sesiapa pun boleh cadangkan perubahan. Penjaga projek, iaitu maintainer, tentukan apa yang masuk. Siapa buat apa?
Maintainer tanda tugasan mudah dengan label good first issue (untuk orang baru). Mula di situ. Tulis semula kod besar boleh tunggu.
Projek simpan peraturan rumahnya dalam CONTRIBUTING.md. Baca yang ini. Kemudian ikut peraturan 1 dalam issue #42.
Susun seluruh perjalanan ini. Anda dah kenal fork (salinan projek orang lain) dalam World 4. Pull request (minta perubahan diterima) pula dalam World 5.
Pembetulan anda dah di-commit (titik simpan) dalam branch (cabang) fix-readme-typo. Bina arahan untuk hantar ke fork anda.
origin ialah fork anda.Maintainer balas: “Terima kasih! Boleh baiki salah taip yang sama dalam docs/setup.md juga?” Apa anda buat?
Satu PR ialah permulaan yang hebat. Tekan untuk lihat laluan anda dari sini.
Kini anda boleh cadangkan pembetulan kepada mana-mana projek sumber terbuka.
You finished this before. Practice is always welcome!
Official docs: Contributing to a project · Finding ways to contribute · Contributor guidelines (CONTRIBUTING) · git push
You've learned for 25 minutes. A short break helps your brain.
Sprint done! Great focus. Stretch for a minute?