remove nightly leftovers

[NobbZ]

Summary by CodeRabbit

• Documentation

  • Revised update instructions in the project guide, including a modified command for updating plugins and removal of outdated Neovim update instructions.

• Chores

  • Removed legacy tools and configurations for handling Neovim dependency updates.
  • Eliminated the previous dependency tracking file to streamline the update process.

[coderabbitai]

📝 Walkthrough

Walkthrough

This change updates the repository's Neovim update process by modifying command references and removing obsolete update logic. The README now uses nix run .#update-plugins for updating plugins, and the separate Neovim update functionality has been removed. Related packages, checks, scripts, and dependency tracking files have been deleted.

Changes

File(s)	Change Summary
README.md	Updated the update process instructions by removing the Neovim lock file update command and changing the plugin update command from nix run .#updatePlugins to nix run .#update-plugins.
bin/default.nix	Removed the update-nvim package definition and its corresponding check from the packages and checks sections.
bin/update-nvim.exs, bin/update-nvim.nix, deps.txt	Deleted files that provided the Neovim update functionality and dependency tracking.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant CLI
    participant PluginUpdater

    User->>CLI: Run "nix run .#update-plugins"
    CLI->>PluginUpdater: Initiate plugin update process
    PluginUpdater-->>CLI: Process complete
    CLI-->>User: Return update status

Loading

Possibly related PRs

• remove nightly leftovers #46: The changes in the main PR are directly related to those in the retrieved PR, as both involve modifications to the same commands in the README.md file regarding the Neovim update process.
• update 2025 02 03 #23: The changes in the main PR are related to the removal of the update-nvim package and its associated commands, while the retrieved PR involves renaming the update-nvim key in the packages section, indicating a direct connection in the context of package management for Neovim.

Poem

I'm a rabbit with a code-filled heart,
Hopping through changes with a joyful start,
Old scripts gone, new commands in view,
In every line, the magic is true,
🐇 Leaping ahead—code dreams coming through!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e8d535b and 85e8be1.

📒 Files selected for processing (1)

• README.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• README.md

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

README.md (2)

13-18: Numbering Consistency in Update Process:
The steps in the update process show a jump from step 3 directly to step 6. If the removal of outdated steps (such as the nightly update or related logic) is intentional, consider renumbering the remaining steps (or adding a brief note) to improve clarity for users.

🧰 Tools

🪛 LanguageTool

[grammar] ~18-~18: The singular determiner ‘this’ may not agree with the plural noun ‘instructions’. Did you mean “these”?
Context: ...* fix build errors 8. optional update this instructions 😀 Inspiration ----------...

(THIS_NNS)

---

18-18: Typographical Improvement:
The phrase "optional update this instructions" on line 18 could be revised to "optional update these instructions" for grammatical correctness.

🧰 Tools

🪛 LanguageTool

[grammar] ~18-~18: The singular determiner ‘this’ may not agree with the plural noun ‘instructions’. Did you mean “these”?
Context: ...* fix build errors 8. optional update this instructions 😀 Inspiration ----------...

(THIS_NNS)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7ff580e and e8d535b.

📒 Files selected for processing (5)

• README.md (1 hunks)
• bin/default.nix (0 hunks)
• bin/update-nvim.exs (0 hunks)
• bin/update-nvim.nix (0 hunks)
• deps.txt (0 hunks)

💤 Files with no reviewable changes (4)

• bin/default.nix
• deps.txt
• bin/update-nvim.nix
• bin/update-nvim.exs

🔇 Additional comments (1)

README.md (1)

16-16: Updated Plugin Update Command:
The command for updating plugins has been updated from nix run .#updatePlugins to nix run .#update-plugins, which aligns with the new update process and removes obsolete logic.