New Organizations API
I pushed the new Organization API documentation today. You can now access and modify Organization and Team information for your repositories. The Org API managed to test the limits of…
I pushed the new Organization API documentation today. You can now access and modify Organization and Team information for your repositories.
The Org API managed to test the limits of the current GitHub API. Traditionally, the Repository API actions required only the name to update your repo information. This worked well since most of the repos that you modified were owned by your own user. With Organizations, this is no longer the case, so we deprecated several of the old Repository API actions. You are encouraged (but not required) to pass the user login and the repo name for these actions (check the docs for more details):
repos/delete/:repo
repos/set/private/:repo
repos/set/public/:repo
repos/keys/:repo
repos/key/:repo/add
repos/key/:repo/remove
repos/collaborators/:repo/add/:collaborator
repos/collaborators/:repo/remove/:collaboratorThank you to all the developers that helped us out during the beta. We received some valuable feedback that helped us fine tune the APIs and ensure its consistency. If you are a developer that works with the API a lot, be sure to follow the API Support Forum for announcements on new API updates.
Written by
Related posts
We need a European Sovereign Tech Fund
Open source software is critical infrastructure, but it’s underfunded. With a new feasibility study, GitHub’s developer policy team is building a coalition of policymakers and industry to close the maintenance funding gap.
GitHub Availability Report: June 2025
In June, we experienced three incidents that resulted in degraded performance across GitHub services.
From pair to peer programmer: Our vision for agentic workflows in GitHub Copilot
AI agents in GitHub Copilot don’t just assist developers but actively solve problems through multi-step reasoning and execution. Here’s what that means.