As with the previous key added in 19c0916, I deleted the associated
private key using /usr/bin/shred. But of course, I have no way to prove
that. Again, all the more reason to always use a test account when
running these integration tests.
For more information about the preview see here:
https://developer.github.com/changes/2015-11-11-protected-branches-api/
This adds only retrieving the information and not setting it. Setting
will come in a later commit (if that one here is okay).
I tried to follow the naming guidelines as much as possible and
hopefully I made it right the first time. :-)
Add a new error type, TwoFactorAuthError, which identifies the need to
include a one-time password when using Basic Auth for a user with
two-factor auth enabled.
An example of using both the new transport and error type can be seen in
examples/basicauth/main.go.
fixes#258
API URLs starting with "/" does not play well with Github Enterprise,
whose API endpoint looks like "http(s)://hostname/api/v3/".
This fixes incorrect URLs in miletones APIs.
This change adds the fields "DiffHunk", "OriginalPosition", and "OriginalCommitId" to the PullRequestComment struct. These fields provide important information about the location of a comment.
- GetOrgMembership updated to accept user parameter (BREAKING CHANGE)
- EditOrgMembership updated to accept user parameter (BREAKING CHANGE)
- Added new RemoveOrgMembership method
Ref #187
- Add new options struct to AddCollaborator (BREAKING CHANGE)
- Add Permissions field to User struct, which gets populated when
calling ListCollaborators
AddTeamRepo's "permission" option and AddTeamMembership's "role" option
should both be passed as part of a JSON request body, not as URL query
parameters.
- AddTeamMembership and ListTeamMembers both take new Option structs to
specify role. (BREAKING CHANGE).
- Add Role to ListMembersOptions
- update Permission and Role docs
Ref #187
- allow setting permission when adding a team repository
- update IsTeamRepo to return a *Repository instead of a bool, since the
Repository contains the permission data for the team. This is a
BREAKING CHANGE, however I don't think this is an often used method.
- update docs for setting the team permission when creating or editing a
team.
Ref #187