You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Very soon, we'll be relocating this repo to a GitHub-owned organization. It will probably be moving to github/squad, but the specifics are still being ironed out.
Reacted by Eric Jorgensen, Mike Linnen, Laurent Kempé, Yashas Gujjar, Leho Kraav, Matthew Morrow and Sreenath Santhanam
Reacted by Earl Tankard, Jr., Ph.D., Danny Tamsen, Laurent Kempé and Sreenath Santhanam
Quick update on this — I've been informed, along with @tamirdresher, that this move will be happening rather soon.
We've had a few kind folks reach out and ask about the move, so I'll answer a few of those questions here and try to summarize why we're moving.
Squad has grown immensely, organically, with a tremendous amount of help from our community, colleagues, contributors, and Squad's customers. We've gotten to a point where the repo simply needs to live in a more centralized, protected place than "some individual's repo," given how many things we're now seeing built using Squad — and on top of Squad.
With my move to GitHub, @tamirdresher's increasing involvement in Squad and serverless compute, and Squad's growth both internally and externally continuing, we knew it was time for Squad to move into a more official organization with stronger control mechanisms — and, frankly, some pretty exciting integration opportunities. You've probably already seen some of those emerging through our gh-aw collaborations.
I'll update this issue once we move, but please be aware that the move is right around the corner. If you've got a fork, you may need to change your upstream soon. We may have a docs hiccup or two as well, but we'll do our best to get everything dialed in as things progress.
@tamirdresher, @spboyer, @diberry, and @IEvangelist — thank you all for being core contributors from the beginning and for helping build Squad into something fantastic, alongside all the contributors, issue-submitters, customers, and community members who've helped us get here.
And everyone: thank you all so, SO much for tinkering, learning, experimenting, and building with us during this first year of our adventure together.
@tamirdresher and I have some ideas we're hoping to share very soon.
I'm excited to see what we do next with Squad.
Reacted by Matthew Morrow, Mike Rousos, Jack Batzner, Brian Swiger, Chris Daly, Jeffrey Luszcz, Laurent Kempé and Michael Kaboro
Closing — this is a point-in-time relocation notice, not an actionable engineering task, and it's gone stale (no update in 3 weeks, repo is still bradygaster/squad). Not useful to keep open as a tracked issue; reopen or re-announce when the move is actually scheduled.
Activity
laurentkempe commentedon Aug 17, 2026
That sounds like fantastic news, @bradygaster! Does this mean it will be supported by GitHub soon?
Omzig commentedon Aug 25, 2026
@bradygaster, woowhoo! good job getting it started, that means more people at MS will be dogfooding it even more. Congrats!
bradygaster commentedon Sep 3, 2026
Quick update on this — I've been informed, along with @tamirdresher, that this move will be happening rather soon.
We've had a few kind folks reach out and ask about the move, so I'll answer a few of those questions here and try to summarize why we're moving.
Squad has grown immensely, organically, with a tremendous amount of help from our community, colleagues, contributors, and Squad's customers. We've gotten to a point where the repo simply needs to live in a more centralized, protected place than "some individual's repo," given how many things we're now seeing built using Squad — and on top of Squad.
With my move to GitHub, @tamirdresher's increasing involvement in Squad and serverless compute, and Squad's growth both internally and externally continuing, we knew it was time for Squad to move into a more official organization with stronger control mechanisms — and, frankly, some pretty exciting integration opportunities. You've probably already seen some of those emerging through our
gh-awcollaborations.I'll update this issue once we move, but please be aware that the move is right around the corner. If you've got a fork, you may need to change your upstream soon. We may have a docs hiccup or two as well, but we'll do our best to get everything dialed in as things progress.
@tamirdresher, @spboyer, @diberry, and @IEvangelist — thank you all for being core contributors from the beginning and for helping build Squad into something fantastic, alongside all the contributors, issue-submitters, customers, and community members who've helped us get here.
And everyone: thank you all so, SO much for tinkering, learning, experimenting, and building with us during this first year of our adventure together.
@tamirdresher and I have some ideas we're hoping to share very soon.
I'm excited to see what we do next with Squad.
bradygaster commentedon Sep 23, 2026
Closing — this is a point-in-time relocation notice, not an actionable engineering task, and it's gone stale (no update in 3 weeks, repo is still
bradygaster/squad). Not useful to keep open as a tracked issue; reopen or re-announce when the move is actually scheduled.bradygaster commentedon Nov 6, 2026
We've moved! we're now at https://github.com/github/squad
Blog post henceforth! It happened so fast right at the end... stay tuned!!!!!