Ali Chebel’s Post

We've all been there - staring at a production bug, wondering how we missed it in code review. As developers, we try our best, but we get tired, we're busy, and sometimes things slip through. GitHub had some nice AI code review integrations like Claude Agent and Cursor Agent, but for Bitbucket users, the options were limited. There was one tool that worked well, but at $12 per developer per month, it felt out of reach for smaller teams 💸 📍 So this is what I did: I created a simple open-source service that can be deployed anywhere to enable Bitbucket automated PR reviews: 🔒 Your code never leaves your infrastructure. Bitbucket webhooks trigger local analysis, keeping everything completely private - no third-party storage of your codebase. 💰 This approach can save teams up to 98% compared to enterprise solutions. This project is still very new. For anyone who wants to use it or even contribute, feel free to try it: 🔥 https://lnkd.in/g4b5rd4x I've created a Medium article explaining the details of the implementation and story, feel free to check it: 🔥 https://lnkd.in/gqe8CgE6 If you see any improvement—prompt ideas, libraries, papers, or gotchas—I’m very open to improvements, just let me know!  #OpenSource #Bitbucket #CodeReview #SoftwareEngineering #DevOps #AI

🚀 Recently integrated and using Google Gemini CLI with GitHub MCP Server – and it's a game changer for developers. Gone are the days of context-switching between your IDE, terminal, and GitHub. Now? Write a single prompt in plain English, and watch your code get written, committed, and pushed automatically. This integration is transforming my development workflow: ✅ Natural language to production code ✅ Automated Git operations ✅ Seamless GitHub integration ✅ Zero context switching The future of development isn't just about writing better code – it's about removing friction from the entire process. For developers still manually managing their Git workflow, this is worth exploring. The productivity gains are real. What AI tools are transforming your development workflow? Let's discuss in the comments. This is what the future of development looks like. Ameen Alam Ali Jawwad Ahmed A. Hafiz Ali Ahmed #AI #GitHub #DeveloperProductivity #GoogleGemini #AI #DeveloperTools #GitHub #GoogleGemini #Productivity #SoftwareDevelopment #CodeAutomation #TechInnovation

🚀 Building Smarter with GitHub Actions + GitHub Copilot I recently set up a complete CI/CD pipeline using GitHub Actions, and I’m genuinely amazed by how seamless automation can be when paired with GitHub Copilot 🤖 Here’s what I built: ✅ Continuous Integration: Automatically runs tests and lint checks on every push or pull request. ✅ Continuous Deployment: Deploys successful builds straight to staging — no manual steps. ✅ GitHub Copilot: Helped me write clean YAML workflows, optimize test scripts, and even catch small logic mistakes while coding. This setup has made development faster, more reliable, and far more enjoyable. Watching code go from commit → test → deployment automatically still feels like magic ✨ If you haven’t tried combining GitHub Actions and Copilot, it’s a game-changer for any developer looking to speed up their workflow. #GitHub #GitHubActions #GitHubCopilot #CICD #DevOps #Automation #AI #SoftwareEngineering #Productivity

𝗧𝗶𝗻𝘆 𝗖𝗵𝗮𝗻𝗴𝗲, 𝗕𝗶𝗴 𝗜𝗺𝗽𝗮𝗰𝘁 𝗶𝗻 𝗖𝗜/𝗖𝗗 𝗣𝗶𝗽𝗲𝗹𝗶𝗻𝗲 🚀 Today, I made a small but critical improvement to my GitHub Actions workflow a great reminder that even one line of YAML can make your automation easy and smooth... 🔧 𝗪𝗵𝗮𝘁 𝘄𝗮𝘀 𝘁𝗵𝗲 𝗖𝗵𝗮𝗻𝗴𝗲? I tightened the workflow triggers to run only when relevant files change, cutting down unnecessary pipeline runs. And I added this small but impactful line: 𝘧𝘦𝘵𝘤𝘩-𝘥𝘦𝘱𝘵𝘩: 0 to my actions/checkout step, ensuring the full Git commit history is fetched during each run. 💡 𝗪𝗵𝘆 𝗧𝗵𝗶𝘀 𝗠𝗮𝘁𝘁𝗲𝗿𝘀 By default, GitHub Actions performs a shallow clone fetching only the latest commit. That means there’s no HEAD^ (previous commit) available, which breaks commands like: 𝘨𝘪𝘵 𝘥𝘪𝘧𝘧 𝘏𝘌𝘈𝘋^ 𝘏𝘌𝘈𝘋 or any workflow logic that compares the current commit with its parent. With fetch-depth: 0, we now get the complete Git history, enabling accurate diffs, changelogs, and versioning logic across our pipeline 🧠 𝗞𝗲𝘆 𝗧𝗮𝗸𝗲𝗮𝘄𝗮𝘆 Improving a CI/CD pipeline isn’t always about big refactors or something crazy, sometimes it is about understanding how your tools behave under the hood. One line, one insight, and you’ve just made your automation faster, leaner, and smarter! #DevOps #GitHubActions #CI/CD #Automation #SoftwareEngineering #GitTips #ContinuousIntegration #ContinuousDeployment #YAML #CloudNative #PlatformEngineering #DeveloperExperience #InfraAsCode #PipelineOptimization #BuildAutomation #EngineeringExcellence #TechLeadership #UAE #FeynmanLearns #LearningByDoing

🚀  Stop refreshing GitHub Actions. Get deployment notifications via SMS. Context switching kills your flow state — and nothing breaks focus like staring at a CI/CD screen waiting for “✅ Success.” Here’s how I fixed it permanently in under 5 minutes. 👇 Most devs (me included) used to refresh GitHub Actions like maniacs. Now I get a text the moment a deployment finishes — no browser tabs, no guessing, no wasted time. 💡 The setup:  name: Send deployment notification  run: |   curl -X POST https://textbelt.com/text \    --data-urlencode phone='${{ secrets.TEXTBELT_PHONE }}' \    --data-urlencode message='✅ Deployment complete' \    -d key='${{ secrets.TEXTBELT_API_KEY }}' ✅ Add two secrets: your phone + API key ✅ Costs ~$0.01 per text ✅ Works perfectly for prod deploys, CI/CD runs, ML model training, or weekend maintenance Why this matters: ⚙️ Zero context switching 🔔 Instant failure alerts 💵 Costs less than a cup of coffee per month 🧠 Preserves your mental focus and shipping rhythm The best debugging? Knowing something failed the moment it happens — not hours later. What repetitive task are you still manually monitoring? Drop it below 👇 — I’m building a list of “one-line automations” that save devs real time. #DevOps #GitHub #Automation #DeveloperProductivity #CI/CD #CodingTips

My GitHub Actions pipeline helps me focus on the building and automates the rest - deploying full stack apps in under 2 minutes.⏱️✨ It's a two-in-one system: 🛡️ The Gatekeeper (on PRs): Spins up a Postgres DB to run unit and integration tests. Only clean code passes! 🚀 The Automaton (on Merge): 🔹Intelligently bumps the version (major, minor, or patch) by reading my commits. 🔹Auto-generates the CHANGELOG and generates a new GitHub Release. 🔹Builds frontend + backend Docker images in parallel. ⚡ 🔹Deploys to my private server and runs health checks to make sure everything is live. 🔹Finally, notifies me once done! From pull request to a versioned, live deployment—all with zero manual steps. What's the coolest automation you've built into your own CI/CD pipeline? Follow for more: Animikh Aich #GitHubActions #CICD #DevOps #Automation #Docker #SoftwareEngineering

🚀 Git isn’t just version control — it’s your time machine. Every Data Engineer, Developer, and Analyst should know these Git commands by heart — because one wrong commit can cost you hours (or your sanity 😅). Here are the essential Git commands you’ll use daily 👇 💻 git init → Start a new repo — your project’s first heartbeat. 🧩 git add . → Stage all your changes (like bookmarking your progress). 💬 git commit -m "message" → Commit with a story. 🔍 git status → Know exactly what’s changed. 🕵️♂️ git diff → See the difference before committing. 🌿 git branch <name> → Create a new idea lane. ↔️ git checkout <name> → Switch between your worlds. ⚡ git merge <branch> → Bring ideas together. ☁️ git push / git pull → Sync your local magic with the world. 🧠 git stash → Hide your messy changes temporarily. 💡 Pro tip: Learn to visualize Git as a timeline, not a tool. It’ll change how you code and collaborate forever. #Git #GitHub #VersionControl #DataEngineering #SoftwareEngineering #LearningInPublic #CareerGrowth

I just published a complete step-by-step guide on how to connect GitHub MCP with Gemini CLI, generate a project, and publish it directly from the terminal. If you’ve ever wanted to automate repo creation, commits, and pushes using AI, this walkthrough will save you a lot of time. I covered everything from creating the right GitHub token to setting up the MCP server, verifying the connection, generating files, and finally publishing the repo. If you're into AI tools, automation, or developer workflows, you’ll enjoy this one. Would love to hear your feedback. Here’s the full guide: https://lnkd.in/dhCzqWzw Ameen Alam Muhammad Qasim Daniyal Nagori Zia Khan Hamzah Syed Fahad Khan Asharib Ali Aneeq Khatri Ali Jawwad Nida Rizwan Muhammad Ahsaan Abbasi Muhammad Junaid Shaukat Wania Kazmi Governor Sindh Initiative for GenAI, Web3, and Metaverse #GeminiCLI #GitHubMCP #DeveloperTools #Automation #AIforDevelopers #CodingWorkflow #GitHub #GeminiAI #DevCommunity

Quick #GitHubActions Tip: Watch Out for System PATH Resets! If you're using self-hosted runners, here's something that might catch you off guard: GitHub Actions resets the system PATH when executing jobs, which can break your workflow if you've pre-installed dependencies on your runner. Real-world example: 1. You pre-install cargo on your runner to prepare for Rust builds 2. Test it with `cargo version` - works perfectly! 3. Use GitHub Actions using your new runner to execute `cargo build` 4. 😱 Error: `cargo: command not found` The fix is simple but not obvious. Before running cargo commands in your GitHub Action, edit the $GITHUB_PATH variable to append to the system PATH: 𝗯𝗮𝘀𝗵 𝗲𝗰𝗵𝗼 "/𝗿𝗼𝗼𝘁/.𝗰𝗮𝗿𝗴𝗼/𝗯𝗶𝗻" >> "$𝗚𝗜𝗧𝗛𝗨𝗕_𝗣𝗔𝗧𝗛" Problem solved! 🎉 #DevOps #GitHubActions #ContinuousIntegration #Rust #TechTips

🚀 Just Automated My First CI/CD Pipeline Using GitHub Actions! Ever wondered how your code goes from “push to main” → live on server in seconds? 🤔 That’s exactly what I explored in my latest project — Automating Code Deployment for a Node.js App using GitHub Actions and Docker. 🧑💻 Here’s what I built 👇 🔹 A Node.js demo app 🔹 A .yml workflow in .github/workflows/main.yml 🔹 Pipeline stages: Test → Build → Dockerize → Push to DockerHub → Deploy 🔹 Triggered automatically on every code push 🔹 Secrets securely managed using GitHub Secrets 🔒 🎯 Goal: Understand the complete CI/CD automation process — from writing code to seeing it deployed automatically! 💡 What I learned: ✅ How CI/CD works behind the scenes ✅ What runners, jobs, and steps really do ✅ How to automate Docker build & push workflows ✅ How to handle deployment errors like a pro 😎 🎥 Check out my short demo: “CI/CD using GitHub Actions” (Watch how the entire pipeline automates the deployment process!) Now I’d love to hear from you 👇 💬 Have you tried setting up a CI/CD pipeline before? 💭 What tools do you prefer — GitHub Actions, Jenkins, or GitLab CI? #DevOps #GitHubActions #CICD #Docker #Nodejs #Automation #CloudComputing #LearningByDoing #AdeshJavir #DevOpsJourney