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

100%

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

✓ Published0🌍 Public

Last edited Jan 4, 2011

Created on Jan 4, 2011

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.

AI-generated description

Similar vizzes

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

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

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…

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

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.

JJustinGOSSES

56% match

Loading thumbnail…

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

JJustinGOSSES

56% match

Loading thumbnail…

Commit and push via Github REST API, from ruby RestClient

This example shows how to programmatically commit a file to a GitHub repository using the GitHub REST API, demonstrated through a Ruby script that performs the five-step Git data model workflow. The code uses the `rest-client` gem for HTTP requests and `JSON` parsing to interact with endpoints like refs, commits, trees, and blobs. It first retrieves the current master branch head, then creates a new tree with the updated file content, builds a commit referencing the prior tree, and finally updates the branch reference. The script relies on basic authentication via environment variables for `GH_USERNAME` and `GH_PASSWORD`.

HHugoberry

55% match

Loading thumbnail…

Gist Scraping Script Prototype

This prototype demonstrates a data migration workflow that iterates through every file within each GitHub Gist associated with a given username. The visualization shows the raw JSON structure of a Gist, including its metadata and file contents. The application uses the Octokit library to fetch Gist data from the GitHub API and displays example file entries such as `App.js`, `data.csv`, and `package.json`. This proof of concept is built with React and includes placeholder functions for generating identifiers and converting timestamps, though the actual migration logic is not yet implemented.

CCurran Kelleher

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

53% match