Project

issues

0.0
No commit activity in last 3 years
No release in over 3 years
GitHub Issues Command Line Interface
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

>= 0.9.2.2
>= 3.12

Runtime

>= 0.7.6
>= 1.6.5
>= 0.4.0
 Project Readme

Issues¶ ↑

GitHub Issues Command Line Interface

Installation¶ ↑

Add this line to your application’s Gemfile:

gem 'issues'

And then execute:

$ bundle

Or install it yourself as:

$ gem install issues

Usage¶ ↑

issues [global options] command_name [command-specific options] [--] arguments...
  • Use the command help to get a summary of commands

  • Use the command help command_name to get a help for command_name

  • Use -- to stop command line argument processing; useful if your arguments have dashes in them

Global Options¶ ↑

These options are available for any command and are specified before the name of the command

--help

Show this message

-p, --password=password

password

-r, --repo=owner/repo

repository

-u, --username=username

username

Commands¶ ↑

help

Shows list of commands or help for one command

initconfig

Initialize the config file using current global options

list

List of Issues

milestones

List of Milestones

help [command]¶ ↑

Shows list of commands or help for one command

Gets help for the application or its commands. Can also list the commands in a way helpful to creating a bash-style completion function

Options¶ ↑

These options are specified after the command.

-c, --completion

List all commands one line at a time, for use with shell completion ([command] argument is partial command to match)

initconfig ¶ ↑

Initialize the config file using current global options

Initializes a configuration file where you can set default options for command line flags, both globally and on a per-command basis. These defaults override the built-in defaults and allow you to omit commonly-used command line flags when invoking this program

Options¶ ↑

These options are specified after the command.

--force

force overwrite of existing config file

list ¶ ↑

List of Issues

Options¶ ↑

These options are specified after the command.

-a, --assignee=username

assignee

-l, --labels=label1,label2

list of comma separated Label names. Example: bug,ui,@high

-m, --milestone

mileston

-s, --state=state

state

milestones ¶ ↑

List of Milestones

Options¶ ↑

These options are specified after the command.

-s, --state=state

state ( default: open)

:include:issues.rdoc

Contributing¶ ↑

  1. Fork it

  2. Create your feature branch (‘git checkout -b my-new-feature`)

  3. Commit your changes (‘git commit -am ’Added some feature’‘)

  4. Push to the branch (‘git push origin my-new-feature`)

  5. Create new Pull Request