Welcome to OpenSource-Hunt, an interactive Open Source contribution challenge by OpenLake — the Open Source programming club of IIT Bhilai.
Build. Learn. Contribute.
Instead of just learning about Open Source, this repository gives you a chance to experience the complete contribution workflow yourself.
The repository contains intentionally introduced bugs, documentation issues, improvements, and beginner-friendly tasks.
Your mission:
Find an Issue → Get Assigned → Fork → Branch → Fix → Commit → Push → Pull Request → Review → Merge 🎉
OpenLake is IIT Bhilai's hub for Open Source innovation and collaborative development.
The community focuses on building real projects, learning together, and contributing to Open Source. The OpenLake GitHub organization hosts projects maintained by IIT Bhilai students across different technologies and problem domains.
Explore OpenLake:
- 🌐 Website: https://openlake.in/
- 💻 GitHub: https://github.com/OpenLake ## assign github.com
- 📸 Instagram: https://www.instagram.com/openlake_iitbhilai/
- 💬 Discord: https://openlake.in/
OpenSource-Hunt is a hands-on contribution challenge created to introduce newcomers to the real Open Source workflow.
The repository intentionally contains:
- 🐛 Bugs
- 📚 Documentation issues
- 🎨 UI/UX improvements
- ♿ Accessibility improvements
- 💻 Code improvements
- ✨ Small enhancements
- 📝 Typographical errors
- 📱 Responsive design issues
- 🟢 Beginner-friendly tasks
You don't need to be an Open Source expert.
You just need to be willing to learn and contribute.
Head over to the Issues section and find something you would like to work on.
Look for labels such as:
good first issue
beginner friendly
easy
documentation
bug
enhancement
medium
help wanted
Choose an issue according to your current skill level.
Found something interesting?
Comment:
/assign
Automated Github Actions will assign the issue to you.
Click the Fork button on GitHub.
This creates your own copy of OpenSource-Hunt under your GitHub account.
Clone your fork:
git clone YOUR_FORK_URLMove into the project:
cd OpenSource-HuntNever work directly on main. Create a branch for your issue:
git checkout -b fix/issue-12Name it after what you're doing, for example:
fix/issue-12
docs/update-readme
feat/add-dark-mode
Keeping each issue on its own branch is what lets you work on more than one thing without your changes getting tangled together.
Now it's time to solve the issue! 🔎
Read the issue carefully and make only the changes required to solve it.
If you're stuck, don't hesitate to ask for help.
Remember:
Open Source is about collaboration, not just code.
Before committing, run the project locally and confirm your fix actually works. Check that you haven't broken anything else while you were in there.
Then review exactly what you're about to commit:
git status
git diffIf you see files you didn't mean to change, sort that out before moving on.
Stage your changes:
git add .Create a meaningful commit:
git commit -m "fix: resolve issue #12"Try to keep commit messages short and descriptive.
Push your branch to your fork:
git push origin fix/issue-12Use the same branch name you created in step 5.
Open your fork on GitHub.
Create a Pull Request against the original OpenSource-Hunt repository.
In the Pull Request description, link the issue:
Closes #12
This tells GitHub that your Pull Request solves that issue.
Once your Pull Request is submitted, an OpenLake maintainer will review it.
You might receive:
- ✅ Approval
- 💬 Suggestions
- 🔄 Changes requested
Don't worry if changes are requested!
That's a normal part of Open Source development.
Make the requested changes, commit them, and push again:
git add .
git commit -m "address review comments"
git push origin fix/issue-12Your Pull Request will update automatically.
Once your Pull Request is approved, it will be merged.
Congratulations! 🎊
You've just completed your first Open Source contribution.
You went through the same basic workflow used in real collaborative software projects.
| Label | Description |
|---|---|
good first issue |
A great issue for your first contribution |
beginner friendly |
Suitable for contributors with basic knowledge |
documentation |
Documentation-related work |
bug |
Something that isn't working correctly |
enhancement |
A feature or improvement |
easy |
A straightforward task |
medium |
Requires moderate technical understanding |
help wanted |
Contributors are especially encouraged to help |
By participating in OpenSource-Hunt, you'll get practical experience with:
- Git
- GitHub
- Issues
- Forks
- Branches
- Commits
- Pull Requests
- Code Reviews
- Issue Assignment
- Collaboration
- Open Source contribution practices
More importantly, you'll learn how contributors work together on real projects.
Before contributing, please read CONTRIBUTING.md.
Please remember:
- Work only on issues assigned to you.
- Don't duplicate another contributor's work.
- Keep your Pull Request focused on one issue.
- Test your changes before submitting.
- Write clear commit messages.
- Be respectful to other contributors.
- Ask questions when you're stuck.
That's completely okay!
You don't need years of programming experience to get started.
Start with an issue labelled:
good first issue
or:
beginner friendly
Documentation and simple fixes are also excellent ways to make your first contribution.
Your first Pull Request doesn't need to be perfect.
It just needs to be your first step.
OpenLake's philosophy is simple:
OpenSource-Hunt follows the same idea.
Build something meaningful.
Learn from the process.
Contribute to something bigger than yourself.
🌐 openlake.in · 💻 github.com/OpenLake · 📸 @openlake_iitbhilai
Happy Contributing! 💙