-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Support the move of the GitHub Teams API #1387
Comments
To clarify here, the library is not currently broken, the above We should though longer term move to the new API endpoints as the current ones are deprecated and will at some point in the future disappear and be only available under the new endpoints. So no immediate rush, but something to do in the future. |
I'm surprised I missed GitHub Developer announcements in their blog posts that the APIs were moving. This issue would be a great opportunity for a new Go developer or someone new to our repo to investigate the change of the API endpoints mentioned above and to bring them up-to-date. Feel free to volunteer for any issue and the issue can be assigned to you so that others don't attempt to duplicate the work. Please check out our CONTRIBUTING.md guide to get started. Thank you! |
I would like to contribute to this issue. |
Thank you, @Atorr ! |
Not the most familiar, but in this case do we want to preserve implementation for legacy endpoints or delete them? |
Since this repo is versioned, we can go ahead and delete them. Thank you! |
@gmlewis That's because the announcement didn't happen yet, and is in progress 😄. The confusion here originally started since an unrelated issue somewhere else was incorrectly thought to also affect this library. So that's why there was basically a premature issue opened here and why you didn't read about this yet 😄. |
OK, thank you, @dbussink! That explains it. 😄 I try to stay on top of the GitHub Developer announcements via RSS and Feedly - (I wish I could subscribe via email to the announcements... is there an easy way to do that?). Anyway, thanks for the info! |
@gmlewis Wanted to let you know that the post is up now at https://developer.github.com/changes/2020-01-21-moving-the-team-api-endpoints/ 😄. |
@Atorr Since this issue is assigned to you I won't start working on a PR for the changes either, please let us know in case you can't continue working on this. |
Since this issue is a big one, let's make a list of what needs to be done, which will help to keep things organized. Endpoints to be deleted:
New endpoints to be added:
|
@weeco - Wrapping up some changes per PR reviews. I should still be able to close this out. Thanks though! |
Over in https://github.com/terraform-providers/terraform-provider-github/issues/323, there has been some breakage due to GitHub moving the top-level
/teams
endpoint to live under/organizations/:org_id/team
.v28.0.0
of this codebase is used for the GitHub Terraform provider, which is affected by the change.I suspect https://github.com/google/go-github/blob/master/github/teams.go will need updates as well to cope with the changes.
cc https://github.com/github/ecosystem-api/issues/1836
The text was updated successfully, but these errors were encountered: