Skip to content

Conversation

@horriblename
Copy link
Collaborator

  • adds a note on new LSP config in release notes
  • update docs on language module to use new API
  • link each vim.languages.<lang>.lsp.servers to vim.lsp.servers in the description

Sanity Checking

  • I have updated the changelog as per my changes
  • I have tested, and self-reviewed my code
  • My changes fit guidelines found in hacking nvf
  • Style and consistency
    • I ran Alejandra to format my code (nix fmt)
    • My code conforms to the editorconfig configuration of the project
    • My changes are consistent with the rest of the codebase
  • If new changes are particularly complex:
    • My code includes comments in particularly complex areas
    • I have added a section in the manual
    • (For breaking changes) I have included a migration guide
  • Package(s) built:
    • .#nix (default package)
    • .#maximal
    • .#docs-html (manual, must build)
    • .#docs-linkcheck (optional, please build if adding links)
  • Tested on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin

Add a 👍 reaction to pull requests you find important.

@github-actions
Copy link

github-actions bot commented Aug 30, 2025

🚀 Live preview deployed from 8e9186e

View it here:

Debug Information

Triggered by: horriblename

HEAD at: format-md

Reruns: 1448

github-actions bot pushed a commit that referenced this pull request Sep 6, 2025
@horriblename horriblename force-pushed the format-md branch 4 times, most recently from 0c04776 to c9bb5a7 Compare September 10, 2025 08:47
github-actions bot pushed a commit that referenced this pull request Sep 10, 2025
@horriblename horriblename force-pushed the v0.8 branch 2 times, most recently from 8b98f07 to ba9ce8b Compare September 13, 2025 07:23
github-actions bot pushed a commit that referenced this pull request Sep 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants