New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1003: GitHubRepository.restrictAccess sends incomplete query #1141
Conversation
|
@edvbld This change now passes all automated pre-integration checks. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 2 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the
|
/integrate |
@edvbld Since your change was applied there have been 2 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 62e23e0. |
Hi all,
please review this patch which sends the correct JSON data to GitHub's branch protection endpoint. I also changed the API of
restrictPushAccess
to make it more clear that only the suppliedHostUser
can push to the given branch afterwards.Thanks,
Erik
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/skara pull/1141/head:pull/1141
$ git checkout pull/1141
Update a local copy of the PR:
$ git checkout pull/1141
$ git pull https://git.openjdk.java.net/skara pull/1141/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 1141
View PR using the GUI difftool:
$ git pr show -t 1141
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/skara/pull/1141.diff