This is an automated archive made by the Lemmit Bot.
The original was posted on /r/neovim by /u/XavierChanth on 2024-11-02 18:13:45+00:00.
Hi all, as the title states, I’m thinking about making a new git worktrees plugin.
I’m aware there is already git-worktree.nvim, it’s what I’m using now. To keep it short, it doesn’t quite fit my needs, even with hooks, hence I’m considering building another plugin.
The reason for a separate plugin is that git-worktree was designed to KISS, and what I would like to add would stray from that with the way things are currently designed.
What I am doing now is heavily wrapping worktree hooks and my keymaps with some additional checks and cached state that gets passed to the hooks, and it is unnecessarily complex.
What I would like to ask is:
- If you use git worktrees, what does your current workflow look like? What is it missing?
- Is there anything you think is unique to your git workflow that I should think about while designing this plugin?
- Are there any features you would want if you were to use this plugin?
You must log in or register to comment.