Skip to content

Conversation

@augustos0204
Copy link
Contributor

@augustos0204 augustos0204 commented Jan 26, 2026

The fix updates the command to point to the correct package under cmd/lazypg, where the CLI entry point is defined.


✅ What was changed

  • Fixed the go install command in the README
  • Ensured compatibility with Go Modules using @latest
  • Improved the installation experience for new users

💡 Motivation

This change prevents installation errors and follows the standard Go CLI project structure, where binaries are usually located under cmd/<cli-name>.


🧪 How to test

go install github.com/rebelice/lazypg/cmd/lazypg@latest


<!-- This is an auto-generated comment: release notes by coderabbit.ai -->

## Summary by CodeRabbit

* **Documentation**
  * Updated installation instructions to specify a more targeted module path for the installation process.

<sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub>

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

@coderabbitai
Copy link

coderabbitai bot commented Jan 26, 2026

📝 Walkthrough

Walkthrough

The Go installation command in README.md has been updated to target the specific module path github.com/rebelice/lazypg/cmd/lazypg@latest instead of the root module during installation.

Changes

Cohort / File(s) Summary
Documentation
README.md
Updated Go install command to specify the target module path with @latest version

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A rabbit hops through docs with glee,
The install path now clear to see,
From root to cmd, a subtle shift,
This guidance gives a helpful lift! 🐰✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'fix: Fix path of go install lazypg' directly relates to the main change: updating the go install command path in README.md from the root module to the correct CLI entry point at cmd/lazypg.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@augustos0204 augustos0204 changed the title fix: Fix path of go install lazypg fix(README): Fix path of go install lazypg Jan 26, 2026
Copy link
Collaborator

@rebelice rebelice left a comment

Choose a reason for hiding this comment

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

Thanks for your contribution! LGTM

@rebelice rebelice merged commit b19700d into pgplex:main Feb 6, 2026
7 checks passed
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.

2 participants