Organization Repositories
Get meta data for all repositories belonging to an organization.
Installation
$ npm install github-org-repos
Usage
var repos = ;
repos( opts, clbk )
Gets meta data for all repositories belonging to an organization.
var opts ='org': 'math-io';;{// Check for rate limit information...if infoconsole;console;console;if errorthrow errormessage ;console;// returns <repo_data>}
The function
accepts the following options
:
- org: Github organization name (required).
- type: repository type; e.g.,
forks
,public
,private
, etc. Default:'all'
. - token: Github access token.
- useragent: user agent
string
.
To authenticate with Github, set the token
option.
var opts ='org': 'math-io''token': 'tkjorjk34ek3nj4!';;
To specify a user agent, set the useragent
option.
var opts ='org': 'math-io''useragent': 'hello-github!';;
To return repositories of a particular type, set the type
option.
var opts ='org': 'math-io''type': 'forks';;
repos.factory( options, clbk )
Creates a reusable function
.
var opts ='org': 'math-io''token': 'tkjorjk34ek3nj4!';var get = repos;;;;// ...
The factory method accepts the same options
as repos()
.
Notes
- Rate limit information includes the following:
- limit: maximum number of requests a consumer is permitted to make per hour.
- remaining: number of remaining requests.
- reset: time at which the current rate limit window resets in UTC seconds.
Examples
var repos = ;var opts ='org': 'math-io''useragent': 'beep-boop-bop';;{if infoconsole;if errorthrow errormessage ;console;}
To run the example code from the top-level application directory,
$ DEBUG=* node ./examples/index.js
CLI
Installation
To use the module as a general utility, install the module globally
$ npm install -g github-org-repos
Usage
Usage: ghorgrepos [options] (--org org | org)Options:-h, --help Print this message.-V, --version Print the package version.--token token Github access token.--org org Github organization name.-ua, --useragent ua User agent.--type type Repository type; e.g., forks, public, private, etc.
Notes
- In addition to the
token
option, the token may also be specified by aGITHUB_TOKEN
environment variable. The command-line option always takes precedence. - Request resources are written to
stdout
. - Rate limit information is written to
stderr
.
Examples
Setting the access token using the command-line option:
$ DEBUG=* ghorgrepos --token <token> --org 'math-io'# => '[{...},{...},...]'
Setting the access token using an environment variable:
$ DEBUG=* GITHUB_TOKEN=<token> ghorgrepos --org 'math-io'# => '[{...},{...},...]'
For local installations, modify the command to point to the local installation directory; e.g.,
$ DEBUG=* ./node_modules/.bin/ghorgrepos --token <token> --org 'math-io'# => '[{...},{...},...]'
Or, if you have cloned this repository and run npm install
, modify the command to point to the executable; e.g.,
$ DEBUG=* node ./bin/cli --token <token> --org 'math-io'# => '[{...},{...},...]'
Tests
Unit
This repository uses tape for unit tests. To run the tests, execute the following command in the top-level application directory:
$ make test
All new feature development should have corresponding unit tests to validate correct functionality.
Test Coverage
This repository uses Istanbul as its code coverage tool. To generate a test coverage report, execute the following command in the top-level application directory:
$ make test-cov
Istanbul creates a ./reports/coverage
directory. To access an HTML version of the report,
$ make view-cov
Browser Support
This repository uses Testling for browser testing. To run the tests in a (headless) local web browser, execute the following command in the top-level application directory:
$ make test-browsers
To view the tests in a local web browser,
$ make view-browser-tests
License
Copyright
Copyright © 2016. Athan Reines.