imp: adjust build output in Makefile target

[MalteHerrmann]

Problem

When running make build && sh local.sh, the script cannot execute because the expected binary is not found:

./local.sh: line 17: ./build/nobled: No such file or directory

Solution

This PR adjusts the output of the make build target to produce the binary at ./build/nobled. Currently, the binary is written to ./build, which does not work with the provided local.sh script, which expects the adjusted path.

Other than that, it updates an outdated Go developer wiki link in tools.go.

[coderabbitai]

Walkthrough

The pull request introduces minor modifications to the project's build configuration and documentation link. The Makefile has been updated to specify a more organized output directory for the compiled binary, directing the build output to a "build" subdirectory. Simultaneously, the tools.go file's comment contains an updated URL reference for tracking tool dependencies, pointing to the latest Go module documentation location.

Changes

File	Change Summary
Makefile	Updated build command to output binary to $(PWD)/build/nobled instead of $(PWD)/build
tools.go	Updated documentation URL for tool dependency tracking

Poem

🐰 A Rabbit's Build Ballad 🏗️

In Makefile's realm, a path anew,
Build directory, crisp and true
A link refreshed with gentle care
Documentation's journey rare
Code marches on, both swift and bright! 🚀

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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 (1)

Makefile (1)

52-52: Consider adding directory creation step.

While the output path is correct, the build might fail if the build directory doesn't exist. Consider adding a directory creation step.

 build:
 	@echo "🤖 Building nobled..."
+	@mkdir -p build
 	@go build -mod=readonly $(BUILD_FLAGS) -o "$(PWD)/build/nobled" ./cmd/nobled
 	@echo "✅ Completed build!"

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ff1e521 and 567020e.

📒 Files selected for processing (2)

• Makefile (1 hunks)
• tools.go (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• tools.go

🔇 Additional comments (1)

Makefile (1)

52-52: LGTM! Output path aligns with local.sh requirements.

The change correctly specifies the binary output location as $(PWD)/build/nobled, which fulfills the PR objective of making it compatible with the local.sh script.