Skip to content

docs: add getting started guide for local setup #3436

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

Umeshinduranga
Copy link

@Umeshinduranga Umeshinduranga commented Aug 4, 2025

Please provide enough information so that others can review your pull request:

Explain the details for making this change. What existing problem does the pull request solve?

Screenshots/GIFs

Summary by CodeRabbit

  • Documentation
    • Added a "Getting Started (Local Setup)" section to the README with prerequisites and initial setup instructions for running the project locally.

Copy link

coderabbitai bot commented Aug 4, 2025

Walkthrough

A new "Getting Started (Local Setup)" section was added to the README.md file, providing step-by-step instructions for setting up the project locally. This includes a list of prerequisites and initial repository cloning commands. No existing documentation was modified or removed.

Changes

Cohort / File(s) Change Summary
README Local Setup Additions
README.md
Added a "Getting Started (Local Setup)" section with prerequisites and repository cloning steps.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇
A README grows, a guide anew,
With steps for local setup too!
Prereqs listed, clone away,
Hop into code without delay.
So grab your keys and follow through—
The rabbit’s path is clear for you!

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
  • 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 explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @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.

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)
README.md (1)

34-35: Avoid introducing an isolated horizontal rule

The README already follows a clear sectional hierarchy. Adding an extra --- here interrupts the visual flow without adding real value. Consider dropping the rule or relocating it to match the style used elsewhere in the document.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between be497bc and 51d9ef3.

📒 Files selected for processing (1)
  • README.md (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Summary

Comment on lines +36 to +52
## 🚀 Getting Started (Local Setup)

To run this project locally, follow these steps:

### 🧰 Prerequisites

- Python 3.8+
- Node.js & Yarn
- Frappe Framework
- Redis, MariaDB, Node.js, and other Frappe dependencies

### 🔽 1. Clone the Repository

```bash
git clone https://github.com/Umeshinduranga/hrms.git
cd hrms

Copy link

Choose a reason for hiding this comment

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

💡 Verification agent

🧩 Analysis chain

New “Getting Started” block duplicates partial content and needs clean-up

  1. Content overlap – A complete local setup guide already exists under “Development setup → Local”. Maintaining two divergent instructions quickly gets outdated and confuses newcomers.
  2. Incomplete steps – The section stops after cloning; prerequisites such as bench init, environment variables, site creation, or Docker are missing.
  3. Wrong clone URL – Use the canonical repository (frappe/hrms) rather than the author’s fork so copy-pasting always works.
  4. Redundant bullet – “Node.js” is listed twice (with and without Yarn).
  5. Version specifics – Frappe Framework and Python versions should be pinned (Frappe v15+, Python 3.10+, etc.) to avoid mismatch errors.

A concise fix could be either to (a) delete this block and point readers to the existing “Development setup”, or (b) fully flesh it out and remove the older section.

Example minimal patch if you keep the block:

-### 🧰 Prerequisites
-
-- Python 3.8+
-- Node.js & Yarn
-- Frappe Framework
-- Redis, MariaDB, Node.js, and other Frappe dependencies
+### 🧰 Prerequisites
+
+- Python 3.10 or higher
+- Node.js (v18 LTS) & Yarn
+- Frappe Framework (v15+)
+- Redis, MariaDB, and other Frappe dependencies

```bash
-git clone https://github.com/Umeshinduranga/hrms.git
+git clone https://github.com/frappe/hrms.git
 cd hrms

Then continue with `bench init`, site creation, etc., or simply refer to the “Development setup” section to keep docs DRY.

---

🏁 Script executed:

```shell
#!/bin/bash
# Display the first 200 lines of README.md with line numbers
sed -n '1,200p' README.md | nl -ba
echo "-----"
# Find any 'Development setup' occurrences
grep -R "Development setup" -n README.md

Length of output: 213


Remove or Consolidate Duplicate “Getting Started” Section

The new block in README.md (lines 36–52) repeats the later Development setup section (line 97). To keep docs DRY and up-to-date:

• Location: README.md (lines 36–52) – the "🚀 Getting Started (Local Setup)" block.
• Option A: Delete this entire block and add a pointer to Development setup → Local.
• Option B: Fully flesh out the block and drop the older section:
– Prerequisites (pin versions):
• Python 3.10+
• Node.js 18 LTS & Yarn
• Frappe v15+
• Redis, MariaDB
– Update clone URL:
bash git clone https://github.com/frappe/hrms.git cd hrms
– Add missing steps (bench init, environment variables, site creation), or refer readers to the detailed “Development setup” section.
• Remove the redundant “Node.js” bullet and ensure version specifics are accurate.

🤖 Prompt for AI Agents
In README.md between lines 36 and 52, the "Getting Started (Local Setup)"
section duplicates content found later in the "Development setup" section around
line 97. To fix this, either delete the entire "Getting Started" block and
replace it with a clear pointer directing readers to the "Development setup →
Local" section, or fully expand the "Getting Started" block with accurate
prerequisites including pinned versions (Python 3.10+, Node.js 18 LTS & Yarn,
Frappe v15+, Redis, MariaDB), update the clone URL to
https://github.com/frappe/hrms.git, add missing setup steps like bench
initialization, environment variables, and site creation, and then remove the
older redundant section to avoid duplication.

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