-
-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
git-worktree v2 #115
Comments
would you like to fork this and have a "deprecation" message pointing towards your repo? i feel bad having you do all this work with not the full recognition you deserve! |
Up to you, you had the original idea |
NO! Its up to you! If you truly don't care, then i don't care. But if you would like that, i am here to support you. It requires work on your behalf. I am here to multiply not to own, i am fine letting go. |
If you have no plans to maintain it, sure I can take it over |
dealio, you can squash me out and or keep me. make your repo and we will point it over to yours! |
Right now I'm always linking my files that I have put in my .gitignore over to each new worktree. This is how I handle this for reference:
|
Adding this feature would be nice as well. It make the whole worktree experience a lot cleaner imo. I'm not sure if I can help with any of this, if there's anything I can do, please let me know 😄 |
I would have liked to have had this on the README. This was a challenge to find! |
i am looking into git-worktree v2 in honor of harpoon v2
I will try to cleanup issues / prs as well
Please comment with requests to add/modify features
My first priority is cleaning up the code to make it more maintainable
The text was updated successfully, but these errors were encountered: