Replies: 3 comments 8 replies
-
You don't have to edit your dotfiles exclusively through chezmoi. I never use
See Handle configuration files which are externally modified for a symlink approach and Modify file for a brief overview on
You can probably use |
Beta Was this translation helpful? Give feedback.
-
These are in two opposite directions, and the result will be your work-state overwritten. I'm guessing what you were looking for was May I suggest the following flow:
At #3 you can script the merge, git add, git commit, git push process - this will be what works for you. When you want to sync your changes from other places, what you're probably looking for is: If there are any conflicts, chezmoi will prompt you and allow you to diff before, you can run your save script first and then |
Beta Was this translation helpful? Give feedback.
-
Hello @jbhanks ,
Still trying to find a way ... |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I like the idea of Chezmoi, but I'm not sure the intended workflow will work for me.
It's problematic for me to edit my dotfiles exclusively through Chezmoi for several reasions:
I'm thinking it might make most sense for me to just have a startup script that runs
chezmoi apply
and push to git at each login. If I understand correctly howchezmoi re-add
works, this will ensure that all the files being tracked by Chezmoi will be backed up (and secrets removed) at least to the last login. As long as I am ok with that limitation, I can do this and ignorechezmoi edit
, is that correct?Apologies if this makes the devs cringe.
*Edited because I mixed up apply and add.
Beta Was this translation helpful? Give feedback.
All reactions