Skip to main content
100%

GitHub-Native Merge Automation — a complete replacement for merge-automation bots (Mergify/Kodiak/Bulldozer/Trunk/Aviator/Graphite/MergeFreeze/backport bots), with native config + CI recipes for each feature

✓ Published0🌍 Public
Aandrewxhill
Last edited Jul 17, 2026
Created on Jul 15, 2026

This example shows how to replace third-party merge-automation bots (Mergify, Kodiak, Bulldozer, Trunk, Aviator, Graphite, MergeFreeze, backport bots) using only GitHub-native features: auto-merge, merge queue, rulesets, and custom CI workflows. The code uses GitHub's GraphQL API (`enqueuePullRequest`) for eligibility-gated enqueueing, YAML workflow files for the `ci` job and `merge_group` event handling, and shell/gh CLI commands for configuration. It covers architecture, plan requirements, queue batching and bisection, freeze windows, and backport recipes.

AI-generated description

Similar vizzes

Loading thumbnail…

automerge-repo auth spec

This example shows the authentication and sharing workflow for Automerge Repo, a local-first collaboration framework, using the `@localfirst/auth` library. It demonstrates how to configure a `LocalFirstAuthProvider` with user and device credentials, create and join shares, invite members and devices, and manage document permissions. The code uses TypeScript APIs like `createUser`, `createDevice`, `inviteMember`, and `addDocuments`, with invitations relying on seeds, usage limits, and expiration timestamps. The documentation is rendered as a pseudocode specification, not a live visualization, but it concretely maps each method call to its parameters and return values.

HHerbCaudill
61% match
Loading thumbnail…

draft readme for automerge repo

This example visualizes the architecture of a proposed Automerge repository API through a plain-text code listing. It shows the core data flow and plugin interfaces for storage, networking, and middleware, using TypeScript and Automerge’s CRDT library. The rendering relies on the raw code blocks themselves, highlighting API method signatures like `AutomergeRepo.createRepo`, `wrappedDoc.addListener`, and `storage.appendChange`. The visualization maps the conceptual layers of the API, from public document operations to internal plugin contracts, without any graphical charts.

HHerbCaudill
61% match
Loading thumbnail…

Gist 859941ebbbd6686689c4c870c1e5cf18

This example demonstrates a chained asynchronous workflow that reads a GitHub username from a local file, fetches the corresponding GitHub profile via the GitHub API, and writes the profile data as JSON to another file. It uses the Promise-based functions `pluckFirstLineFromFile`, `getGitHubProfileAsync`, and `asynWrite`, structured with `then` and `catch` handlers to manage data flow and error logging. The code illustrates how to sequence file I/O and network requests without callback nesting, relying on async/await-style chaining through native JavaScript Promises.

MMailnickko
59% match
Loading thumbnail…

Merge vs. Rebase vs. Squash

This visualization compares three Git workflows—merge, rebase, and squash—by rendering commit histories as branching node-link diagrams. It uses D3’s `d3.forceSimulation` to position commits and `d3.line` or path generators to draw edges, with each strategy shown as a separate panel. The data comes from a gist by ackuser describing situational preferences, and the code encodes commit order, merge points, and squashed clusters directly from that narrative. Interactive hover or click events highlight individual commits, revealing the author’s rationale for each approach.

Aackuser
59% match
Loading thumbnail…

The Gist to Clone All Gists

This example demonstrates a practical workflow for backing up or synchronizing a GitHub user’s public gists. It first clones every gist from a specified GitHub account over SSH, using a paginated API fetch to retrieve the list of gists and the Node.js `https` module to authenticate via an OAuth token. It then shows a complementary bash script that iterates through local directories, committing any changes with an empty message and pushing them back to their remote origins. The visualization highlights the interplay between the GitHub REST API and command-line Git operations for batch repository management.

Mmbostock
57% match
Loading thumbnail…

Gist 1a9660527e35cdeba43b

This example visualizes a Git branching and merging workflow as a sequence of command blocks, showing each step from checkout through commit and merge. The code uses d3’s selection and transition methods to animate the blocks appearing in sequence, with text labels for branch names and commit messages. It renders as a simple timeline of styled HTML divs, where the data—the list of shell commands—is embedded directly in the markup and driven by d3’s data join. The visualization emphasizes the order and syntax of typical Git operations without simulating actual repository behavior.

LLayne Smith
57% match
Loading thumbnail…

Normative git branching model based on rebasing and best practices

This example presents a normative Git branching model that emphasizes rebasing and best practices for maintaining a clean, deployable `master` branch. The visualization, authored by alper in a gist, illustrates the workflow through a simple diagram and accompanying text, showing how feature branches are created, rebased, and merged using `git merge --no-ff`. It also includes a flowchart-like representation of the process, with commands such as `git rebase`, `git pull`, and `git push --force-with-lease`, and references GitHub’s pull-request workflow. The data source is the gist’s markdown content, rendered as static images.

Aalper
57% match
Loading thumbnail…

How to make git repo to be another's repo subfolder preserving history

This example shows a multi-step Git workflow for relocating an existing repository (`Proto`) into a subfolder of another repository (`Main`) while preserving full commit history. It demonstrates the use of `git checkout --orphan`, `git rebase`, and the history-rewriting command `git filter-branch --tree-filter` to move all files into `SRC/proto` across every prior commit. The process also addresses hidden files (like `.editorconfig`) and explains how to merge the two repositories via `git remote add` and a final `git rebase`. The source is a plain-text markdown guide with shell commands.

RRestuta
56% match