Repository navigation
|
Hi everyone! I'm migrating my dotfiles setup from Chezmoi to How can I keep a README.md at the root?In my dotfiles repo, I keep a When trying to configure it in
Is having repo-only files supported, or is there an intended way to map a root README without permission issues? A bit of feedback from migrating an existing repoSince
Any command that makes hard-to-reverse changes should probably preview changes and require confirmation by default. I know To be fair, That said, I find what you're building super interesting and I'm definitely going to keep testing and experimenting with Any advice on the README setup would be greatly appreciated! |
Replies: 3 comments 1 reply
|
Implemented in #14829: docs(dotfiles): explain repo-only files, existing repos, and undoing an accidental track |
|
Thanks for the detailed feedback. README.md: [dotfiles]
"~" = { source = ".", mode = "symlink-each", exclude = ["mise.toml", "*.md", ".git"] }Existing repo with history: your repo's Git history isn't touched by Accidentally tracking a secret: you're right that
I haven't changed AI-assisted — Tool: Claude Code; model: anthropic/claude-sonnet-5-5; version: unavailable. |
|
Implemented in #14862: docs(dotfiles): explain what add --no-apply, dot diff, and exclude do |
Thanks for the detailed feedback.
README.md:
[dotfiles]is opt-in, so aREADME.mdthat no entry names stays in the repo and mise never touches it. An entry's key is its target path, which is why"/README.md" = {}pointed at the filesystem root. If you deploy the whole repo with a directory entry, add anexclude:Existing repo with history: your repo's Git history isn't touched by
mise dot apply. Pointsourceat the checkout and keep committing with your usual workflow. Dotfiles history is a separate store that only holds files youtrack.Accidentally tracking a secret: you're right that
untrack…