#!/usr/bin/env bash

# DO NOT EDIT. This file generated by tool/generate-help-functions.pl.

set -e

help:all() {
    cat <<'...'
cache-clear          cache-clear
clone                clone ([<owner>/]<repo> [<directory>])...
collabs              collabs [<owner>/<repo>]
comment              comment [<owner>/<repo>] <issue-id-number>
config               config [<config-key> [<config-value>]]
config-keys          config-keys
config-list          config-list
config-unset         config-unset <config-key>
follow               follow <user>...
followers            followers [<user>]
following            following [<user>]
follows              follows <user> [<target-user>]
fork                 fork <owner>/<repo> [--org=<org>] [--remote=<name>]
forks                forks [<owner>/<repo>]
gist                 gist <gist-id>
gist-clone           gist-clone <gist-id> [<directory>]
gist-delete          gist-delete <gist-id>
gist-edit            gist-edit <gist-id> <key-value-pair...>
gist-fork            gist-fork <gist-id>
gist-get             gist-get <gist-id> <data-key>
gist-init            gist-init (public|secret) <description>
gist-new             gist-new (public|secret) <description> <files...>
gist-star            gist-star <gist-id>
gist-unstar          gist-unstar <gist-id>
gists                gists [<user>]
git-hub-travis       git-hub-travis
help                 help
info                 info
irc-enable           irc-enable <room> [<server>]
irc-enable           irc-enable
irc-url              irc-url
issue                issue [<owner>/<repo>] <issue-id-number>
issue-close          issue-close [<owner>/<repo>] <issue-id-number>
issue-edit           issue-edit [<owner>/<repo>] <issue-id-number>
issue-new            issue-new [<owner>/<repo>]
issue-resolve        issue-resolve [<owner>/<repo>] <issue-id-number>
issues               issues [<owner>/<repo>] [--all]
keys                 keys [<user>]
keys-add             keys-add <title> <key>
member-add           member-add <team_id> <user>
member-get           member-get <team_id> <user>
member-remove        member-remove <team_id> <user>
members              members <org>|<team_id>
notify-list          notify-list [--all]
open                 open [<owner>/<repo>] [<file-path>]
org                  org <org>
org-edit             org-edit <org> <key-value-pairs>...
org-get              org-get <org> <data-key>
org-members          org-members <org>
org-repos            org-repos <org>
orgs                 orgs [<user>]
pr-created           pr-created [<user>] [--all]
pr-diff              pr-diff [<owner>/<repo>] <issue-id-number>
pr-fetch             pr-fetch [<owner>/<repo>] <issue-id-number>
pr-involves          pr-involves [<user>] [--all]
pr-list              pr-list [<owner>/<repo>]
pr-merge             pr-merge [<owner>/<repo>] <issue-id-number>
pr-new               pr-new [<issue-id-number>] [<options>]
pr-queue             pr-queue [<user>] [--all]
repo                 repo [<repo>]
repo-delete          repo-delete <owner>/<repo>
repo-edit            repo-edit [<owner>/]<repo> <key-value-pair>...
repo-get             repo-get <owner>/<repo> <data-key>
repo-init            repo-init [<directory>]
repo-new             repo-new [<org>/]<repo>
repos                repos [<user>]
scope-add            scope-add <api-token-id> <scope-name>...
scope-remove         scope-remove <api-token-id> <scope-name>...
scopes               scopes <api-token-id>
search-issues        search-issues <query>
search-repo          search-repo <query>
search-user          search-user <query>
setup                setup
star                 star [<owner>/<repo>]
starred              starred [<user>]
stars                stars [<owner>/<repo>]
team                 team <team_id>
team-delete          team-delete <team_id>
team-members         team-members <team_id>
team-new             team-new <org> <name> <perm>
team-repo-add        team-repo-add <team_id> <repo>
team-repos           team-repos <team_id>
teams                teams <org>
token-delete         token-delete <api-token-id>
token-get            token-get <api-token-id> <data-key>
token-new            token-new [<description-string>]
tokens               tokens
trust                trust [<owner>/<repo>] <user>...
unfollow             unfollow <user>...
unstar               unstar [<owner>/<repo>]
untrust              untrust [<owner>/<repo>] <user>...
unwatch              unwatch [<owner>/<repo>]
upgrade              upgrade
url                  url [<owner>/<repo>] [<file-path> [<line-number>]]
user                 user [<user>]
user-edit            user-edit <key-value-pair>...
user-get             user-get <user> <data-key>
version              version
watch                watch [<owner>/<repo>]
watchers             watchers [<owner>/<repo>]
watching             watching [<user>]
...
}

help:cache-clear() {
    cat <<'...'

  Usage: git hub cache-clear

  Clear your API response cache.
...
}

help:clone() {
    cat <<'...'

  Usage: git hub clone ([<owner>/]<repo> [<directory>])...

  Clone a GitHub repo. Always uses `--recursive` so you get submodules too.
  You can specifiy a list of repos. If you specify a directory for a repo, it
  should be an absolute path name or else begin with './' or '../' so that it
  can be distinguished from another repo name.
...
}

help:collabs() {
    cat <<'...'

  Usage: git hub collabs [<owner>/<repo>]

  List current collaborators for a repository.
...
}

help:comment() {
    cat <<'...'

  Usage: git hub comment [<owner>/<repo>] <issue-id-number>

  Add a comment to an issue. You can also use `issue-edit` to just add a
  comment.
...
}

help:config() {
    cat <<'...'

  Usage: git hub config [<config-key> [<config-value>]]

  With no args, this command will print the contents of `~/.git-hub/config`.
  With With one argument (a key), print the current value of the config key.
  With two arguments (key value), set the value of the config key. 4 keys are
  currently supported: `login`, `api-token`, `use-auth`, and `json-lib`.
...
}

help:config-keys() {
    cat <<'...'

  Usage: git hub config-keys

  Output all possible configuration keys
...
}

help:config-list() {
    cat <<'...'

  Usage: git hub config-list

  Will list your current configuration like `git config --list`
...
}

help:config-unset() {
    cat <<'...'

  Usage: git hub config-unset <config-key>

  Unset a config key. Removes the key from the `~/.git-hub/config` file.
...
}

help:follow() {
    cat <<'...'

  Usage: git hub follow <user>...

  Follow one or more users.
...
}

help:followers() {
    cat <<'...'

  Usage: git hub followers [<user>]

  List the people who are followers of a user.
...
}

help:following() {
    cat <<'...'

  Usage: git hub following [<user>]

  List the people that a user is following.
...
}

help:follows() {
    cat <<'...'

  Usage: git hub follows <user> [<target-user>]

  Check if `<user>` follows `<target-user>`. The default target user is you.
...
}

help:fork() {
    cat <<'...'

  Usage: git hub fork <owner>/<repo> [--org=<org>] [--remote=<name>]

  Fork a repository to your account or to an organization. Optionally, you can
  specify the name of a remote to add, pointing to your fork.
...
}

help:forks() {
    cat <<'...'

  Usage: git hub forks [<owner>/<repo>]

  List the forks of a repository.
...
}

help:gist() {
    cat <<'...'

  Usage: git hub gist <gist-id>

  Show info about gist.
...
}

help:gist-clone() {
    cat <<'...'

  Usage: git hub gist-clone <gist-id> [<directory>]

  Clone a gist.
...
}

help:gist-delete() {
    cat <<'...'

  Usage: git hub gist-delete <gist-id>

  Delete a gist.
...
}

help:gist-edit() {
    cat <<'...'

  Usage: git hub gist-edit <gist-id> <key-value-pair...>

  Set specific meta-data fields of a gist to new values. You list the
  parameters as key/value pairs.
...
}

help:gist-fork() {
    cat <<'...'

  Usage: git hub gist-fork <gist-id>

  Fork a gist.
...
}

help:gist-get() {
    cat <<'...'

  Usage: git hub gist-get <gist-id> <data-key>

  Get a specific data value for a particular gist.
...
}

help:gist-init() {
    cat <<'...'

  Usage: git hub gist-init (public|secret) <description>

  Create an (almost) empty gist and clone it

  This will create a gist with a file '.gitignore'
...
}

help:gist-new() {
    cat <<'...'

  Usage: git hub gist-new (public|secret) <description> <files...>

  Create a gist from existing files
...
}

help:gist-star() {
    cat <<'...'

  Usage: git hub gist-star <gist-id>

  Add your *star* to a gist.
...
}

help:gist-unstar() {
    cat <<'...'

  Usage: git hub gist-unstar <gist-id>

  Remove your *star* from a gist.
...
}

help:gists() {
    cat <<'...'

  Usage: git hub gists [<user>]

  List gists for a user.
...
}

help:git-hub-travis() {
    cat <<'...'

  Usage: git hub git-hub-travis

  Enable and/or disable travis-ci testing from the command line.
...
}

help:help() {
    cat <<'...'

  Usage: git hub help

  Show this manpage.
...
}

help:info() {
    cat <<'...'

  Usage: git hub info

  Show detailed version and environment info about your `git-hub` installation.
  This can be useful for figuring out things about how `git-hub` is operating
  in a given situation. Also good for reporting bugs / issues in `git-hub`.
...
}

help:irc-enable() {
    cat <<'...'

  Usage: git hub irc-enable <room> [<server>]


  This command must be run inside a cloned repo. It enables GitHub activities
  for a repo to be reported to an IRC channel.
...
}

help:irc-enable() {
    cat <<'...'

  Usage: git hub irc-enable


  This command must be run inside a cloned repo. It disables the GitHub IRC
  webhook for a repo.
...
}

help:irc-url() {
    cat <<'...'

  Usage: git hub irc-url


  Show the GitHub URL for setting webhooks on the current repo.
...
}

help:issue() {
    cat <<'...'

  Usage: git hub issue [<owner>/<repo>] <issue-id-number>

  Show info (including any comments) for a specific issue. If no issue number
  is given, this command will call `issue-new` instead.
...
}

help:issue-close() {
    cat <<'...'

  Usage: git hub issue-close [<owner>/<repo>] <issue-id-number>

  Close an issue. You can also use `issue-edit` to close an issue.
...
}

help:issue-edit() {
    cat <<'...'

  Usage: git hub issue-edit [<owner>/<repo>] <issue-id-number>

  Add a comment. Change values of 'title', 'state', 'assignee' and
  'milestone'. Changing state to 'closed' will close the issue.
...
}

help:issue-new() {
    cat <<'...'

  Usage: git hub issue-new [<owner>/<repo>]

  Create a new issue for a repository.
...
}

help:issue-resolve() {
    cat <<'...'

  Usage: git hub issue-resolve [<owner>/<repo>] <issue-id-number>

  Add a comment to an issue and then close it.
...
}

help:issues() {
    cat <<'...'

  Usage: git hub issues [<owner>/<repo>] [--all]

  List the open issues for a repo. Use the `--all` flag to see both open and
  closed issues.
...
}

help:keys() {
    cat <<'...'

  Usage: git hub keys [<user>]

  List public SSH keys for a user.
...
}

help:keys-add() {
    cat <<'...'

  Usage: git hub keys-add <title> <key>

  Add a public ssh key for your user.
...
}

help:member-add() {
    cat <<'...'

  Usage: git hub member-add <team_id> <user>

  Add a user to a team.
...
}

help:member-get() {
    cat <<'...'

  Usage: git hub member-get <team_id> <user>

  Show whether a user is a member of a specified team.
...
}

help:member-remove() {
    cat <<'...'

  Usage: git hub member-remove <team_id> <user>

  Remove a user from a team.
...
}

help:members() {
    cat <<'...'

  Usage: git hub members <org>|<team_id>

  List the members of an organization or team. If numeric argument, show team
  members, else organization members.
...
}

help:notify-list() {
    cat <<'...'

  Usage: git hub notify-list [--all]

  List your recent /unread/ user notifications. To list your /read/
  notifications as well, use the `--all` option.
...
}

help:open() {
    cat <<'...'

  Usage: git hub open [<owner>/<repo>] [<file-path>]

  Open a browser window to a repo or a file in a repo.
...
}

help:org() {
    cat <<'...'

  Usage: git hub org <org>

  Show basic information about a GitHub organization. The `--raw` and
  `--json` options show the data in different formats than normal output.
...
}

help:org-edit() {
    cat <<'...'

  Usage: git hub org-edit <org> <key-value-pairs>...

  Set specific meta-data fields of an organization to new values. You list
  the parameters as key/value pairs.

  You can edit the following organization keys: `name`, `email`,
  `billing_email`, `blog`, `location`, `company`.
...
}

help:org-get() {
    cat <<'...'

  Usage: git hub org-get <org> <data-key>

  Get a specific data value for a particular organization.
...
}

help:org-members() {
    cat <<'...'

  Usage: git hub org-members <org>

  List members of an organization.
...
}

help:org-repos() {
    cat <<'...'

  Usage: git hub org-repos <org>

  Show all the repos for an organization, both public and private.
...
}

help:orgs() {
    cat <<'...'

  Usage: git hub orgs [<user>]

  List the organizations that a user is a member of.
...
}

help:pr-created() {
    cat <<'...'

  Usage: git hub pr-created [<user>] [--all]

  Show a list of Pull Requests the user created, for all repos. Shows the open
  PRs for any repo that has them. The `--all` option says to show closed as
  well as open PRs. Results are sorted by date of creation.
...
}

help:pr-diff() {
    cat <<'...'

  Usage: git hub pr-diff [<owner>/<repo>] <issue-id-number>

  Show the diff for a pull request.
...
}

help:pr-fetch() {
    cat <<'...'

  Usage: git hub pr-fetch [<owner>/<repo>] <issue-id-number>

  Fetches a pull request to a local `review/$number` branch
...
}

help:pr-involves() {
    cat <<'...'

  Usage: git hub pr-involves [<user>] [--all]

  Show a list of Pull Requests the user is involved in. ie Pull Requests that
  were created by, assigned to, mention, or were commented on by that user.
  Shows the open PRs for any repo that has them.  The `--all` option says to
  show closed as well as open PRs. Results are sorted by date of creation.
...
}

help:pr-list() {
    cat <<'...'

  Usage: git hub pr-list [<owner>/<repo>]

  List the pull requests for a repo.
...
}

help:pr-merge() {
    cat <<'...'

  Usage: git hub pr-merge [<owner>/<repo>] <issue-id-number>

  Merge and close a pull request.

  It supports the following options:
  * `--sha`
  * `--merge-method`
  * `--commit-title`
  * `--commit-message`
...
}

help:pr-new() {
    cat <<'...'

  Usage: git hub pr-new [<issue-id-number>] [<options>]

  Create a new pull request for a repository based on the current branch. If
  an issue ID number is given, this command will attach the pull request to the
  issue instead of creating a new one.

  If the default remote is a fork, the pull request will target the default
  branch of the parent repository. Otherwise the pull request will target the
  default branch of the default remote itself. Use `--remote`, `--branch`,
  `--parent`, and `--base` options to change the default source remote, source
  branch, target remote and target branch (respectively).

  This command will open an editor like `git commit` does. To avoid that you
  can pipe text into the command.
...
}

help:pr-queue() {
    cat <<'...'

  Usage: git hub pr-queue [<user>] [--all]

  Show a user's Pull Request queue, for all repos. Shows the open PRs for any
  repo that has them. The `--all` option says to show closed as well as
  open PRs. Results are sorted by date of creation.
...
}

help:repo() {
    cat <<'...'

  Usage: git hub repo [<repo>]

  Show basic information about a specific repository. The `--raw` and
  `--json` options show the data in different formats than normal output.
...
}

help:repo-delete() {
    cat <<'...'

  Usage: git hub repo-delete <owner>/<repo>

  Delete a GitHub repository.
...
}

help:repo-edit() {
    cat <<'...'

  Usage: git hub repo-edit [<owner>/]<repo> <key-value-pair>...

  Set specific meta-data fields of a repository to new values. You list the
  parameters as key/value pairs.

  You can edit the following repo keys: `description`, `homepage`.
...
}

help:repo-get() {
    cat <<'...'

  Usage: git hub repo-get <owner>/<repo> <data-key>

  Get a specific data value for a particular repository.
...
}

help:repo-init() {
    cat <<'...'

  Usage: git hub repo-init [<directory>]

  This command is useful for setting up new repos. Just mkdir a new dir, cd
  into it and issue the command. It will 'git init', make the GitHub repo
  and add it as the origin remote. It will only do the things that have not
  yet been done.
...
}

help:repo-new() {
    cat <<'...'

  Usage: git hub repo-new [<org>/]<repo>

  Create a new GitHub repository.
...
}

help:repos() {
    cat <<'...'

  Usage: git hub repos [<user>]

  List the repos for a user or organization. List is returned in order of
  recent activity.
...
}

help:scope-add() {
    cat <<'...'

  Usage: git hub scope-add <api-token-id> <scope-name>...

  Add one or more scopes to your API token. You can use the `--all` option
  to add all possible scopes at once.
...
}

help:scope-remove() {
    cat <<'...'

  Usage: git hub scope-remove <api-token-id> <scope-name>...

  Remove one or more scopes from your API token. You can use the `--all`
  option to remove all possible scopes at once.
...
}

help:scopes() {
    cat <<'...'

  Usage: git hub scopes <api-token-id>

  List the scopes assigned to your API token, and also list all the possible
  scope values that you can assign. Use the `--raw` option to just list the
  scopes.
...
}

help:search-issues() {
    cat <<'...'

  Usage: git hub search-issues <query>


  Search for issues and pull requests.
  For more information, see the search documentation at
  [https://developer.github.com/v3/search/#search-users]
...
}

help:search-repo() {
    cat <<'...'

  Usage: git hub search-repo <query>

  Search for repositories.

  By default it searches in the repository name, but you can change that:
  `search-repo "libyaml in:description"`. For more information, see
  the search documentation at
  [https://developer.github.com/v3/search/#search-repositories]
...
}

help:search-user() {
    cat <<'...'

  Usage: git hub search-user <query>

  Search for users.

  By default it searches in the login field, but you can change that:
  `search-user "wall in:fullname"`. For more information, see
  the search documentation at
  [https://developer.github.com/v3/search/#search-users]
...
}

help:setup() {
    cat <<'...'

  Usage: git hub setup

  Before you can use the commands described below, you need to perform some
  setup/configuration steps.

  This "wizard" style dialog, will walk you through the configuration process
  quickly and painlessly, with lots of explanation. You should run this
  command right away. You can also re-run it, and it will allow you to change
  your config, while defaulting to your existing settings.

  If you would rather do the steps by hand, see [#Configuration-Commands]
  below.
...
}

help:star() {
    cat <<'...'

  Usage: git hub star [<owner>/<repo>]

  Add your *star* to a repository.
...
}

help:starred() {
    cat <<'...'

  Usage: git hub starred [<user>]

  List repositories that a user has starred.
...
}

help:stars() {
    cat <<'...'

  Usage: git hub stars [<owner>/<repo>]

  Show what users have starred a repository.
...
}

help:team() {
    cat <<'...'

  Usage: git hub team <team_id>

  Get information about a team.
...
}

help:team-delete() {
    cat <<'...'

  Usage: git hub team-delete <team_id>

  Delete a team.
...
}

help:team-members() {
    cat <<'...'

  Usage: git hub team-members <team_id>

  List members of a team.
...
}

help:team-new() {
    cat <<'...'

  Usage: git hub team-new <org> <name> <perm>

  Add a new team (name) to an organization. The 'perm' arg must be pull, push
  or admin.
...
}

help:team-repo-add() {
    cat <<'...'

  Usage: git hub team-repo-add <team_id> <repo>

  Add repo to a team. Repo name must not include org name.
...
}

help:team-repos() {
    cat <<'...'

  Usage: git hub team-repos <team_id>

  List repos of a team.
...
}

help:teams() {
    cat <<'...'

  Usage: git hub teams <org>

  List the teams in an organization.
...
}

help:token-delete() {
    cat <<'...'

  Usage: git hub token-delete <api-token-id>

  Delete one of your API tokens for your GitHub login id. Note: You need to
  delete tokens by *id* (listed by the `tokens` command), not by token value.
...
}

help:token-get() {
    cat <<'...'

  Usage: git hub token-get <api-token-id> <data-key>

  Get a specific data value for a particular token.
...
}

help:token-new() {
    cat <<'...'

  Usage: git hub token-new [<description-string>]

  Create a new API token for your GitHub login id. Note: Creating a new
  token will not automatically add it to your `~/.git-hub/config` file; you
  need to do that yourself with the `git hub config api-token
  <token-value>` command. Use the `--raw` option to just print the new
  token id.
...
}

help:tokens() {
    cat <<'...'

  Usage: git hub tokens

  List all the API tokens for your GitHub account. Use the `--raw` option
  to print the token IDs and descriptions, but not the actual token values.
...
}

help:trust() {
    cat <<'...'

  Usage: git hub trust [<owner>/<repo>] <user>...

  Add one or more collaborators to a repository.
...
}

help:unfollow() {
    cat <<'...'

  Usage: git hub unfollow <user>...

  Stop following one or more users.
...
}

help:unstar() {
    cat <<'...'

  Usage: git hub unstar [<owner>/<repo>]

  Remove your *star* from a repository.
...
}

help:untrust() {
    cat <<'...'

  Usage: git hub untrust [<owner>/<repo>] <user>...

  Remove one or more collaborators from a repository.
...
}

help:unwatch() {
    cat <<'...'

  Usage: git hub unwatch [<owner>/<repo>]

  Stop watching a repo.
...
}

help:upgrade() {
    cat <<'...'

  Usage: git hub upgrade

  Upgrade the `git-hub` installation to the latest version. Note: you need to
  be running 'git-hub' from the source repo, and be on the main branch for
  this to work.
...
}

help:url() {
    cat <<'...'

  Usage: git hub url [<owner>/<repo>] [<file-path> [<line-number>]]

  Print the URL of a repo or a file in a repo.
...
}

help:user() {
    cat <<'...'

  Usage: git hub user [<user>]

  Show basic information about a specific user. User defaults to the owner
  of the current repo, or your login if you are not inside a repo directory.
  The `--raw` and `--json` options show the data in different formats than
  normal output.
...
}

help:user-edit() {
    cat <<'...'

  Usage: git hub user-edit <key-value-pair>...

  Set specific fields of your user info to new values. You list the
  parameters as key/value pairs.

  You can edit the following user keys: `name`, `email`, `blog`,
  `location`, `company`, `bio`.
...
}

help:user-get() {
    cat <<'...'

  Usage: git hub user-get <user> <data-key>

  Get a specific data value for a particular user.
...
}

help:version() {
    cat <<'...'

  Usage: git hub version

  Print version info for `git-hub`.
...
}

help:watch() {
    cat <<'...'

  Usage: git hub watch [<owner>/<repo>]

  Start watching a repo.
...
}

help:watchers() {
    cat <<'...'

  Usage: git hub watchers [<owner>/<repo>]

  Show the users who are watching a repo.
...
}

help:watching() {
    cat <<'...'

  Usage: git hub watching [<user>]

  Show which repos a user is watching.
...
}

# vim: set sw=2 lisp:
