chore: updated readme

This commit is contained in:
stephansama 2026-05-28 04:07:22 -04:00
parent cfdc17be3a
commit f1de74680a
No known key found for this signature in database
GPG Key ID: 4B38234D51C44328
1 changed files with 10 additions and 7 deletions

View File

@ -61,23 +61,26 @@ Neovim's configurations are located under the following paths, depending on your
#### Recommended Step
[Fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) this repo
so that you have your own copy that you can modify, then install by cloning the
fork to your machine using one of the commands below, depending on your OS.
Create your own copy of this repo using GitHub's
["Use this template"](https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template)
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.
> [!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`
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
it's recommended to track it in version control (see `:help vim.pack-lockfile`).
#### Clone kickstart.nvim
> [!NOTE]
> If following the recommended step above (i.e., forking the repo), replace
> `nvim-lua` with `<your_github_username>` in the commands below
> If following the recommended step above (i.e., creating your own repo from
> the template), replace `nvim-lua` with `<your_github_username>` in the
> commands below
<details><summary> Linux and Mac </summary>