nowfound

Alternatives

Products that do what CI Governor does

Detect CI waste and flaky workflows in GitHub Actions

  1. 1

    Find flaky tests and wasted CI time in GitHub Actions

    May 2026

  2. 2IM
  3. 3

    Automate your workflow from idea to production

    2018 · github.com

  4. 4GW

    I've always wanted a better way to explore the authorship data embedded in a Git commit log. I'm having fun building a CLI tool to do this. It's a bit like the "Contributors" tab on Github that shows you how many commits each contributor has made but much faster and with many more options. If you get a chance to try it out, please let me know. I'd love to hear feedback and suggestions. Thank you!

    2025 · github.com

  5. 5

    Instantly visualize any codebase as an interactive diagram

    2025

  6. 6GB
  7. 7

    "If X, then do Y" for your GitHub repository

    2024

  8. 8
    Gitar103

    AI code review that fixes what it finds

    27d ago · gitar.ai

  9. 9GF
  10. 10AT

    Hi HN! I’ve been running GitHub Actions workflows for a while, and when GitHub announced the new ubuntu-slim runners as a cheaper alternative to ubuntu-latest, I wanted to migrate—but figuring out which workflows are safe to switch turned out to be surprisingly tedious. You need to check for Docker usage, services, containers, step failures due to missing packages, and whether jobs rely on tools not available in the slim image. So I built gh-slimify, a GitHub CLI extension that automates all of this. It scans your repository, detects which jobs can be migrated, flags incompatible patterns,…

    Nov 2025 · github.com

  11. 11PS

    Hey HN — I kept seeing developers describe the same frustration: the commit-push-wait-read-logs cycle when debugging CI pipelines. So I built PipeStep. PipeStep parses your GitHub Actions YAML, spins up the right Docker container, and gives you a step-through debugger for your run: shell commands. You can: 1. Pause before each step and inspect the container state. 2. Shell into the running container mid-pipeline (press I). 3. Set breakpoints on specific steps (press B). 4. Retry failed steps or skip past others. It deliberately does not try to replicate the full GitHub Actions runtime — no…

    Mar 2026 · github.com

  12. 12GB
  13. 13WG

    For the past month, we've been monitoring GitHub's public event stream to catch spam comments and fake stars. Today, the spammers are back. Go check out the damage! You can see the spam comments and which users are posting the spam in real time. Also, here's a post we wrote about how we set it up: https://www.trytrench.com/blog/preventing-spam-and-fake-star...

    2024 · play.trytrench.com

  14. 14

    AI-powered CI/CD failure analysis for GitHub Actions

    May 2026 · failbrief.com

  15. 15

    Catch GitHub Actions cost regressions before merge

    Aug 2026 · seba-montero.github.io

  16. 16IB

    I built a GitHub app that detects it in pull requests, notifies or blocks them. Alongside it, I published a Semgrep ruleset for any stage of the CI/CD. I started this after getting frustrated by all the FUD around malicious code - lots of noise, little effort to solve it. Having said that, it's still a major attack vector - a stored RCE, with the codebase itself as the sink. Feedback is appreciated. The app, PRevent - https://github.com/apiiro/PRevent The ruleset: https://github.com/apiiro/malicious-code-ruleset The research:…

    2025 · github.com

  17. 17

    One webhook. Every CI failure in one inbox.

    Jun 2026

  18. 18PT

    I've been trying to figure out how long feature development takes, for years. I'm not a fan of (a priori) estimations of work, which just seem like the wrong measure. I think I've got a better way. Genuinely interested if some git gurus can improve this. Particularly around the pre-push hook, which is dependent on retained squash commit text. Or if there's an entirely better way to achieve the same thing.

    2025 · doocot.sh

  19. 19GC

    I built a tool which you can use to visualise your git commits at an org or repository level. It shows just how much work an engineering team, or even an individual does, that often goes unseen by non-dev teams. You can read about the build here: https://ably.com/blog/visualize-your-commits-in-realtime-wit... Repo is here: https://github.com/ably-labs/github-commit-visualizer You can deploy your own to netlify (or provider of your choice) and start visualising your own project's commits in realtime.

    2022 · github-vis.ably.dev

  20. 20IC

    Hey HN, I built ShadowGit a while back to automatically commit code every minute to a hidden git repo (.shadowgit.git). Original goal was to easily rollback when AI tools break things. But I discovered something interesting: this minute-by-minute history is perfect context for AI assistants. So I built an MCP server that lets Claude/Cursor query this history using native git commands. The results surprised me: Before: Claude would read my entire codebase repeatedly, burning 15,000+ tokens to debug issues. After: Claude runs `git log --grep="drag"` finds when drag-and-drop worked,…

    2025 · shadowgit.com

  21. 21AC
  22. 22

    AI agent that fixes your failing GitHub Actions CI

    May 2026 · warpfix.org

  23. 23IB

    Hey HN, About a year ago I shared a first MVP of a visual node-based system for CI/CD pipelines that I've been very passionate about. I've been building on it since, and it's now live. I've always liked building pipelines and workflows, but I've never liked writing YAML for anything more than simple linear tasks. Branching, conditions, loops, or trying to just run certain things in parallel always gets messy. So I built Actionforge, a visual node system to tackle some of these pain points. Instead of writing YAML yourself, you build workflows as graphs. While Actionforge still uses YAML…

    Feb 2026 · actionforge.dev

  24. 24

    Analyze any GitHub profile instantly with AI

    2025

Ranked by how close each launch is in meaning, then by votes. Refine with a description →