mirror
/
kickstart.nvim
mirror of https://github.com/nvim-lua/kickstart.nvim.git
1
0
Fork 1
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #2068 from stephansama/feature/update-readme-for-templating 

chore: updated readme
This commit is contained in:
Ori Perry 2026-07-25 21:47:36 +03:00 committed by GitHub
parent 216e06a36d 7a3532ac07
commit 267fb6aa73
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 16 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
README.md
View File

@ -61,23 +61,32 @@ Neovim's configurations are located under the following paths, depending on your
#### Recommended Step #### Recommended Step
[Fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) this repo Create your own copy of this repo using GitHub's
so that you have your own copy that you can modify, then install by cloning the ["Use this template"](https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template)
fork to your machine using one of the commands below, depending on your OS. button so that you have your own copy that you can modify, then install by
cloning your new repo to your machine using one of the commands below,
depending on your OS.
Alternatively, you can [fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo)
this repo if you prefer an easy upstream sync path (e.g., keeping your config
on a separate branch and fast-forwarding `master` from upstream). See the
[discussion in #1740](https://github.com/nvim-lua/kickstart.nvim/issues/1740)
for the tradeoffs between the two approaches.
> [!NOTE] > [!NOTE]
> Your fork's URL will be something like this: > Your repo's URL will be something like this:
> `https://github.com/<your_github_username>/kickstart.nvim.git` > `https://github.com/<your_github_username>/kickstart.nvim.git`
You likely want to remove `nvim-pack-lock.json` from your fork's `.gitignore` You likely want to remove `nvim-pack-lock.json` from your repo's `.gitignore`
file too - it's ignored in the kickstart repo to make maintenance easier, but file too - it's ignored in the kickstart repo to make maintenance easier, but
it's recommended to track it in version control (see `:help vim.pack-lockfile`). it's recommended to track it in version control (see `:help vim.pack-lockfile`).
#### Clone kickstart.nvim #### Clone kickstart.nvim
> [!NOTE] > [!NOTE]
> If following the recommended step above (i.e., forking the repo), replace > If following the recommended step above (i.e., creating your own repo from
> `nvim-lua` with `<your_github_username>` in the commands below > the template or fork), replace `nvim-lua` with `<your_github_username>`
> in the commands below
<details><summary> Linux and Mac </summary> <details><summary> Linux and Mac </summary>