Skip to content

I Would Like Some Clarity on Ways of Working with squad (Branches) #75

Closed

Description

@essenbee2

Watching csharpfritz's streams using squad and an apparent issue he had with branches and the squad files seemingly "disappearing" (might have misinterpretted what happened) and being that I want to start using squad tomorrow on a big project, I'd like some clarity on how I should work with the agent team in terms of git branches please.

Normally, I would create a project with a main and a develop branches, and work in the latter (creating feature branches as required), and merging into main after features are built and tested. So with squad, do I run the team in develop and it takes care of the branches off of that it needs? Do I manually merge develop into git as an when I'm ready (i.e. do what I always do only with the Squad taking care of features)? Or should I be working in a different manner? I ask after reading some of the Blog Posts and getting a bit confused about the working pattern I should adopt.

Probably a dumb issue to raise, but as I want to start working with squad on a real work project, I thought it worthwhile getting advise from you beforehand!

Thanks for your patience,

Stu

Activity

  1. bradygaster commented on Feb 15, 2026

    @bradygaster
    Collaborator

    Thanks for submitting the issue - can you see if you're seeing the .ai-files folders in your .gitignore file?

  2. added 2 commits that reference this issue on Mar 26, 2026
    6ca3def
    d4a47ea
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