A simple script to backup an organization's GitHub repositories, wikis and issues.

100%

A simple script to backup an organization's GitHub repositories, wikis and issues.

✓ Published0🌍 Public

Last edited Feb 22, 2016

Created on Sep 16, 2019

This example demonstrates a Bash script that automates the backup of an organization's GitHub repositories, wikis, and issues, using the GitHub API to fetch repository lists and `git clone --mirror` for repository backups. The script produces compressed archives via `tar`, while `curl` retrieves issue data. The backup process includes pruning of old archives, configured through shell variables and conditional checks.

AI-generated description

Similar vizzes

Loading thumbnail…

A simple script to backup an organization's GitHub repositories, wikis and issues.

JJustinGOSSES

100% 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…

Gist 1b72416b70ed6ab1957e78c94a754f91

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.

CCarlos-Augusto

58% match

Loading thumbnail…

Gist ea3c2dbb293136905194cfa2fa60cec8

This example demonstrates a shell script that automates the download and extraction of the latest Linux 64-bit geckodriver release. It shows how to query the GitHub API for the newest release, parse the download URL using `sed`, and pipe the archive directly into `tar` for extraction. The script relies on `curl` to fetch the API metadata and `wget` to retrieve the tarball, providing a one-liner workflow for staying up-to-date with geckodriver binaries.

HHerst

57% match

Loading thumbnail…

Quick script to help you find and deal with old watched repos, forks and owned repos.

This script demonstrates a command-line workflow for identifying and managing stale GitHub repositories from a user’s watched list. It sorts repos into four categories—your forks, your own repos, their forks, and their repos—based on ownership and fork status, then flags those not pushed to in over eight months. For each stale repo, it prompts the user to either unwatch (via the GitHub API’s `unwatch` endpoint) or delete (requiring a two-step confirmation with a delete token). The code uses Ruby’s `json`, `time`, and `highline` gems, plus `curl` to interact with GitHub’s API v2 JSON.

CCaged

56% match

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

56% match

Loading thumbnail…

a set of scripts to pull the git history from the d3 git repositories

This example provides a set of Node.js scripts that extract and consolidate commit history from the D3 GitHub repositories. The scripts clone each repository, use `git log` to output commit data with custom delimiters, parse that text into JSON, and combine results into a single `all-d3-commits.json` file containing author, date, and repository name for each commit. The data is sourced from D3’s package.json dependencies and can be used to visualize contributor activity over time.

CCurran Kelleher

55% match

Loading thumbnail…

Gist 10794

This example demonstrates a GitHub repository interaction system built with Ruby and the GNCommand event framework, showing how drag-and-drop actions on repository URLs trigger context-specific behaviors. The visualization highlights the branching logic that detects whether a dropped URL points to a repository, a tree, or a commit, with placeholder sections for handling forks, files, and users. The code uses the GNCommand API’s `:drop` event scoped to `github.com` and parses URL path components via `path.pathComponents`. While the rendering approach is not visible, the focus lies on the event-driven decision tree that maps URL structures to potential GitHub actions.

CCaged

53% match