A shared practice repository for all cohorts (SQL, Python, Data Engineering, Data Science) to get real, hands-on experience with Git and GitHub collaboration - forking, branching, issues, and pull requests - using tasks matched to what each cohort is currently learning.
This is not about being an expert coder. It's about becoming comfortable with the workflow professional teams use every day, on a shared codebase.
- Fork this repository to your own GitHub account (button top-right).
- Browse the Issues tab and find one in your track that's still unclaimed (no one has commented "I'll take this" yet, and it isn't assigned).
- Comment "I'll take this" on the issue to claim it - this is standard team etiquette, it stops two people from doing the same work.
- Clone your fork, create a branch, do the work, and open a pull request back to this repo. See CONTRIBUTING.md for the exact commands.
- A reviewer (instructor or TA) will review your PR and merge it.
| Track | Folder | What it covers |
|---|---|---|
| SQL | /sql |
Beginner-level SQL practice against a small mock e-commerce database. |
| Python | /python |
Small Python functions, bug fixes, and utilities. |
| Data Engineering | /data-engineering |
Data validation, cleaning, and small pipeline utilities. |
| Data Science | /data-science |
Exploratory analysis, stats, and visualization tasks on a shared dataset. |
- 🟢 Git Mechanics issues (
tier:1) - deliberately simple (fix a typo, add your name to a file, add a comment). These exist purely to help you practice the fork → branch → PR → merge workflow without needing deep track knowledge yet. Perfect for your very first PR. - 🔵 Track Challenge issues (
tier:2) - small, real technical tasks matched to your track's current level, where you'll get actual feedback on your work during review.
Start with a 🟢 Tier 1 issue in your own track if this is your first pull request ever.
- One issue = one contributor. Claim it in the comments before starting.
- Keep pull requests small and focused on the one issue you claimed.
- Be kind in reviews - everyone here is learning.
- If your PR sits for more than 3 days without a claim update, it may be reassigned.
Good luck, and welcome to your first real collaborative codebase.