Uh oh!
There was an error while loading. Please reload this page.
[Feature]: Per-project local settings outside the repository #8871
danielo515
started this conversation in
Ideas
Replies: 0 comments
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Problem or use case
I'm a freelancer working in client repositories I don't control. I'd like to configure each project locally on my machine — without committing anything to the client's repo:
Today the pieces live in different places: project settings sit in T3's own per-project record, but the declarative way to seed them is a repo-committed
t3.json(plus a manual import per checkout). Committing T3 config to a client's repo isn't an option for me.Proposed solution
A per-project local config file outside the repository (e.g.
<T3 home>/projects/<project>/t3.json, or a user-level file keyed by repo), supporting everything repot3.jsonsupports, applied automatically without a manual import.Related discussions, each asking for one slice of this: #6989 (user-level t3.json), #6975 (worktree location), #6866 (default base branch), #6807 (per-project instruction files).
Thanks for considering it — happy to provide more detail on the workflow if useful.
All reactions