how should tilt behave when you switch git branches?

If you have Tilt running, and you switch git branches, the experience isn't great. Tilt will pick up a ton of file changes and re-deploy all the services. This is almost never what you want. What would be a better experience?

Possible solutions:

• Tilt could pause and pop up a prompt in the web UI to confirm that you've switched branches. You would have to explicitly confirm that you want to re-deploy everything

• Some teams we work with use feature branches to work on different subsets of services. For example, branch A might be for service X + Y, and branch B might be for service Y + Z.

If you switch, maybe we check if you have Tilt configs, and we ask you if you want to set new tilt args? (https://docs.tilt.dev/tiltfile_config.html)

Or maybe Tilt could remember the tilt args associated with a branch.

Other Questions:

• Is there ever a case where you'd want service X from branch A and service Z from branch B? Or would this behavior be too confusing / hard to reason about? Maybe you want all your services to come from the same branch

No source files or tests are named. Start by reading the linked Tiltfile configuration documentation and locating how Tilt detects branch changes and handles Tilt args; done means agreeing on and documenting a predictable branch-switch experience, including whether redeploying or changing service selections requires confirmation.