integration with VCSH dotfile-in-git manager

[thkoch2001]

VCSH manages dotfiles in git repos just by setting $GIT_DIR and core.worktree. This way one can treat ones home dir like a git repository but there's no .git folder in $HOME.

I've used VCSH before I started using home-manager and use both in parallel now. The following home-manager snippet creates $HOME/.gitignore thus that VCSH ignores files managed by home-manager:

  home.activation.gitignore-for-vcsh = lib.hm.dag.entryAfter ["writeBoundary"] ''
    (cd $newGenPath/home-files && run find . \( -type f -or -type l \) -printf "%h/%f\n" | cut -c 2- > "$HOME/.gitignore" )
    run echo "/.gitignore" >> "$HOME/.gitignore"
  '';

I'd propose to make the above snippet somehow available under a home-manager option.

VCSH has the advantage that one can just edit config files directly and see the effect immediately without a build step.

You can see my VCSH repo at https://github.com/thkoch2001/general-config/tree/nixos

[teto]

The following home-manager snippet creates $HOME/.gitignore thus that VCSH ignores files managed by home-manager:

why does VCSH care about home-manager files in the first place ? HM does not handle $HOME as a git folder ? There are many ways to handle dotfiles, that snippet is maybe too specific to go in HM ?

[stale[bot]]

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

• If this is resolved, please consider closing it so that the maintainers know not to focus on this.
• If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough.
• If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

• If you are also experiencing this issue, please add details of your situation to help with the debugging process.
• If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.