How I Started Using GitHub to Document My Projects

A developer recounts learning to use GitHub while building their first repository, AI Civic Issue Mapper, and emphasizes that beginners should start documenting projects early rather than waiting for expertise. The developer now uses GitHub for all projects, including two AI-related ones, and credits real-world use and AI tools like Claude and ChatGPT for their learning.

For a long time, I thought GitHub was something you were supposed to understand before you started using it. Commands, repositories, commits, pushing code, errors... Honestly, when I first started using it, a lot of it was confusing. I only started using GitHub seriously toward the end of my 2nd year of B.Tech. And my first proper repository was for a project I was actually building: 👉 AI Civic Issue Mapper That was when GitHub stopped feeling like something I should learn and started becoming something I actually needed to use. AI Civic Issue Mapper was my first proper GitHub repository. As I worked on the project, I started putting almost everything there: Source code Project structure README documentation Features Tech stack Screenshots Deployment information Roadmap Known limitations It wasn't perfect from the beginning. I was learning while building. And that made the repository much more meaningful to me than simply uploading a finished project. One of the biggest problems I faced initially was simply understanding what was happening. I'd run a command and get an error. Then I'd wonder: “Okay... what did I do wrong?” 😭 Sometimes I didn't even understand what the command was supposed to do in the first place. I had to gradually understand things like: What a repository actually is How to push code How commits work How changes are tracked How to update a project How to structure a README How GitHub connects with deployment I learned a lot of this through Claude and ChatGPT, especially when I got stuck on errors or didn't understand a command. But the biggest learning came from actually using GitHub while working on real projects. Today, I use GitHub for almost everything related to my projects. I use it to: Store my code Document projects Track changes Showcase my work Collaborate with others Connect projects with deployment Keep my work organized Have something I can eventually show recruiters And I'm still learning. I don't consider myself a Git or GitHub expert. There are still things I don't understand immediately, and I still run into errors. But now, instead of being completely lost when something goes wrong, I can usually figure out where to start. AI Civic Issue Mapper was my first proper repository, but it didn't stay my only project. I currently have three projects on GitHub. Two of them involve AI, while another is a project I'm working on with a friend based on her idea. That has also helped me understand something important: GitHub isn't just about having a huge number of repositories. It's about having a place where your actual work exists and grows. When I first started, I thought I needed to become good at GitHub before I could properly use it. Now I think the opposite is closer to the truth. You learn GitHub by using GitHub. You make mistakes. You get errors. You search for what they mean. You fix them. And eventually, commands that once looked confusing start becoming normal. I'm still somewhere in that process. If you're a student who hasn't started using GitHub yet, don't wait until you have 10 or 20 projects. You don't need a huge portfolio. You don't need to know every Git command. You don't even need to be an expert. Start documenting what you're already building. Even one small project is enough to start. For me, that first project was AI Civic Issue Mapper. And looking back, I'm glad I started when I did. Because now GitHub isn't just a place where my code sits. It's becoming a record of what I'm learning and building.