@PrakstheBruce

The BIIGESST and smallest mistake that I did 🫢🫢😭😭…. Guys, I Finally was Hyped Up that I completed my Slack Bot- Smile-Bot!!! BUT While trying to ship it, The Ship It Button was Greyed Out! I did not know what to do, when two of my bros @mr_kn5196❤️❤️ and @fsh 🍀🍀 Helped me out!! I was not a really big bug! I JUST PUT A “.git” EXTENSION IN MY GIT HUB URL!! THAT CAUSED THE ERROR! Hope you guys have a Great week ahead! And I WILL SOON POST UPDATES ON MY NEW “frictionless” project––“CodeAtlas!!”. Peace!!

🗺️ CodeAtlas — Devlog #2
Day 2(According to my Schedule 😜) — Heyyy Guys!! CodeAtlas can finally talk to GitHub.
The UI looked pretty decent when I started off, But with more improvements I am actually going somewhere!
Today I started making CodeAtlas actually work.
I added:

🔗 GitHub repository URL parsing

🐙 GitHub API integration
📊 Repository metadata
⚡ Loading states
❌ Invalid URL & repository error handling
⌨️ Enter-to-analyze support

Now I can paste a public GitHub repository and CodeAtlas can retrieve and display its information!! Yayy!!!
The next step is much more interesting:
Instead of just knowing the repository exists, CodeAtlas needs to understand what’s inside it.
Next up → mapping the repository’s file structure. 🗺️ And Good Luck TO ALL Reading this!
#CodeAtlas #Devlog #BuildInPublic #Stardance #HackClub #GitHub #WebDevelopment #TypeScript #React

🚀 CodeAtlas — Devlog #1
Day 1 — The Beginning
Heyy Guyss!! I’m starting a new project called CodeAtlas 🗺️
The idea is simple: understanding an unfamiliar codebase can be painful ! You open a GitHub repository and suddenly you’re staring at hundreds of files, folders, imports, and dependencies with no idea where to start.
Sooo I’m building CodeAtlas to turn a codebase into an interactive map — helping developers understand how different parts of a project connect, where important logic lives, and how the whole system works.
Today, I set up the project with React + TypeScript, initialized the GitHub repository, and started laying the foundation.
The goal:

GitHub repository >Codebase analysis > Interactive architecture map

This is Day 1. Let’s see how far I can take it. 🚀
#CodeAtlas #BuildInPublic #Stardance #HackClub #Devlog #WebDevelopment

Devlog #2 — Another Interesting Problem- After getting the basic Slack commands working, I started preparing the project for deployment. That introduced a completely different side of development that I hadn’t really dealt with before: Git, GitHub, SSH, environment variables, and servers. One of the first things I learned was why .env files shouldn’t be pushed to GitHub. My Slack tokens are required for the bot to work, but they’re also credentials that shouldn’t be sitting inside a public repository. I added .env to .gitignore and learned that deploying an application means recreating those environment variables securely on the server. Git also gave me a few headaches. My local repository and GitHub repository weren’t completely in sync, so my first push was rejected. Instead of forcing the push, I had to understand what Git was actually telling me and pull the remote changes before pushing again. Now I’m moving on to Hack Club Nest. The goal is to get SmileBot running on a real server instead of depending on my laptop and terminal being open. The interesting part of this project so far is that the Slack commands themselves weren’t the hardest part. Getting the entire development workflow around them working has taught me just as much. Next step: SSH into Nest, deploy SmileBot, and get it running 24/7.(P.S I just applied, waiting for approval!!)

My First and Useful Devlog(It would be helpful for ppl staring out.) Devlog #1 — Setting Up My SlackbotProject: I started setting up my development environment for the Stardance Slackbot challenge.I already had VS Code and Node.js installed, so I expected the setup to be pretty straightforward. I ran: “npm -v” but PowerShell returned an error saying that scripts were disabled on the system. Initially, I thought there was something wrong with my Node.js or npm installation. After looking into it, I realized that npm itself was installed correctly. The issue was that PowerShell’s execution policy was preventing the “npm” PowerShell script from running. Instead of changing a bunch of system settings, I switched the VS Code terminal from PowerShell to Command Prompt and tested it again: “node -v” &
“npm -v” Both commands worked!!! I was then able to continue with the project setup: “npm init -y”
“npm install @slack/bolt dotenv” What I learned-This was a small issue, but it was a useful reminder that debugging isn’t always about the code itself. Sometimes the problem is with the environment you’re running the code in. The important part was figuring out what was actually failing instead of immediately reinstalling Node.js or changing random settings. Now the development environment is ready, and I can move on to building the actual Slackbot. Next: Create the basic Slackbot and get it responding to messages.