Write Pro Git Commits for Remote Teams

I found this multiple times: Even when devs meant they were cherry-picking changes from one Git branch to another, they were doing it all manually. 😬 There is a specific, simple git command to handle it. Now, that's not the main problem, though. The actual issue is in understanding its use cases and when to apply it. Published a quick video explaining the "why" part, and then "how" to achieve it. If you have ~10 mins, take a look, the link is in the comment below. Thanks! #javascript #react #git #github #opensource #webdevelopment #softwareengineering #fullstack #cherrypick

There are files in every project you almost never open as a developer. The setup is done, things work, you don't quite question it. .env files are one of those file I didn’t paid much attention to because things worked, but now I had to set them in my next & vite personal projects. They are pretty easy to grasp so here is a summarise: 🔵 What are env files? Files at the root of you project that are storing configuration outside your code. Instead of hardcoding values, your app reads them from the environment via process.env.KEY_NAME. Two problems solved: values that change per environment, and secrets that must never live in your codebase. 🟣 The files and what each one means .env → committed to git, shared defaults between teammates, never put secrets here .env.local → never committed, your personal secrets stored on your personal machine .env.example → committed to git, documents what keys exist, key declarations but no values If your env file is committed to git, it can never contain secrets. Git keeps history forever. Bots scan GitHub constantly for credentials. If ever pushed by mistake all secret keys are compromise and you need to regenerate all fast because it’s a huge security problem. Always make sure to have the env file containing secrets in git ignore or it can bring hell down. Setting things up from scratch has a way of making you think about decisions you usually inherit. #frontend #reactdeveloper #frontendarhitecture #react #recrutiers

Waitt… if you're still using git clone like this: git clone <repo-url> Then you're probably downloading way more than you actually need 👀 Better approach?? Here u go ;) ✨ git clone --depth 1 <repo-url> honestly… it's one of those small things that just makes sense once you know it. When you normally clone a repo, Git pulls everything literally the entire history, every commit, every change since day one. But with --depth 1 {aka a shallow clone}, you only get the latest version of the code. No history. No extra baggage. Just what you need. Which means way faster cloning, Saves disk space 🧠 and hell cleaner when you just want to use the project If you've never tried this before, go ahead and give it a shot ;) Follow Sakshi Jaiswal ✨ for more quality content like this. #Frontend #React #Sakshi_Jaiswal #FullstackDevelopment #javascript #TechTips #Git #Clone #flags #Webdev

🚀Just finished creating a clean and complete Git & GitHub Workflow Guide for developers! Whether you're a beginner or already working with Angular, React, Node.js or Spring Boot, this guide covers everything you need: • Repository setup (git init, .gitignore) • Connecting to GitHub • Commit & push best practices • Feature branch workflow • Using git stash effectively • Keeping your code updated (git pull) • Clean merge process 💡 Simple workflow: 1. Create a branch → git checkout -b feature-name 2. Work & commit 3. Push → git push -u origin feature-name 4. Synchronize with main → git pull origin main 5. Merge cleanly If you're tired of searching Git commands every time or want to improve your version control habits, this is for you! #Git #GitHub #Workflow #SoftwareEngineering #Programming

🚀 Just shipped Auto-Deploy on Nexus — push to GitHub, go live automatically. I've been building Nexus, a full-stack deployment platform (think a self-hosted Vercel), and today I shipped a feature that completes the CI/CD loop: ⚡ GitHub Auto-Deploy via Webhooks Here's what it does: → Connect your GitHub repo to a Nexus project → Enable Auto-Deploy with one toggle → Get a unique webhook URL + HMAC-SHA256 secret → Paste it into GitHub's webhook settings → From that moment, every push to your tracked branch triggers an automatic deployment — no manual clicking required And the engineering behind it wasn't trivial: 🔐 Secure by design — Every incoming webhook is verified using HMAC-SHA256 signature validation (timing-safe compare). Invalid signatures are rejected before any logic runs. 🧱 Middleware ordering matters — The biggest gotcha was that Express's express.json() consumes the raw body stream, making HMAC verification impossible. The fix was registering the webhook route with express.raw() before the JSON middleware — the same pattern used for Stripe/Razorpay webhooks. 🛡️ Multiple safety layers: Branch matching (only deploy on the right branch) Repo URL identity check (no cross-repo spoofing) Build quota enforcement before triggering Branch deletion events are gracefully skipped 📦 Full stack: TypeScript, Node.js, Express, MongoDB, React — deployed with its own infrastructure. If you're building something and tired of manually clicking "redeploy" every time you push — this is the workflow you want. 👉 I'm looking for early testers: If you want to try Nexus and ship your frontend projects with one push, here's the link https://madhavkumar.tech #buildinpublic #webdev #devtools #nodejs #typescript #cicd #opensource #deployment #javascript #react #github

We're back with another update on react-infinite-scroll-component(https://lnkd.in/gZgRuSkG)! 🥁 When I took over as maintainer, I laid out a 4-phase roadmap to bring this library back to life. Today, we're crossing off Phase 2 with the release of v7.0.0. 🎉 Here's where we stand: ✅ Phase 1 — Comprehensive test suites & CI/CD automation (v6.1.1) ✅ Phase 2 — React 17 migration (v7.0.0) 🔜 Phase 3 — TypeScript conversion & modern React features 🔜 Phase 4 — Accessibility improvements & enhanced documentation What shipped in v7: - React 17 peer dependency support - Jest + React Testing Library test coverage - Storybook upgraded from v5 to v7 - Revamped CI/CD with automated publish workflows - ESLint, Prettier, and Husky configured for contributor-friendly DX - Node.js 18+ baseline 109k+ dependents. Still going. Still breaking nothing. Huge thanks to Ankeet Maini for the trust, and to everyone who's filed issues, opened PRs, or just starred the repo, your patience means a lot. I'll be actively going through open issues and PRs now, so if you've been waiting, your turn is coming. 🙌🏻 #OpenSource #React #JavaScript #TypeScript #WebDevelopment #Community #Maintainership

Working with Claude Design and GitHub? And can't commit the changes to the repo? Important: repo access may be read-only, not write access. In that case, the easiest workflow is to ask Claude Design for a patch file, then apply it locally with: git apply your-changes.patch Then review, commit, and push yourself. It is a simple way to use Claude Design for UI work while still keeping full control over your repo. #ClaudeDesign #Git #GitHub #DeveloperWorkflow #UIEngineering

TypeScript doesn’t make your code safe. It makes it safer. There’s a difference. Here’s why 👇 TypeScript checks: ✔ Compile-time types But runtime: ❌ Anything can happen Example: → API returns unexpected data → Type says “string” → Runtime gives null Result: → Crash What works: ✔ Validate data at runtime ✔ Don’t blindly trust types ✔ Use proper guards Key insight: TypeScript is not a runtime safety tool. It’s a development aid. #TypeScript #JavaScript #Frontend #Backend #SoftwareEngineering #Engineering #Programming #Tech #CleanCode

TypeScript tip: Don't use 'any'. Even when you're lazy. Define your types properly and future-you will thank present-you. Also — your teammates will thank you too. Strong types = fewer bugs = fewer 2am debugging sessions. #TypeScript #FrontendDev #CleanCode

Still using VS Code after trying everything else — and here's exactly why 🔧⚡ From extensions to Git integration to the built-in debugger, VS Code just works. I broke down every real reason it keeps winning — plus common mistakes most developers make with it. Read the full post at 👉 hamidrazadev.com 💬 Drop a comment — are you still on VS Code or did you switch to something else? #vscode #webdev #javascript #developertools #productivity #frontenddevelopment #programminglife #hamidrazadev