Separation of project config and user config

[mavam]

My config.toml sits in a git repo that I version control. But every new project that I create adds to the very same config file, preventing sharing of the config in a team setting or even just across machines.

Example:

[post-create]
graft = "~/.config/worktrunk/scripts/graft.py {{ worktree_path }} --remote-url '{{ remote_url }}' --branch '{{ branch }}'"

#
# ⚠️ This should not be here! I cannot share this with others as a result.
#
[projects]

[projects."github.com/tenzir/docs"]
approved-commands = [
    "bun install",
]

Can we have a separate, system-local file for the projects?

[max-sixty]

I guess we could offer something like git's include syntax? I'm quite hesitant to add an additional config file; the config system is arguably fairly complex already...

[mavam]

I would keep it simple and not go into a direction of a generic include mechanism. Agreeing that's too complex.

Proposal: Add a project-config option. When set, it points to a separate path for project configs and wt uses it for all projects.* settings.

[max-sixty]

this is done! #1042

thanks for the issue, lmk any feedback

[mavam]

Even better. Convention over configuration. Liking the solution!