When I joined GitHub, I didn't have a plan.
I just started building things — some useful, some broken, some embarrassing.
But 18 repositories later, I've learned more from pushing code than from any tutorial.
Here's an honest breakdown of what I built, what flopped, and what actually taught me something real.
🦈 The One That Started Everything: Pull Shark Automation
Automate GitHub PR creation at scale — 62 PRs/min with Python
This was my first "real" project. I wanted the GitHub Pull Shark badge, but doing it manually was painfully slow. So I automated it.
What it does:
- Dual modes: Sequential (stable) and Parallel (blazing fast async)
- Multi-token rotation to stay within rate limits
- Auto-merge, Discord/Slack webhooks, proxy support
- Windows compatible
# Sequential mode
python main.py
# Parallel mode (fast)
python parallel_automation.py --count 100 --concurrent 10
# Test without committing
python main.py --dry-run
Real-world result: 62.5 PRs/min with 3 tokens and 20 parallel workers.
⚠️ Built for learning and CI/CD stress testing. Use responsibly.
🔗 Pull-Shark-Automation on GitHub — drop a ⭐ if it helps!
🤝 Pair Extraordinaire — Automating Co-Author Badges
After Pull Shark, I went after the Pair Extraordinaire badge.
Same idea — understand how GitHub's contribution system works by building around it.
This one taught me:
- How Git co-authoring actually works under the hood
- Managing multiple identities in commits
- Token scoping and permission management
🔗 Pair-Extraordinaire on GitHub — drop a ⭐ if it helps!
💡 What 18 Repos Actually Taught Me
1. READMEs matter more than code quality at first
Nobody digs into your code on first impression. They read your README.
Write it like you're explaining to a smart friend who's never seen your project.
2. Stars don't validate you — but they do signal clarity
Pull Shark got 27 stars in a week not because the code was perfect,
but because the README was clear and the use case was specific.
3. Broken repos are fine. Abandoned repos are not.
I have repos I haven't touched in weeks. That's okay.
What's not okay is leaving them with no description, no README, no context.
Even a one-liner description helps someone understand what you were thinking.
4. Your GitHub is a portfolio before you have a portfolio
I don't have a deployed portfolio site yet (it's in progress 👀).
But recruiters and collaborators can still see exactly what I can do
by looking at my repos. Treat every repo like a mini-resume.
5. Committing consistently beats committing perfectly
Green squares on your contribution graph tell a story.
Don't wait until your code is "ready." Push early, push often.
🛠️ My Current Stack Across All Projects
| Language/Tool | Used For |
|---|---|
| Python | Automation, scripting, GitHub tools |
| JavaScript / TypeScript | Web apps, frontend logic |
| React + Next.js | UI, full stack projects |
| Node.js | Backend, API building |
| Firebase | Auth, real-time DB |
| HTML + CSS | Foundations, landing pages |
🔭 What I'm Building Next
- Personal portfolio site with Next.js (almost done)
- AI-powered web app integrating Claude / OpenAI APIs
- More open source tools for developers
🤙 Let's Connect
If you're a dev from Pakistan, a beginner just starting out,
or someone who loves building weird automation tools — let's connect.
Drop a comment, follow along, or check out my repos.
📦 GitHub → itxashancode
🌐 Linktree → itxashanvibes
What was your first GitHub repo? Drop it in the comments 👇
Top comments (0)