Akash Santra

Posted on Jun 5

How I Finally Finished My Unfinished Chat App with GitHub Copilot

#devchallenge #githubchallenge #githubcopilot #opensource

GitHub “Finish-Up-A-Thon” Challenge Submission

This is a submission for the *GitHub Finish-Up-A-Thon Challenge*.

What I Built

PASO is a real-time chat platform inspired by apps like WhatsApp, Discord, and Slack.

It supports:

Real-time messaging
Group chats
Voice and video calling
AI-powered moderation
OTP-based password recovery
Admin dashboard
Redis-powered Socket.IO scaling
Machine Learning integration using FastAPI

I originally started this project as a way to learn full-stack development and distributed systems. Like many side projects, it reached a point where the core features worked, but there were still many unfinished parts, missing documentation, incomplete testing, and several production-level improvements that I wanted to add.

The GitHub Finish-Up-A-Thon gave me the perfect reason to come back and finally finish it properly.

Demo

Application Preview

The Comeback Story

One thing I like about this graph is that it tells the story better than I can.

I started PASO earlier as a learning project and made steady progress for a while. Like many side projects, it eventually slowed down and sat unfinished.

The GitHub Finish-Up-A-Thon gave me a reason to come back to it.

The spike in contributions during May reflects the work that went into finally completing the missing pieces: Redis scaling, OTP password recovery, testing improvements, documentation, roadmap planning, and overall project polish.

What started as "I'll come back to this someday" turned into a project I was finally proud to share publicly.

Before

Basic chat functionality
Limited documentation
Minimal test coverage
Single-instance Socket.IO setup
Missing password recovery flow
Several unfinished project docs
No clear future roadmap

What I Added

Redis Horizontal Scaling

One of the biggest upgrades was adding Redis support for Socket.IO.

This allowed the application to move beyond a single server setup and support communication across multiple instances using Redis Pub/Sub.

Working on this taught me a lot about distributed systems and real-time communication.

OTP Password Recovery

I implemented a complete OTP-based password recovery system.

Users can now:

Request password reset codes
Verify OTPs
Securely update passwords

This made the authentication flow much more realistic and production-ready.

Testing Improvements

I spent a lot of time improving tests across the project.

I added and expanded tests for:

Authentication
Messaging
Groups
Admin functionality
Middleware

This gave me much more confidence when making changes.

Documentation Overhaul

A huge part of this challenge was finishing the documentation.

I added and improved:

Architecture documentation
Deployment guides
Scaling documentation
Testing guides
Security documentation
Roadmap planning

The goal was to make the project easier for future contributors to understand and use.

Roadmap & Future Planning

I also completely updated the roadmap to better reflect where the project is today and where it can go in the future.

Future plans include:

End-to-End Encryption
Mobile Applications
Enterprise Features
Multi-region Scaling
Plugin Ecosystem

Community Response

One thing that surprised me was seeing people actually use and interact with the project.

After sharing PASO publicly and documenting the development journey, the project received:

5,000+ LinkedIn post views
8 GitHub stars
7 GitHub forks

Posts:

For a student-built open source project, that was incredibly motivating and reminded me why finishing projects matters.

My Experience with GitHub Copilot

GitHub Copilot played a huge role throughout this project. I didn't use it to blindly generate code.

Instead, I used it as a development partner.

Where Copilot Helped Most

Boilerplate Code

Copilot helped generate:

Controllers
Routes
Middleware
Database models
API handlers

This saved a lot of repetitive work.

Testing

One of the biggest benefits was test generation.

Copilot helped me create test cases much faster, which encouraged me to write more tests than I normally would.

Debugging

While implementing Redis scaling and authentication features, Copilot was extremely useful for:

Explaining errors
Suggesting fixes
Identifying edge cases
Reviewing implementation ideas

Documentation

A large portion of the documentation improvements were accelerated with Copilot.

It helped me structure technical documentation, explain architecture decisions, and improve overall clarity.

What I Learned

The biggest lesson from this project is that finishing a project requires a different mindset than starting one.

Building features is fun.

Writing tests, improving documentation, fixing edge cases, and polishing the developer experience is where real software engineering happens.

GitHub Copilot helped me spend less time on repetitive tasks and more time learning system design, architecture, and problem solving.

Final Thoughts

PASO started as a learning project.

This challenge pushed me to turn it into something much closer to a real production-ready application.

More importantly, it reminded me that unfinished projects still have value.

Sometimes the hardest part isn't building a project.

It's coming back and finishing it.

For me, that's what this challenge was really about.

Thanks GitHub and DEV for creating a challenge that encouraged builders to finish what they started. ❤️

If you'd like to check out the project, feedback and contributions are always welcome.

⭐ Project Repository: https://github.com/CodePlaygroundHub/paso-chat-app
GitHub: https://github.com/Akash504-ai
LinkedIn: https://www.linkedin.com/in/akash-santra-5823b42a6/
X (Twitter): https://x.com/akashsantra999

DEV Community