Skip to content

Latest commit

 

History

History
212 lines (142 loc) · 5.08 KB

File metadata and controls

212 lines (142 loc) · 5.08 KB

Task 1: Practicing on Your Own

Now it’s time to start contributing!

1. Create a GitHub Account 📝

If you don’t have a GitHub account yet, that’s your first step. GitHub is where we host and collaborate on the project.

📘 Official documentation:

💜 Beginner-friendly (PT-BR):

2. Install Git 💻

To contribute, you’ll need Git, the version control system that helps track code changes.

📘 Official documentation:

💜 Beginner-friendly (PT-BR):

3. Fork the Project 🍴

3.1 Fork? What? 🤔

A fork is your own copy of a repository.

Think of it like copying a recipe so you can experiment freely without changing the original. You can tweak, break, and improve things without affecting the main project.

If your changes turn out great, you can suggest them back via a pull request.

3.2 Why use a fork? 💡

  • Experiment safely
  • Contribute improvements
  • Learn from real projects

3.3 How to fork 🔨

  1. Go to the repo: https://github.com/cumbucadev/git-chaos
  2. Click Fork (top right)
  3. You’ll get your own copy: your-username/git-chaos

3.4 Original repo vs your fork 🆚

Original (cumbucadev/git-chaos):

  • Main source of truth
  • Has issues and PRs

Your fork (your-username/git-chaos):

  • Your playground
  • Safe to experiment

Tip: always check the repo path to make sure you’re in your fork.

4. Clone your fork 🐏

4.1 Clone? What? 🤔

Cloning means downloading your fork to your computer.

4.2 Why clone your fork? 🧐

  • Work locally
  • Full control
  • Use your favorite tools

4.3 How to clone 📖

git clone https://github.com/your-username/git-chaos.git
cd git-chaos

5. Find an issue to work on 🔍

Go to the repo → Issues tab Look for:

👉 Task 1: Create file: your-username.txt

This issue is created just for you.

6. Create a new branch 🎋

git checkout -b 12

(Use your issue number instead of 12)

7. Make your changes 🔨

Follow the issue instructions and create your file:

chaos/task_1/your-username.txt

8. Stage your changes ➕

git add chaos/task_1/your-username.txt

9. Commit your changes ✅

9.1 Commit? What? 🤔

A commit is a snapshot of your changes.

9.2 Make a commit 🔨

git commit -m "Add your-username.txt"

10. Push your changes 🤞

10.1 Push? What? 🤔

Push = send your changes to GitHub.

10.2 Push your changes 🔨

git push origin 12

10.3 Why push? ❓

  • Share your work
  • Backup
  • Enable collaboration

11. Create a Pull Request (PR) 💬

  1. Go to your fork on GitHub
  2. Click Compare & pull request
  3. Title:
Task 1: your-username.txt
  1. Description:
Task 1:
- Added your-username.txt

Closes #12
  1. Click Create pull request

Done 🎉

Here’s an example of a pull request so you can see what it looks like.

What happens next? 🙋

  • Your PR will be reviewed
  • You might get feedback
  • Once approved, it will be merged

Next steps 👀

  • Check your PR for comments
  • Respond and improve
  • Move on to the next task

Congrats on your first open source contribution! 🚀

Everything we build at Cumbuca Dev is free and made for the community 💜
If this helped you, consider supporting us on GitHub Sponsors and help us keep creating more accessible learning experiences.

👉 https://github.com/sponsors/cumbucadev