This is a small tool that helps you interface with githubarchive.org It provides utilities to fetch specific archives, or fetch a range of archives via date. You can then run some semi-complex queries on the downloaded archives, which are still in gz format. Try running help to see information of each command, and subcommands.

gar 0.2.0
Simon psyomn Symeonidis <[email protected]>
Github Archive interfacing and querying tool

USAGE:
	gar [FLAGS] [SUBCOMMAND]

FLAGS:
    -h, --help       Prints help information
    -v, --version    show the current version

SUBCOMMANDS:
    fetch    for fetching singular files
    help     Prints this message
    query    for running queries on the retrieved data
    show     for printing different program information

Let's take a look at simple fetching commands:

gar-fetch
for fetching singular files

USAGE:
	gar fetch [FLAGS] [OPTIONS] [SUBCOMMAND]

FLAGS:
    -h, --help       Prints help information
    -V, --version    Prints version information

OPTIONS:
        --file <file>    the date in YYYY-mm-dd-h format

SUBCOMMANDS:
    help     Prints this message
    range    for fetching from certain dates

You can fetch one file this way:

gar fetch --file 2014-1-1-1

Or if you want a specific range:

gar fetch range --from 2013-1-1-1 --to 2013-1-5-1

You can run simple queries this way:

gar-query
for running queries on the retrieved data

USAGE:
	gar query [FLAGS] [OPTIONS]

FLAGS:
    -h, --help       Prints help information
    -V, --version    Prints version information

OPTIONS:
    -f, --from <from>            specify query date in YYYY-mm-dd-h format
    -s, --select <select>        specify which fields to output
    -m, --template <template>    specify handlebar template for output
    -t, --to <to>                specify query date in YYYY-mm-dd-h format
    -w, --where <where>          specify selection constraints

Here is an example of a query:

gar query --where language:Rust,type:create

This will search for all events, and select only the events where the repository is of the Rust language, and the type of event is a CreateEvent. You can also specify time constraints with to and from:

gar query --where language:Rust,type:create --from 2013-1-1-1 --to 2013-1-5-1

And as you noticed you can also provide a type of event, and language using the --where clause. The way you do this, is by providing a label, delimited with a colon : and provide the value. For example:

language:Rust

Satisfies this query. You can add more constraints by delimiting them with a comma ','. The relevance of a comma in this case is as if it's a logical AND. As you previously saw:

language:Rust,type:create

Here's the list of things you can add as constraints:

These are the event types you can capture using these labels:

• language:value, where value is the exact name of the language (case sensitive)

• owner:value, where value is the exact name of the owner (case sensitive)

• name:regex-value, where value is the (part) name of the repository (regex)

• description:regex-value, where value is part of the comments, with a regex match

• +watchers:value, where value is an integer. Matches against repos which have watchers more than or equal to the given value.

• -watchers:value, where value is an integer. Matches against repositories which have less watchers than the value provided.

• +stargazers:value,-stargazers:value, same as watchers above.

• type:event-type where event-type is:

  • create
  • commit_comment
  • delete
  • deployment
  • deployment_status
  • download
  • follow
  • fork
  • fork_apply
  • gist
  • gollum
  • issue_comment
  • issues
  • member
  • membership
  • page_build
  • public
  • pull_request
  • pull_request_review_comment
  • push
  • release
  • repository
  • status
  • team_add
  • watch

• commit_comment:, where value is the text to be matched, case insensitive against the given commits. This will only work against event types of push.

You can format your output with a handlebar template. That is, each time that something is found, a handlebars template is used, and is printed in the stdout this way. Maybe this will change in the future. Also for the time being, payloads are not printed in the output of handlebar templates, another feature that might be added in the future. Essentially you should look for certain things in events, and get the information of that repo, by piping to file.

Example:

Your handlebar template:

    ==== Some entry ======================
    The repo name is {{ name }}
    The repo id is {{ id }}
    The repo url is {{ url }}
    ======================================

And your query should look like this:

    gar query --where language:Rust --template /tmp/temp.hbs

Which should give you output like this:

    ...
    ==== Some entry ======================
    The repo name is rust
    The repo id is 724712
    The repo url is https://github.com/mozilla/rust
    ======================================
    ==== Some entry ======================
    The repo name is rust
    The repo id is 724712
    The repo url is https://github.com/mozilla/rust
    ======================================
    ==== Some entry ======================
    The repo name is rust
    The repo id is 724712
    The repo url is https://github.com/mozilla/rust
    ======================================
    ...

Here are the labels you can use in your handlebars template:

• id
• name
• description
• language
• has_issues
• owner
• url
• watchers
• stargazers
• forks