Gist 1b72416b70ed6ab1957e78c94a754f91

100%

Gist 1b72416b70ed6ab1957e78c94a754f91

✓ Published0🌍 Public

Last edited Aug 19, 2021

Created on Aug 19, 2021

This visualization demonstrates a shell script that cleans a Git repository by removing local branches whose remote counterparts no longer exist. It shows the process of fetching all remote branches, identifying branches marked as “gone” via `git branch -vv`, and deleting them with `git branch -D`. The example uses command-line Git APIs for repository management, with output reflecting the sequential execution of these operations. The rendering approach is plain text output from the terminal, illustrating the practical workflow for tidying up stale branches after many pull requests are merged.

AI-generated description

Similar vizzes

Loading thumbnail…

Gist 96829331ffd980ee6a4f3ab1196708f1

This visualization presents a structured Git cheat sheet, organizing commands into clear categories like configuration, local and remote branch management, and advanced operations. It demonstrates a comprehensive set of command-line workflows, including branching, merging, stashing, and comparing changes, each paired with practical usage examples. The rendering relies on standard Markdown code blocks and inline formatting to distinguish commands, comments, and options, providing a reference-style layout rather than a data-driven graphic.

JJaxonDvl

75% match

Loading thumbnail…

GIT delete merged branches

This example shows how to clean up a Git repository by deleting local branches that have already been merged into the current branch. It provides two implementations—one for Bash and one for Windows PowerShell—both using the `git branch --merged` command to list eligible branches, then filtering out protected branches like `master`, `main`, `dev`, and `develop` with `egrep` or `Where-Object`, and finally deleting the remaining ones via `xargs git branch -d` or `ForEach-Object { git branch -d }`. The code relies on standard Git command-line tools and does not use a charting library, as the “visualization” here is the terminal output of branch names before and after deletion.

IIvanBuljovcic

74% match

Loading thumbnail…

Gist 614541

This example visualizes a command-line prompt configuration that dynamically displays the current Git branch and working-directory status in color. It shows how the prompt turns red when uncommitted changes exist and green when the working directory is clean. The shell script uses `parse_git_branch` with `sed` and `awk`-style piping to extract branch names, while `check_git_changes` relies on `git status` and `tput setaf` to set terminal colors. The PS1 variable composes the final prompt, embedding the branch name and status indicator between the directory path and a colon. It relies on standard Bash and Git command-line tools, not a visualization library.

DDylanFM

71% match

Loading thumbnail…

Gist 9979190ea462c76d13e80def7b5aa3d8

This example demonstrates a Node.js script that checks whether the current Git branch is "master" before allowing a publish operation. It shows how to enforce a branch-based gate using the `execa` library to run `git symbolic-ref --short HEAD` and compare the output. The visualization highlights the workflow of validating Git state programmatically, with the script exiting with an error if the branch condition is not met. The code uses `execa.stdout` for asynchronous command execution, mirroring patterns from the `np` package. The rendering approach is text-based, relying on console output for success or failure.

HHypercubed

71% match

Loading thumbnail…

Gist 619560

This visualization loads a map using Polymaps and merges it with a local fork via a shell script. The code demonstrates a version-control workflow rather than a graphical output, as it logs git commands piping the `mbostock/master` branch into the local tree. The primary rendering relies on Polymaps’ tile-based mapping, while the surrounding repository management shows how to integrate external contributions. The example pairs a geographic data display with a practical Git merge, highlighting maintenance of a live mapping project through `git remote`, `fetch`, and `merge` operations.

Mmbostock

69% 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

68% match

Loading thumbnail…

git命令大全

This visualization presents a comprehensive cheat sheet of Git commands, organized as a text-based reference list. It shows the syntax and purpose of each command, ranging from repository initialization and configuration to branching, merging, and remote operations. The rendering relies on plain text formatting, with commands and their descriptions paired line by line, likely styled through CSS for readability. No graphical libraries or interactive elements are used; instead, the data source is the raw command list from the gist, displayed as a static, scannable document. The layout emphasizes quick lookup, with commands highlighted alongside their explanations.

JJoeycz

66% match

Loading thumbnail…

rename master to main

This example shows a step-by-step command-line sequence for renaming a Git repository’s default branch from `master` to `main` and updating the remote. The visualization presents the two-line `rename.bat` script, followed by comments explaining the need to change the default branch in GitHub’s settings before the final delete command can succeed. It uses the Git command-line interface (via `git branch`, `git push`, and `git push origin --delete`) to illustrate the workflow. The data source is the script itself, rendered as plain text without any graphical or programmatic visualization libraries.

HHerbCaudill

66% match