Commit and push via Github REST API, from ruby RestClient

100%

Commit and push via Github REST API, from ruby RestClient

✓ Published0🌍 Public

Last edited Jun 17, 2012

Created on Jan 25, 2018

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`.

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

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

58% match

Loading thumbnail…

Fetching Remove Password comments from Github. Using Power Query and R

This example visualizes a GitHub code search for commits that remove passwords, using a Power Query workflow that calls the GitHub Search API to collect matching commits and their file patches. The data flows through Power Query’s table expansion functions before being handed to an R script via `R.Execute`, where a regular expression pattern extracts only the removed lines from each patch. The final table retains the commit metadata and the cleaned removed-line text, omitting the original patch column. The visualization demonstrates a hybrid ETL pipeline combining GitHub’s REST API, Power Query’s M language, and base R string processing.

HHugoberry

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

55% match

Loading thumbnail…

8 steps to using someone's "seed / boilerplate" repo as the basis for another project / repo.

This example outlines an eight-step procedure for reusing a seed or boilerplate repository as the foundation for a new project. It demonstrates the workflow through a plain-text gist, showing how to clone the original repo, remove its git remote or history, create a fresh GitHub repository, and establish a new remote origin. The steps conclude with committing the starter code and pushing it to the new remote. No external visualization libraries or APIs are used; the content relies solely on command-line git operations.

GGRamirez2

55% match

Loading thumbnail…

Instructions to set up

This example shows a step-by-step guide for setting up a Jekyll blog, from installing required gems to pushing the final build to a GitHub repository. It demonstrates a command-line workflow using `gem install`, `bundle install`, and `bundle exec jekyll build`, with plain-text instructions and code blocks. The visualization relies on a gist authored by Jverma, presenting the setup as a linear sequence of terminal commands and file actions. It does not use any charting or rendering libraries, focusing instead on a textual, procedural format.

JJverma

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

53% match

Loading thumbnail…

Gist 77879

This example demonstrates a Flickr photo management system built with Ruby on Merb, using the Flickr API to fetch, validate, and update photo metadata. It shows a batch workflow that first retrieves photos by category tags, then verifies their existence and tags on Flickr, and finally updates stored attributes like title, description, and image sizes. The code relies on Flickr’s `flickr_photo` objects and the Merb ORM for database persistence, with tasks chained via Rake. The visualization highlights the procedural data-sync logic, emphasizing error handling and association management between photos and categories.

DDylanFM

53% match