Skip to content

Commit

Permalink
push: improve docs on success / failure of git_push_finish
Browse files Browse the repository at this point in the history
  • Loading branch information
schu committed Feb 14, 2013
1 parent a9e1339 commit a53b5e5
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions include/git2/push.h
Original file line number Diff line number Diff line change
Expand Up @@ -82,6 +82,11 @@ GIT_EXTERN(int) git_push_update_tips(git_push *push);
/**
* Actually push all given refspecs
*
* Note: To check if the push was successful (i.e. all remote references
* have been updated as requested), you need to call both
* `git_push_unpack_ok` and `git_push_status_foreach`. The remote
* repository might refused to update some or all of the references.
*
* @param push The push object
*
* @return 0 or an error code
Expand All @@ -100,6 +105,11 @@ GIT_EXTERN(int) git_push_unpack_ok(git_push *push);
/**
* Call callback `cb' on each status
*
* For each of the updated references, we receive a status report in the
* form of `ok refs/heads/master` or `ng refs/heads/master <msg>`.
* `msg != NULL` means the reference has not been updated for the given
* reason.
*
* @param push The push object
* @param cb The callback to call on each object
*
Expand Down

0 comments on commit a53b5e5

Please sign in to comment.