Repository navigation
Add support for Copilot Spaces #4238
Description
GitHub has just announced that the Copilot Spaces API is now GA.
Metadata
Metadata
Assignees
Labels
No labels
{{ message }}
GitHub has just announced that the Copilot Spaces API is now GA.
Activity
ibrahimkarimeddin commentedon May 20, 2026
I’m a new contributor and would love to work on this feature if it’s available.
gmlewis commentedon May 20, 2026
Thank you, @ibrahimkarimeddin! It's yours.
Please see CONTRIBUTING.md for helpful details while working on this feature.
maishivamhoo123 commentedon Jun 17, 2026
@gmlewis it is looking no any reply from one month. can you please assign this issue to me ? i love to work on this issue.
Thank you !
gmlewis commentedon Jun 17, 2026
@maishivamhoo123 - thank you for your interest! Let's please check with @ibrahimkarimeddin and give one day to respond on the current status, then if we don't hear back by tomorrow, we will assign the task to you.
gmlewis commentedon Jun 18, 2026
OK, @maishivamhoo123 - hearing no response, the issue is now yours. Thank you!
Ackberry commentedon Jul 2, 2026
Hey @gmlewis , it seems there's no response from the other person too. If it's okay, I would love to work on this issue as a part of Codepath's Open source capstone project! If you'd like to wait , that works too :)
gmlewis commentedon Jul 2, 2026
OK, @Ackberry - as we did before, let's give @maishivamhoo123 one day to respond and if we still hear nothing, I'll assign the issue to you. 😄
gmlewis commentedon Jul 3, 2026
OK, @Ackberry - hearing no response, the issue is now yours. Thank you!
Ackberry commentedon Jul 10, 2026
Hey @gmlewis, would you prefer Copilot Spaces support to land as one PR covering spaces, collaborators, and resources, or split into smaller PRs? I was thinking of starting with just the core Spaces CRUD endpoints first, then following up with collaborators/resources if that shape sounds good.
Also:
should these methods live on the existing
CopilotService?should requests use
WithVersion(api20260310)since the docs list Copilot Spaces under API version2026-03-10or stick to the usual version?gmlewis commentedon Jul 10, 2026
In general, many smaller PRs are more preferable to fewer larger PRs as they are much easier to review.
Yes, I think
CopilotServicemakes sense.If the same API works for both versions then there is no need to tag it explicitly.
Ackberry commentedon Jul 10, 2026
Thanks, that makes sense.
I’ll start with a smaller first PR focused only on the core Copilot Spaces CRUD endpoints on
CopilotService, without collaborators or resources for now.My planned scope for the first PR is:
Then, if that looks good, collaborators and resources can follow in separate smaller PRs.
Ackberry commentedon Jul 13, 2026
@gmlewis let me know if this works, and then I can begin working on PR#2 :)
gmlewis commentedon Jul 13, 2026
Just FYI - it is the responsibility of the PR authors to locally test that their new code works.
Ackberry commentedon Jul 13, 2026
on it! I completely forgot about the running test scripts, and just ran specific tests for each endpoints locally. I will make sure to run those scripts before any PRs. thank you!