GitHub reliability incidents and improvements

Good Friday is a day of rest — your deployments deserve one too. While your team takes a well-earned break this holiday weekend, NoShip keeps your codebase safe with automated code freezes. Set up recurring freeze schedules so merges are blocked before anyone even thinks about pushing to prod on a long weekend. Because the only thing that should be rising this Easter weekend is your uptime. #GoodFriday #Easter #DevOps #GitHub #CodeFreeze #SRE #PlatformEngineering #DeploymentSafety #EngineeringLeadership

🚨 Is GitHub's reliability hurting your team? I've been talking with many customers recently, and a common theme keeps coming up — frustration with GitHub's service health. Outages, degraded performance, and uncertainty around uptime are slowing teams down. If that sounds familiar, there's a path forward. In 3 days, I'll be running a free workshop walking through how to migrate from GitHub to GitLab — step by step, no guesswork. You'll leave with a clear migration plan, practical tips, and confidence to make the switch. 👉 Interested? Join us here: https://lnkd.in/d-ckV-9G Quinten Dismukes, Colin Stevenson, Thiago Magro, Adrian Tigert #GitLab #GitHub #DevOps #Migration #Workshop

Just came across a simple diagram which clearly represents the flow of docker under the hood. I would like to add few points to it. If I would like to consider as 2 steps like : Step-1: Talking to Daemon Step-2: From Daemon Here are some useful beginner friendly commands: Step-1: To Daemon 1. docker version: to check if client and docker are communicating 2. docker build: Tells daemon to look at localhost's Dockerfile and assemble an image 3. docker run: Tells daemon to create and start a container. 4. docker log <container>: Asks daemon to retrieve history from a specific container Step-2: From Daemon 1. docker pull: Daemon reaches out to registry, finds the image, and downloads it to host 2. docker images: Daemon provides a list of all images stored on local host 3. docker push: Daemon takes a local image and uploads it to registry 4. docker ps: Daemon reports back on all containers that it is supervising Simply, Step-1 helps to make decisions, while step-2 helps to move files and start processes. Thanks Soham Naik for the most simplest breakdown about docker.

I started by building the infrastructure for my To-Do App using Terraform and Ansible, and then added a full CI/CD pipeline using GitHub Actions and Docker. What it does: First, Terraform creates the server (VPC, Subnets, ElasticIP, Security Groups, etc) and network automatically. Then Ansible sets up the server, Git Runner, installs Docker, and prepares the environment. After that, CI/CD handles the deployment. When I push code to GitHub main branch, GitHub Actions builds the app, creates a Docker image, and pushes it to Docker Hub. After that the server pulls the latest image, stops the old container, and starts the new one automatically. It also keeps only the latest 5 images to save space. Why this is useful: This removes manual work, reduces errors, and makes deployment faster and more reliable. What I learned: This project helped me understand how infrastructure setup and deployment automation work together in real DevOps. Special thanks to my supervisor Sampath D. for the guidance and support. #DevOps #Terraform #Ansible #Docker #GitHubActions #CICD #InfrastructureAsCode #CloudComputing #Automation #SoftwareEngineering #DevOpsJourney #LearningByDoing #TechProject #PortfolioProject #FutureEngineer #AWS #CloudArchitecture #OpenToWork #ITStudent #ContinuousDeployment #antlerfoundry

Easter Sunday is not the time to find out your deploy pipeline is still open. We've all seen it. A PR gets merged late Friday "just to get it in." By Sunday someone's getting paged. The on-call engineer is not happy. NoShip lets you set a recurring freeze that kicks in automatically every holiday weekend. Define the window once, and GitHub enforces it. No Slack reminders. No honor system. No "I thought someone else handled it." Set it. Forget it. Enjoy the long weekend. #DevOps #GitHub #CodeFreeze #SRE #PlatformEngineering #DeploymentSafety #Easter

Migrating from Bitbucket to GitHub is rarely just a repo transfer. It's tempting to treat it as a lift-and-shift. The truth is, the technical migration is the straightforward part. It's everything around it that matters: → Migrating repositories (the easy part) → Rethinking pull request workflows → Refactoring Bitbucket Pipelines into GitHub Actions → Reviewing security models and permissions → Evaluating integrations (Jira, Bamboo, marketplace apps) The opportunity? That's where the real value is: ✔ Cleaner CI/CD ✔ Stronger DevSecOps practices ✔ Simplified tooling ✔ Better developer experience The most successful migrations treat it as transformation, not translation. Furō Delivery Manager Shawn St Mart shares his insights on where the effort sits, where the value is, and how to sequence it right. ⬇️ Link in comments! #GitHub #GitHubMigration #DevSecOps #PlatformEngineering #Furō #Bitbucket

There’s a persistent misconception that platform migrations are primarily a technical exercise. In reality, they’re organisational inflection points. The move from Bitbucket → GitHub isn’t just about repositories or pipelines - it’s about rethinking how engineering teams collaborate, how security is embedded, and how delivery is standardised at scale. What we’re seeing across clients is consistent: the real value comes from the decisions made around the migration - not the migration itself. I’ve shared some of these perspectives and practical takeaways in the post below 👇

Kubernetes CLI Deep Dive [Part C] You can get all the commands from this GitHub Repo: https://lnkd.in/d4RHyn99 It'd be great if you follow me on GitHub 😍 #kubernetes #k8s #devops #devopsmolvi #cli #terminal

A lot of developers rely on GitHub every single day, but the moment you ask them how it truly differs from GitLab, the answers often get blurry. And honestly, I understand why, on la surface they look similar, yet they don’t serve the same vision at all. GitHub has become the place where the world writes code together. Backed by Microsoft and fueled by a massive open-source community, it’s built for speed, simplicity, and collaboration. Actions, Codespaces, Dependabot… everything is designed to help teams move quickly and stay focused on building. GitLab, on the other hand, follows a completely different philosophy. It’s not just a code platform, it’s a full DevSecOps environment. CI/CD is built-in, security tools are native, governance is centralized, and you can even self-host it with the open-source edition. Many companies choose it because they want one platform to manage everything from planning to deployment. So the question isn’t really “which one is better?”. It’s more like “which vision matches the way you work?”. One focuses on velocity and massive adoption. The other focuses on deep integration and full end-to-end control. If you’ve used either platform in your projects, I’d really love to hear your experience. What actually makes a difference in your daily workflow? And what would you pick again if you had to start from scratch? Your insights will definitely help others who are still trying to choose the right tool. #GitHub #GitLab #DevOps #DevSecOps

A lot of developers rely on GitHub every single day, but the moment you ask them how it truly differs from GitLab, the answers often get blurry. And honestly, I understand why, on la surface they look similar, yet they don’t serve the same vision at all. GitHub has become the place where the world writes code together. Backed by Microsoft and fueled by a massive open-source community, it’s built for speed, simplicity, and collaboration. Actions, Codespaces, Dependabot… everything is designed to help teams move quickly and stay focused on building. GitLab, on the other hand, follows a completely different philosophy. It’s not just a code platform, it’s a full DevSecOps environment. CI/CD is built-in, security tools are native, governance is centralized, and you can even self-host it with the open-source edition. Many companies choose it because they want one platform to manage everything from planning to deployment. So the question isn’t really “which one is better?”. It’s more like “which vision matches the way you work?”. One focuses on velocity and massive adoption. The other focuses on deep integration and full end-to-end control. If you’ve used either platform in your projects, I’d really love to hear your experience. What actually makes a difference in your daily workflow? And what would you pick again if you had to start from scratch? Your insights will definitely help others who are still trying to choose the right tool. #GitHub #GitLab #DevOps #DevSecOps