evil-helix git branches

[turbofish-pk]

I am excited I found this project.

What you are doing appears to be the same to what I wanted to do for me. Namely to fork helix and make it behave like neovim with respect to motions, selections etc.
My problem is that I am finding difficult to navigate your repo with all of its branches. My plan was to fork and clone everything locally and start experimenting.

Could you please give me a couple of tips, which branches are relevant and how to proceed?

Thanks a lot in advance.

PS
In case it matters I work on windows 11.

[turbofish-pk]

I don't see any interest in providing info, so I am closing it.

[usagi-flow]

Hey there @python-pk, sorry for replying just now. I didn't notice this discussion earlier. Please don't hesitate to leave a discussion/issue open if it's still relevant/unanswered, because these do not get overlooked so easily.

As with many repositories, you can consider the main branch the only interesting branch, and you can ignore the other branches. The many other branches are feature branches.

As with forking, there is nothing really specific to this repository. I recommend forking it (if you want to fork it) using the button in GitHub, and then cloning your fork. Additionally, if you plan on maintaining your fork, I recommend adding a remote named "upstream" or similar, which points to this repository (instead of your fork). That allows you to easily update your fork locally, compare it to the upstream (this repository), ...

Once you cloned your fork (or this repository directly) you can consider this project as a pretty regular Rust project, so what you'll do from here will be similar as with most other projects. cargo check to check if it compiles, cargo build to produce a debug build, and so on... (Of course, you need a rust toolchain for that; but again, that's nothing specific to this repository).

Let me know if you need more specific information.

[turbofish-pk]

Hey @usagi-flow, thanks a ton for the info — really helpful!

I’ll fork the repo and get everything set up like you suggested. I’m checking out the evil-helix fork because I’d love to see Neovim-style motions in Helix, and this looks like a really cool direction.

For now, I’ll spend some time exploring and testing the codebase. If things click, I’d love to contribute.

Appreciate the help, and looking forward to seeing how this evolves!

PS
As a first step I will compare the original codebase with this codebase to see where it has been modified etc.

In any case I will keep in touch. Have a great day.