Skip to content

docs: update contributing guide with uv development setup#66

Open
danieljrc888 wants to merge 1 commit intomainfrom
docs/update-contributing-uv-setup
Open

docs: update contributing guide with uv development setup#66
danieljrc888 wants to merge 1 commit intomainfrom
docs/update-contributing-uv-setup

Conversation

@danieljrc888
Copy link
Contributor

@danieljrc888 danieljrc888 commented Mar 1, 2026

Summary

  • Replace outdated pip-based dev setup instructions in CONTRIBUTING.md with uv commands (uv sync, uv run gltest)
  • Add a note linking to the uv installation guide for new contributors

Test plan

  • Verify the CONTRIBUTING.md renders correctly on GitHub
  • Verify uv sync and uv run gltest work as documented

🤖 Generated with Claude Code

Summary by CodeRabbit

Release Notes

  • Documentation
    • Simplified contribution setup process with streamlined installation instructions
    • Updated testing workflow with new commands for running tests
    • Enhanced setup guidance with explicit steps for cloning the repository and installing dependencies
    • Added references to dependency management documentation for contributors

Replace the outdated pip-based development setup instructions with
uv sync/run commands, matching the project's migration to uv for
dependency management.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@coderabbitai
Copy link

coderabbitai bot commented Mar 1, 2026

📝 Walkthrough

Walkthrough

Updated CONTRIBUTING.md to replace multiple setup and installation subsections with a streamlined workflow emphasizing uv for dependency management and testing. The changes consolidate instructions by removing redundant options and directing developers to use uv sync and uv run gltest.

Changes

Cohort / File(s) Summary
Documentation
CONTRIBUTING.md
Streamlined developer setup instructions by removing multiple installation options (1.3, 1.4_SETUP subsections) and consolidating into a single uv-based workflow with uv sync and uv run gltest commands.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

Suggested reviewers

  • MuncleUscles
  • cristiam86

Poem

🐰 Hopping through the docs with glee,
Old setup paths swept clean as can be!
uv sync, uv run—the way is clear,
Contributing guides now bright and near!

🚥 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 accurately describes the main change: updating the contributing guide to use uv for development setup, which matches the raw summary of replacing pip-based instructions with uv commands.
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.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch docs/update-contributing-uv-setup

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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
CONTRIBUTING.md (1)

38-53: Add explicit Python version prerequisite before setup commands.

Please state the required Python version (>=3.12) in this section so contributors don’t hit environment mismatch issues before running uv sync.

Based on learnings: Use Python >= 3.12 for development and ensure dependencies are synced via uv sync from the lockfile.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@CONTRIBUTING.md` around lines 38 - 53, Update the "1.3. Setup the package
locally" section to add an explicit Python prerequisite line stating "Python >=
3.12" before the clone/install commands, and mention that contributors should
use that Python version when running `uv sync`; also note to run `uv sync`
against the lockfile (e.g., use the project's lockfile) so dependencies are
deterministic.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CONTRIBUTING.md`:
- Around line 41-43: Remove the leading "$" prompt characters from the command
examples in the CONTRIBUTING.md command blocks so they are plain commands (e.g.,
"git clone https://github.com/genlayerlabs/genlayer-testing-suite.git", "cd
genlayer-testing-suite", "uv sync" and the similar command later in the file);
edit those lines to drop the "$" prefix to satisfy markdownlint MD014 and keep
command blocks free of prompt characters.

---

Nitpick comments:
In `@CONTRIBUTING.md`:
- Around line 38-53: Update the "1.3. Setup the package locally" section to add
an explicit Python prerequisite line stating "Python >= 3.12" before the
clone/install commands, and mention that contributors should use that Python
version when running `uv sync`; also note to run `uv sync` against the lockfile
(e.g., use the project's lockfile) so dependencies are deterministic.

ℹ️ Review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 32e76ee and 22b9afe.

📒 Files selected for processing (1)
  • CONTRIBUTING.md

Comment on lines 41 to +43
$ git clone https://github.com/genlayerlabs/genlayer-testing-suite.git
$ cd genlayer-testing-suite
$ uv sync
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Fix markdownlint MD014 warnings in command blocks.

Line 41, Line 42, Line 43, and Line 49 use $ prompts without command output, which triggers MD014. Remove the leading $ to match the repo’s linting expectations.

Suggested doc fix
-  $ git clone https://github.com/genlayerlabs/genlayer-testing-suite.git
-  $ cd genlayer-testing-suite
-  $ uv sync
+  git clone https://github.com/genlayerlabs/genlayer-testing-suite.git
+  cd genlayer-testing-suite
+  uv sync
...
-  $ uv run gltest
+  uv run gltest

Also applies to: 49-49

🧰 Tools
🪛 markdownlint-cli2 (0.21.0)

[warning] 41-41: Dollar signs used before commands without showing output

(MD014, commands-show-output)


[warning] 42-42: Dollar signs used before commands without showing output

(MD014, commands-show-output)


[warning] 43-43: Dollar signs used before commands without showing output

(MD014, commands-show-output)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@CONTRIBUTING.md` around lines 41 - 43, Remove the leading "$" prompt
characters from the command examples in the CONTRIBUTING.md command blocks so
they are plain commands (e.g., "git clone
https://github.com/genlayerlabs/genlayer-testing-suite.git", "cd
genlayer-testing-suite", "uv sync" and the similar command later in the file);
edit those lines to drop the "$" prefix to satisfy markdownlint MD014 and keep
command blocks free of prompt characters.

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.

1 participant