It would be awesome to be able to set a profile-wide non-"main" branch for new repositories (or, upon repository creation, use the first nonempty branch name as the remote "default" branch) instead of having to set it anew on every new repository, every time. (E.g., I have "master" as my default on all of my computers and I keep on forgetting to set it correctly in the web ui until I go to one of my repos and realize nothing is showing because I haven't set the correct default branch!)
allowing non-"main" branch names to be set as default profile-wide #404
I think it is better to treat "user preference" in general as private data and store everything on tangled appview instead of splitting into multiple atproto records. Users will be able to export/configure their preferences from sh.tangled.actor.{get,put}Preferences xrpc methods supported by appview like how bsky handles this from app.bsky.actor.{get,put}Preferences.
I do see some use cases of sh.tangled.gitConfig being public as third-party services can use it. But one more atproto record to sync doesn't seem good for current Tangled's decentralization situation.
sweet, thanks
agree re: the rest of defaults, assumed there would be a few others that might be worth thinking about, but I'll continue poking around and using tangled a little more!
good shout. few other things i'd want settings for (some of these are probably best as "appview" specific)
some of these do not have to be private data, and i wouldn't mind introducing something like
sh.tangled.gitConfig(maybe even mimic several git-config options!) to configure the "git experience" on tangled.