GitHub Commit History Not Updating After Push

I stopped logging into Netlify to deploy changes to my portfolio. Instead, I set up GitHub Actions with a CI/CD pipeline. Now I just push code from my local machine — and my site updates automatically. That's it! No manual deploys. Just: ✅ git commit ✅ git push ✅ Live in minutes CI/CD isn't just for big teams. Even a personal project deserves an automated workflow. #GitHubActions #CICD #WebDevelopment #Netlify #DevOps Visit my Portfolio here → https://lnkd.in/eHfz8rxg

One week. One hackathon. And a very cool demo video 😂 I just shipped Envoy Watch — a GitHub App that automatically creates isolated preview environments for every pull request, then destroys them when the PR closes. Here's what that means practically: You open a PR. A bot comment appears on it within seconds. 3-7 minutes later, that comment updates with a live URL — a fully deployed version of your app, running your exact branch, in its own isolated container. You merge the PR. The environment is gone. No cleanup. No lingering infra. No cost. I built this on top of Locus's BuildWithLocus API — a platform that lets you deploy containers programmatically with a single API call. No Dockerfiles, no cloud console, no DevOps. I'd never used it before this week. The interesting engineering challenge wasn't the deployment part. It was the orchestration. GitHub doesn't talk to Locus. Locus doesn't talk to GitHub. My Next.js app sits in the middle — receiving webhook events from one side, making API calls to the other, storing the mapping in Neon Postgres so it knows which environment to destroy when a PR closes. Three moving parts. One flow. Fully autonomous. One honest note: for the hackathon, all environments deploy from my own Locus wallet. In production, each user would connect their own API key so deployments bill against their account, not mine. Scoped intentionally, the architecture supports it cleanly. The demo video says more than I can in a post. If you're a developer tired of shared staging environments breaking your team's workflow — this is for you. #buildinpublic #softwaredevelopment #africatech #nextjs #hackathon

🚀 DevFlow is evolving — and this update is a big one. When I started building DevFlow, the goal was simple: Make developer consistency visible and rewarding. Now, it’s getting closer to that vision. ⚔️ A structured rank system (E → S tiers) 📊 XP progression based on real work 🔗 GitHub integration — your commits now count 📈 NEW: Contribution graph + weekly, monthly, yearly time tracking You can now see your effort — not just feel it. Still in beta, still improving every day. But the system is starting to take shape. If you're someone who values consistency over shortcuts, this is for you. 🌐 Try it: https://lnkd.in/dr9nx6Uf BuildInPublic #DevFlow #Developers #Productivity #GitHub #StartupJourney

Sveltos v1.8.0 is out. Three new features, handful number of bug fixes, each targeting a specific operational gap. 1. 𝗚𝗶𝘁𝗢𝗽𝘀-𝗳𝗿𝗶𝗲𝗻𝗱𝗹𝘆 𝗸𝘂𝗯𝗲𝗰𝗼𝗻𝗳𝗶𝗴 𝗿𝗲𝗻𝗲𝘄𝗮𝗹 When Sveltos rotated a cluster's kubeconfig, it wrote a new key (`re-kubeconfig`) and updated `SveltosCluster.spec`. GitOps tools like Flux or ArgoCD saw this as live-state drift from the Git source. The fix is a new field: 𝘴𝘱𝘦𝘤:  𝘵𝘰𝘬𝘦𝘯𝘙𝘦𝘲𝘶𝘦𝘴𝘵𝘙𝘦𝘯𝘦𝘸𝘢𝘭𝘖𝘱𝘵𝘪𝘰𝘯:  𝘬𝘶𝘣𝘦𝘤𝘰𝘯𝘧𝘪𝘨𝘒𝘦𝘺𝘕𝘢𝘮𝘦: 𝘬𝘶𝘣𝘦𝘤𝘰𝘯𝘧𝘪𝘨 # 𝘴𝘢𝘮𝘦 Set 𝘬𝘶𝘣𝘦𝘤𝘰𝘯𝘧𝘪𝘨𝘒𝘦𝘺𝘕𝘢𝘮𝘦 to the existing key name and Sveltos overwrites the Secret in-place, skipping the spec update. Live state and Git stay aligned 2. 𝗦𝗸𝗶𝗽 𝗻𝗮𝗺𝗲𝘀𝗽𝗮𝗰𝗲 𝗰𝗿𝗲𝗮𝘁𝗶𝗼𝗻 𝗳𝗼𝗿 𝗿𝗲𝘀𝘁𝗿𝗶𝗰𝘁𝗲𝗱 𝗥𝗕𝗔𝗖 In multi-tenant clusters where Sveltos operates without cluster-wide Namespace permissions, the pre-flight namespace check would fail even when the namespace already existed. 𝘚𝘬𝘪𝘱𝘕𝘢𝘮𝘦𝘴𝘱𝘢𝘤𝘦𝘊𝘳𝘦𝘢𝘵𝘪𝘰𝘯: 𝘵𝘳𝘶𝘦 on 𝘗𝘰𝘭𝘪𝘤𝘺𝘙𝘦𝘧s and 𝘒𝘶𝘴𝘵𝘰𝘮𝘪𝘻𝘢𝘵𝘪𝘰𝘯𝘙𝘦𝘧𝘴 bypasses that check and deploys directly into pre-provisioned namespaces. 3. 𝗡𝗮𝘁𝗶𝘃𝗲 𝗛𝗲𝗹𝗺 𝘁𝗲𝘀𝘁 𝗲𝘅𝗲𝗰𝘂𝘁𝗶𝗼𝗻 Helm charts ship with test hooks that authors write precisely to validate a deployment. With 𝘳𝘶𝘯𝘛𝘦𝘴𝘵𝘴: 𝘵𝘳𝘶𝘦 in the chart spec, Sveltos runs those hooks automatically after each successful install or upgrade. Failures surface as deployment failures in ClusterSummary status. 𝗕𝘂𝗴 𝗳𝗶𝘅𝗲𝘀 𝘄𝗼𝗿𝘁𝗵 𝗻𝗼𝘁𝗶𝗻𝗴 Modifying Helm patches no longer goes undetected when chart version and values are unchanged. Sveltos now tracks a hash of the patch set. Failure messages on Helm releases are no longer overwritten before persisting. And manually deleting a ClusterSummary while a cluster is mid-update no longer causes a reconciliation deadlock. Full changelog: https://lnkd.in/d65DAXuA #Kubernetes #MultiCluster #GitOps #PlatformEngineering #Sveltos

Typed “guthib” instead of GitHub today… and landed somewhere I definitely didn’t expect. 😄 It’s funny how in tech, even a single misplaced letter can completely change the outcome—whether it’s a search, a command, or a line of code. Moments like these are small, but they reinforce an important habit: being mindful of the details. Because in our field, precision isn’t optional—it’s everything. Sometimes the best reminders don’t come from big failures, but from tiny slips like this. Back to typing carefully… one character at a time. #DeveloperLife #CodingLessons #AttentionToDetail #TechJourney #GitHub

I set up a GitHub Actions pipeline! 🚀 Now, every time I push code to the main branch, my application automatically redeploys to my Hostinger VPS. No more manual SSHing or dragging files—just clean, automated CI/CD. If you’re looking to level up your deployment game, I highly recommend checking out the video I followed. I've linked it in the first comment below! #Docker #GithubActions #DevOps #MERNStack #Hostinger #LearningInPublic #WebDevelopment #CodingLife

Over the past year, we at Independence Blue Cross have deployed GitHub Copilot to our technology teams and it has become a valuable force multiplier for our development teams and has helped us deliver more for less. By accelerating boilerplate coding, surfacing patterns faster, and reducing context-switching, developers focus more time on business problem-solving and higher-value work. Thanks to Larry Reeve, Robert Pruett, Timothy O'Malley, Mark Taylor #DeveloperProductivity #GitHubCopilot #AIinEngineering #SoftwareDevelopment #DevEfficiency

Shipping faster starts with one integration. Connecting GitHub to Vercel takes less than 2 minutes, and it changes everything about how you share your work. Every pull request gets its own live preview URL. Automatically. No extra config, no manual deploys, no "can you send me the build?" messages. Here's what you unlock instantly: ⚡ Preview deployments on every PR, shareable with one link ✅ Stakeholders review real UI, not screenshots 🎯 Feedback loops cut from days to minutes 🔗 Production deploys triggered automatically on merge 🛡️ Zero risk of showing unfinished work on your main domain I use this on every project now. A designer, a client, or a PM can click a link and see exactly what the feature looks like, before it ships. No staging server. No "works on my machine." Just a URL. Have you tried Vercel preview deployments yet? What changed in your workflow when you did? #Vercel #GitHub #WebDevelopment #DeveloperExperience #DevOps

devpath-idp | Phase 6 update — Backstage self-service provisioning — I said I'd share more on the scaffolder issue when I had a cleaner picture. Here it is. After going back and forth on it, I realised I was starting to loop — re-proving things I'd already proven. So I stopped and took stock of what was actually confirmed. Here's where Phase 6 actually landed: ✅ The template works ✅ Backstage creates the GitHub repo successfully ✅ The GitHub token is valid — manual push with the same token works perfectly ✅ Repo creation and GitHub authentication are not the problem The one thing that doesn't work: Backstage's internal push step times out in local development. The repo gets created, but the scaffolded files don't make it in. That's a specific, isolated limitation. Not a failure of the whole phase. In a real production setup, this timeout behaviour is less likely to be an issue — local dev mode introduces constraints that don't exist in a properly deployed environment. But documenting it honestly is part of the work. So the Phase 6 conclusion is: Backstage self-service provisioning partially works. Repo creation is proven. The push step has a known local dev timeout. The limitation is understood and isolated. That's good enough to move forward. There's something worth saying about knowing when to stop debugging. Not every issue needs to be fully resolved before you move on. Sometimes the right call is to understand the problem clearly, document it honestly, and keep building. Moving on to the next phase. #Backstage #PlatformEngineering #DevOps #InternalDeveloperPlatform #GitHub #CloudEngineering #SoftwareEngineering

Day 26 – GitHub CLI (gh): Manage GitHub from Your Terminal Today I explored how to use the GitHub CLI to manage everything without leaving the terminal — from creating repos to handling PRs and issues. 💡 Key Learnings: Installed & authenticated gh Created and managed repositories directly from terminal Worked with issues (create, view, close) Created & merged pull requests without browser Explored GitHub Actions workflows using CLI Discovered powerful commands like gh api, gh alias, and gh search Biggest takeaway: No more context switching between terminal and browser — everything can be automated and managed efficiently using gh. #90DaysOfDevOps #DevOpsKaJosh #TrainWithShubham #GitHubCLI #DevOps #Automation #CLI #Git #LearningInPublic #CloudComputing #Scripting #DeveloperJourney