Repo catalog squad

[diberry]

I want to use Squad to manage all my work across repos. Is anyone else doing this? It would not be at the GH org level but across personal repos and repos with GH orgs or GH EMU orgs.

[bradygaster]

I'd like to know if folks are doing this. In an upcoming release we're going to give you the ability to have "personal squads" that are just on your machine and not "married" to a single repository.

[dfberry]

@bradygaster If would be nice if your project provides Company level management of squads and Contracting house/Tiger Team level management where independent squad members from different squads can be pulled in for special projects.

[dfberry]

@bradygaster After using Squad for a few days across the many code and content repos, I don't want to check Squad into a repo, I want it to live above the repo and operate either in the Cloud or on a local machine. I can see keeping memory/history in a repo, but the skills of the teams should be above the repo. I can image using a specific GitHub repos such as github.com/dfberry/.squad or github.com/azure/.squad or github.com/MicrosoftDocs/.squad for this. I've been experimenting with how to talk to my Squad such as through a discussion board on the repo so I'm not tied into a local instance.

[thecrockster]

@bradygaster I'm using squad across repos. I work on different micro sites - these usually consist of a react frontend, bff, internal APIs (with SQL DBs), messaging (ASB) etc. I've started creating Aspire apps for each micro site stack - all the components it needs as resources. I house Squad within the Aspire app giving it knowledge/access to all it's resources (repos) so the Squad works across the micro site stack (everything in the Aspire app). It's great for feature work which often involves changes in multiple repos.