Git Product home page Git Product logo

git-issue's Introduction

git-issue

git subcommand of browse/modify issue traker's tickets.

now available issue-tracker system is Redmine and Github-issues.

ScreenShots

Installation

$ gem install git-issue

or

$ git clone https://github.com/yuroyoro/git-issue.git
$ cd git-issue
$ gem install jeweler
$ rake install

Configuration(Redmine)

set type of issue traking system(redmine or github)

$ git config issue.type redmine

set url of issue traking system's api endopoint.

$ git config issue.url http://redmine.example.com

set api-key for accessing issue traking system.

$ git config issue.apikey FWeaj3I9laei03A....

set repository name if using github.

$ git config issue.repo gitterb

set your account name if using github.

$ git config issue.user yuroyoro

Configuration(Github Issues)

set type of issue traking system(redmine or github)

$ git config issue.type github

set user and password of github(for authentication)

$ EDITOR=vim pit set github

Usage(Redmine)

git issue <command> [ticket_id] [<args>]

Commnads:
  show     s show given issue summary. if given no id,  geuss id from current branch name.
  view     v view issue in browser. if given no id,  geuss id from current branch name.
  list     l listing issues.
  mine     m display issues that assigned to you.
  commit   c commit with filling issue subject to messsage.if given no id, geuss id from current branch name.
  add      a create issue.
  update   u update issue properties. if given no id, geuss id from current branch name.
  branch   b checkout to branch using specified issue id. if branch dose'nt exisits, create it. (ex ticket/id/<issue_id>)
  publish  pub push branch to remote repository and set upstream
  rebase   rb rebase branch onto specific newbase
  help     h show usage.
  local    loc listing local branches tickets
  project  pj listing ticket belongs to sspecified project

Options:
  -a, --all                        update all paths in the index file
  -f, --force                      force create branch
  -v, --verbose                    show issue details
  -n, --max-count=VALUE            maximum number of issues
      --oneline                    display short info
      --raw-id                     output ticket number only
      --remote=VALUE               on publish, remote repository to push branch
      --onto=VALUE                 on rebase, start new branch with HEAD equal to "newbase"
      --debug                      debug print
  -j, --supperss_journals          do not show issue journals
  -r, --supperss_relations         do not show issue relations tickets
  -c, --supperss_changesets        do not show issue changesets
  -q, --query=VALUE                filter query of listing tickets
      --project_id=VALUE           use the given value to create subject
      --description=VALUE          use the given value to create subject
      --subject=VALUE              use the given value to create/update subject
      --ratio=VALUE                use the given value to create/update done-ratio(%)
      --status=VALUE               use the given value to create/update issue statues id
      --priority=VALUE             use the given value to create/update issue priority id
      --tracker=VALUE              use the given value to create/update tracker id
      --assigned_to_id=VALUE       use the given value to create/update assigned_to id
      --category=VALUE             use the given value to create/update category id
      --fixed_version=VALUE        use the given value to create/update fixed_version id
      --custom_fields=VALUE        value should be specifies '<custom_fields_id1>:<value2>,<custom_fields_id2>:<value2>, ...'
      --notes=VALUE                add notes to issue

Usage(Github Issues)

git issue <command> [ticket_id] [<args>]

Commnads:
  show     s show given issue summary. if given no id,  geuss id from current branch name.
  view     v view issue in browser. if given no id,  geuss id from current branch name.
  list     l listing issues.
  mine     m display issues that assigned to you.
  commit   c commit with filling issue subject to messsage.if given no id, geuss id from current branch name.
  add      a create issue.
  update   u update issue properties. if given no id, geuss id from current branch name.
  branch   b checkout to branch using specified issue id. if branch dose'nt exisits, create it. (ex ticket/id/<issue_id>)
  publish  pub push branch to remote repository and set upstream
  rebase   rb rebase branch onto specific newbase
  help     h show usage.
  mention  men create a comment to given issue

Options:
  -a, --all                        update all paths in the index file
  -f, --force                      force create branch
  -v, --verbose                    show issue details
  -n, --max-count=VALUE            maximum number of issues
      --oneline                    display short info
      --raw-id                     output ticket number only
      --remote=VALUE               on publish, remote repository to push branch
      --onto=VALUE                 on rebase, start new branch with HEAD equal to "newbase"
      --debug                      debug print
  -s, --supperss_commentsc         show issue journals
      --title=VALUE                Title of issue.Use the given value to create/update issue.
      --body=VALUE                 Body content of issue.Use the given value to create/update issue.
      --state=VALUE                Use the given value to create/update issue. or query of listing issues.Where 'state' is either 'open' or 'closed'
      --milestone=VALUE            Use the given value to create/update issue. or query of listing issues, (Integer Milestone number)
      --assignee=VALUE             Use the given value to create/update issue. or query of listing issues, (String User login)
      --mentioned=VALUE            Query of listing issues, (String User login)
      --labels=VALUE               Use the given value to create/update issue. or query of listing issues, (String list of comma separated Label names)
      --sort=VALUE                 Query of listing issues, (created,  updated,  comments,  default: created)
      --direction=VALUE            Query of listing issues, (asc or desc,  default: desc.)
      --since=VALUE                Query of listing issue, (Optional string of a timestamp in ISO 8601 format: YYYY-MM-DDTHH:MM:SSZ)
      --password=VALUE             For Authorizaion of create/update issue.  Github API v3 doesn't supports API token base authorization for now. then, use Basic Authorizaion instead token.
      --sslnoverify                don't verify SSL

Copyright

Copyright (c) 2011 Tomohito Ozaki. See LICENSE for details.

git-issue's People

Contributors

bakudankun avatar banyan avatar chinmo avatar kdmsnr avatar kunigaku avatar kyanny avatar lettas avatar linyows avatar mattn avatar mizzy avatar monaka avatar mooz avatar ukstudio avatar usualoma avatar yasuyk avatar yukirii avatar yuroyoro avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

git-issue's Issues

ちゃんとしたruby-gemsにしたい

わりと適当だし、rubygems-orgにも登録してない。
使うには自分でrake buildしなきゃなので。

gemtの作り方とかわかんねっすよ

githubの時にissue.repoの設定を利用する

githubの時にissue.repoの設定を利用していないようです。
現在は「git config remote.origin.url」を使っているようです。
forkしたレポジトリを扱っている時にオリジナルのissueを操作したいのですが、そのような場合に困りました。

Someone in charge?

I saw @shiftky and @urokota have branches ahead as I do. And there are plenty of issues to take care of. I started using git-issue a few months ago but it’s damn usefull for me and I intend to continously maintain it. @yuroyoro, maybe I can help you maintain this ?

github apikey not used

type:githubにてconfigでapikey設定しないと使えないようになっていますが、実際には使っているのはBASIC認証用のpasswordでPitからとってきているようですが…

tracとか

tracってjson返すAPIなんかあった?

Add english translation

I already did it for github, should I make a PR ? I don’t know bitbucket or redmine so I won’t do it

もうこれ以上やる気がでない

とりあえず自分にとってはそれなりに便利に使えるようになったし、Gemとか作るのメンドイし、Github IssueとかTracとか今のところあまり使ってないしで、もうあんまりやる気がなくなった。

だれか引き継いでくれ

gitのSSLの設定を利用できる

GitHubのissueを操作するときに以下の例外が発生して失敗します。gitのSSLに関する設定を使うようにすれば解決できると考えています。

SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed
/Users/kouji/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/net/http.rb:799:in `connect'
/Users/kouji/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/net/http.rb:799:in `block in connect'
/Users/kouji/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/timeout.rb:54:in `timeout'
/Users/kouji/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/timeout.rb:99:in `timeout'
/Users/kouji/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/net/http.rb:799:in `connect'
/Users/kouji/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/net/http.rb:755:in `do_start'
/Users/kouji/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/net/http.rb:744:in `start'
/Users/kouji/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/open-uri.rb:306:in `open_http'
/Users/kouji/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/open-uri.rb:775:in `buffer_open'
/Users/kouji/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/open-uri.rb:203:in `block in open_loop'
/Users/kouji/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/open-uri.rb:201:in `catch'
/Users/kouji/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/open-uri.rb:201:in `open_loop'
/Users/kouji/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/open-uri.rb:146:in `open_uri'
/Users/kouji/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/open-uri.rb:677:in `open'
/Users/kouji/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/1.9.1/open-uri.rb:29:in `open'
/Users/kouji/.rvm/gems/ruby-1.9.3-p125/gems/git-issue-0.8.2/lib/git_issue/github.rb:198:in `fetch_json'
/Users/kouji/.rvm/gems/ruby-1.9.3-p125/gems/git-issue-0.8.2/lib/git_issue/github.rb:57:in `list'
/Users/kouji/.rvm/gems/ruby-1.9.3-p125/gems/git-issue-0.8.2/lib/git_issue/base.rb:44:in `execute'
/Users/kouji/.rvm/gems/ruby-1.9.3-p125/gems/git-issue-0.8.2/lib/git_issue.rb:145:in `main'
/Users/kouji/.rvm/gems/ruby-1.9.3-p125/gems/git-issue-0.8.2/bin/git-issue:7:in `<top (required)>'
/Users/kouji/.rvm/gems/ruby-1.9.3-p125/bin/git-issue:19:in `load'
/Users/kouji/.rvm/gems/ruby-1.9.3-p125/bin/git-issue:19:in `<main>'

再現環境は以下の環境です。

  • Mac OS X 10.7 (Lion)
  • ruby 1.9.3-p125
  • git version 1.7.9.6
  • git-issue (0.8.2)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.