Matt

> Thanks for the details. It really seems like the real issue is this: > > `Our want is that we want the main repo to be able to import...

> Are there drawbacks in asking/forcing monorepo users to adopt the sample project structure outlined above? In the projects I worked on, it was not a problem and I am...

Sorry, missed this earlier. Isn't there a crate_name attribute for this exact reason? Could we not either use that for prost, or add the attribute if it doesn't exist to...

Unfortunately, I think I'm lacking the knowledge here to comment on a solution. I'll defer to someone more familiar with prost.

I believe that the best command to start with would probably be `jj log`, since the APIs for that are probably ~80% of what's needed for APIs (I can run...

Yes, the primary purpose of this FR was for version controlled configuration files (I wasnt aware of the .jj/repo/config.toml, so I tried to add in that too, but the primary...

I much prefer your .config/JJ/config.toml over the example I had. I didn't really like my suggested placement but didn't have a better place to put it.

> So, there needs to be project-wide config (like for hooks), but these can be changed in the life of the project. Yep > Also, user config per project, as...

> One of the main problems with version control config in version control is that it can affect the behavior of operations potentially outside of the commit that contains the...

I think I've made a solution to this problem that's both user-friendly and is no less secure than the current approach. If people are happy with it, I'll add finishing...