New Public Gist

100%

New Public Gist

✓ Published0🌍 Public

Last edited Jan 29, 2017

Created on Jan 29, 2017

This example shows the top 165 GitHub repositories for the ServiceStack organization, sorted by watcher count, by fetching JSON data from the GitHub API. The code uses the `GetJsonFromUrl` method with a custom User-Agent to retrieve the repository list, then parses it with `FromJson<GithubRepository[]>` and orders it via `OrderByDescending`. The result is printed as a top-five list and a full dump, leveraging ServiceStack.Text's `Print` and `PrintDump` utilities for console output.

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

55% match

Loading thumbnail…

Gist 8e4a7859bf351698daff

This example displays a collection of Git command-line snippets organized by workflow categories, with each command as a labeled node. The visualization uses D3.js to render these commands as interactive text elements, applying a force-directed layout to spatially group related commands like repository creation, branching, and syncing. The code references `d3.forceSimulation` for positioning nodes and includes the raw command strings from a public Gist, with no external data fetching. Each node displays its command syntax and a brief comment, while the layout dynamically adjusts to avoid overlap based on the text content.

LLayne Smith

55% match

Loading thumbnail…

Gist API Latency

This histogram visualizes the distribution of GitHub Gist API response times in milliseconds for 10,000 requests, broken down by endpoint type: single-gist queries (light blue) versus user-gist listings (dark blue). The stacked bars reveal that the slow tail of the distribution comes almost entirely from the listing endpoint. The chart is rendered as SVG using D3 v3, with `d3.scale.linear`, `d3.svg.axis`, and data loaded from a TSV file via `d3.tsv`. Axis labels and percentage annotations are drawn using SVG text elements.

Mmbostock

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

54% match

Loading thumbnail…

Gist db32a113f546aa03b43c0e1f84f80d28

The visualization shows a force-directed network graph of GitHub gist data, with nodes representing individual gists and links showing relationships between them. It uses d3.forceSimulation to compute the layout, with node size encoding gist size and color indicating file type or language. The rendering relies on SVG elements updated per tick via the simulation’s tick event. The code loads a static JSON file containing preprocessed gist metadata, and does not use canvas or WebGL. The visualization highlights clustering patterns among related gists, revealing emergent communities in the dataset.

335degrees

54% match

Loading thumbnail…

Gist 7a408ae6b97507c83e6613316e32a9c7

This example contrasts two JavaScript approaches for fetching GitHub user data from the GitHub REST API. It uses the Fetch API to request `https://api.github.com/users/mistyblunch` and logs the resulting JSON. The first method chains `.then()` callbacks in a Promise-based function, while the second defines an `async` function that uses `await` to handle the response and return the parsed JSON object. Neither function performs any visualization or rendering—only console output.

MMistyBlunch

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

54% match

Loading thumbnail…

Requesting data from the Github API

This example demonstrates the complete workflow of fetching repository data from the GitHub API and rendering it as an HTML list. It uses a raw XMLHttpRequest to request JSON from `https://api.github.com/users/razpudding/repos`, parses the response with `JSON.parse`, and then dynamically creates a `<ul>` element with `<li>` items for each repository name using the DOM methods `document.createElement` and `appendChild`. The visualization highlights the data pipeline from an asynchronous API call to interactive webpage content.

LLaurens

54% match