Hey @sweezyio. Thanks for wanting to contribute. I want to set some clear expectations here. We currently have very limited capacity to review and accept PRs for features, especially ones we haven't made a clear decision on how to address. Getting this reviewed thoroughly could end up taking a long time.

A very high level comment on this though is that WorkflowPreferences feels like the wrong place to host this. Workflow preferences is specifically about how the user wants to contribute to the repository (i.e. as an independent fork vs contributing to upstream).

I reckon there's two possible approaches here. Either extend IDatabaseRepository such that we can persist the user's choice there (and forward that to Repository) or we create some type of editor override object that lives separate from repositories. The downside of the latter being that we'd need specific cleanup when a repository gets removed. So, not having thought this through I think I'd prefer the former.

Currently this does not support custom editors and having a custom editor set overrides any per-repository selections. Is this something that I should handle? If so, how? Should I allow for the setting of custom editors on a per-repository basis?

Yes, I imagine users would be confused if we did not offer the ability to use a custom editor in a repository. I imagine this interface would be exactly the same as in the global preferences.

From this point, it seems like it would be pretty straightforward to add the same feature but for shells as well. Is that something I should tack onto this PR?

No. We have not seen the same request for custom shells per repository which makes sense, typically you'd use different editors based on the project but have a global shell. It being straightforward is not a good enough reason.