README.markdown in git-issue-0.7.0 vs README.markdown in git-issue-0.7.1

- old
+ new

@@ -20,11 +20,11 @@ ## Configuration set type of issue traking system(redmine or github) - $ git config issue.type redmine + $ git config issue.type redmine set url of issue traking system's api endopoint. $ git config issue.url http://redmine.example.com @@ -41,11 +41,11 @@ $ git config issue.user yuroyoro ## 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. 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. @@ -80,24 +80,26 @@ --category=VALUE use the given value to update category id --fixed_version=VALUE use the given value to 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(Redmine) +## 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. 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 checout 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 @@ -106,10 +108,20 @@ --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 - --state=VALUE Where 'state' is either 'open' or 'closed' + --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 does'nt supports API token base authorization for now. then, use Basic Authorizaion instead token. ## Copyright Copyright (c) 2011 Tomohito Ozaki. See LICENSE for details.