dodexahedron

This step: ``` git pull origin v2_xxx-branch ``` Has the potential to cause a merge that _could_ cause unexpected annoyances, since the default is to merge from your remote into...

> > Then, if, as I'm working, `v2_develop` changes, I want those changes in `v2_xxx-branch`, so I > > ```powershell > > git checkout v2_develop > > git pull upstream...

Loving the work on this. 👍 Planning to take a good look at the code later today.

There are options. At a high level, I think the one that would be most natural for everyone, since they already use it without even realizing, is sticking them into...

Oh. Forgot to mention the second option I meant to mention.. There's a visual studio extension to address this shortcoming that basically just hacks it by generating new names for...

As for the first option (nuget packages or other pre-deployment that takes the project out of the solution), we could even just put them in their own repo under the...

And, with how the newer ones are intended to be designed in a more target-agnostic fashion, I could even just publish them on nuget myself as not specifically bound to...

My inclination (without me publishing them separately, anyway) is to do it via a bit of a hybrid approach, doing all of the following: - Analyzer project not in Terminal.sln...

That would be temporary only[^foShizzle], btw, until a long-term solution is implemented. Not great practice to keep binaries in source control if you can help it. [^foShizzle]: And not temporary...

I did that on purpose because I didn't intend to support it where VS can't run. You don't have to pre-build the analyzers to do a CLI build. However, I...