You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Github allows you to specify "sha" parameter multiple times while querying for commits. For eg., the case where we need commits from branch x from commit sha y, we could specify sha query parameter twice in the github api url. The current code has no way to achieve this scenario.
(This is related to Merge of pull request #86 . Commit : a409b4f)
The text was updated successfully, but these errors were encountered:
Sorry for the confusion.
Here is the details of what works and what does not work
Works:
gitHub.getUser("kohsuke").getRepository("github-api").queryCommits().from("gh-pages")
=> Shows all 45 commits in branch gh-pages
Works:
gitHub.getUser("kohsuke").getRepository("github-api").queryCommits().from("5c6267b37624540c568a18ae7ee337a00a2d992c")
=> Shows the three commits starting from the given commit sha
Works:
gitHub.getUser("kohsuke").getRepository("github-api").queryCommits().from("gh-pages").from("5c6267b37624540c568a18ae7ee337a00a2d992c")
=> Shows three commits from the given commit number. Actually ignores the branch option given
and takes only the sha option. (This was the case I tested first and closed the issue :( )
Doesn't work:
gitHub.getUser("kohsuke").getRepository("github-api").queryCommits().from("5c6267b37624540c568a18ae7ee337a00a2d992c").from("gh-pages")
=> Shows all 45 commits in branch gh-pages. It ignores the sha option we have specified.
Expected: Show only 3 commits from given sha from the given branch
Github allows you to specify "sha" parameter multiple times while querying for commits. For eg., the case where we need commits from branch x from commit sha y, we could specify sha query parameter twice in the github api url. The current code has no way to achieve this scenario.
(This is related to Merge of pull request #86 . Commit : a409b4f)
The text was updated successfully, but these errors were encountered: