Recommend new users use the repo as a template instead of as a fork

[stephansama]

currently the recommended installation step is to fork the repo and then continue from there "kickstarting" your configuration. i think it would make more sense if the repo was converted into a template (similar to neovim-plugin-boilerplate) that way users do not get "out of sync" with something that they should only have used as a starting point.

https://github.com/nvim-lua/kickstart.nvim?tab=readme-ov-file#recommended-step

[guru245]

I like this opinion. This can prevent users from sending a false pull request.

[Sefriol]

No. This is actually a great feature and allows you to update changes to your configuration, if you so desire. I have done this multiple times and regularly update my own fork.

Guide should be updated, recommending you to do your changes in your own branch after forking. This way you can easily sync changes to your fork's main branch and rebase fast forward them.

I have used this workflow over a year with only minor merge conflicts.

False pull requests might be a nuisance to the maintainers, but also quite easy to notice.

[stephansama]

No. This is actually a great feature and allows you to update changes to your configuration, if you so desire. I have done this multiple times and regularly update my own fork.

Guide should be updated, recommending you to do your changes in your own branch after forking. This way you can easily sync changes to your fork's main branch and rebase fast forward them.

I have used this workflow over a year with only minor merge conflicts.

False pull requests might be a nuisance to the maintainers, but also quite easy to notice.

This is an interesting point. I personally do not use kickstart so I am not super opinionated on it. I just noticed this when I was helping someone who uses it. And thought it could potentially help others. Curious what others think as well.

[JoniBecker]

Neovim-Newb perspective:
I've been using kickstart as a starting point for quite a while but never really did much with my nvim config, only updating my fork a couple of times. However, between the last two times updating my fork, I wrote a small nvim plugin for myself. When it came to updating my fork again like an hour ago, I intuitively also settled on moving my custom configuration into a custom branch, discarding the custom commits from my main branch and rebasing my custom branch onto main once I updated the fork.

What I'm trying to say: At least from my limited amount of experience, this seems like a rather intuitive way to go about things (admittedly, I have a relevant amount of experience working with git in professional settings, so not sure how intuitive this would be for someone who is also new to working with git).