Skip to content

Clarify comment in .gitignore for lazy-lock.json#1896

Merged
oriori1703 merged 1 commit intonvim-lua:masterfrom
giogt:fix-gitignore-lazylock-comment
Feb 27, 2026
Merged

Clarify comment in .gitignore for lazy-lock.json#1896
oriori1703 merged 1 commit intonvim-lua:masterfrom
giogt:fix-gitignore-lazylock-comment

Conversation

@giogt
Copy link
Contributor

@giogt giogt commented Feb 22, 2026

The current comment in .gitignore for lazy-lock.json suggests to uncomment it yourself, but you actually need to comment it instead.

This change modifies the comment to clarify the recommended approach for kickstart users.

The current comment in .gitignore for lazy-lock.json suggests to
uncomment it yourself, but you actually need to comment it instead.

This change modifies the comment to clarify the recommended approach for
kickstart users.
@oriori1703
Copy link
Collaborator

Makes sense :)

@oriori1703 oriori1703 merged commit a4bbfdc into nvim-lua:master Feb 27, 2026
1 check passed
# but for kickstart, it makes sense to leave it ignored.
# You likely want to comment this, since it's recommended to track lazy-lock.json in version
# control, see https://lazy.folke.io/usage/lockfile
# For kickstart, it makes sense to leave it ignored.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd suggest a slight further clarification:

Suggested change
# For kickstart, it makes sense to leave it ignored.
# For the canonical kickstart git repository, it makes sense to leave it ignored.

since otherwise it could be confusing for someone who interprets kickstart to more generally refer to this base set of nvim configuration they start from.

Copy link
Contributor

@rmacklin rmacklin Feb 28, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Opened a PR here (slightly improved from what I suggested above): #1914

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants