Skip to content

Squad will be moving soon #1603

Closed
Closed

Description

@bradygaster

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.

Activity

  1. pinned this issue on Aug 4, 2026
  2. laurentkempe commented on Aug 17, 2026

    @laurentkempe

    That sounds like fantastic news, @bradygaster! Does this mean it will be supported by GitHub soon?

  3. Omzig commented on Aug 25, 2026

    @Omzig
    Contributor

    @bradygaster, woowhoo! good job getting it started, that means more people at MS will be dogfooding it even more. Congrats!

  4. bradygaster commented on Sep 3, 2026

    @bradygaster
    CollaboratorAuthor

    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.

  5. bradygaster commented on Sep 23, 2026

    @bradygaster
    CollaboratorAuthor

    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.

  6. bradygaster commented on Nov 6, 2026

    @bradygaster
    CollaboratorAuthor

    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!!!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions