Skip to content

Conversation

ssz2605
Copy link

@ssz2605 ssz2605 commented Jun 27, 2025

📦 Added CONTRIBUTING.md file

Closes #73


📝 Description

This pull request adds a complete CONTRIBUTING.md file to the InPactAI repository.

The file provides detailed instructions on:

  • Cloning and setting up the project locally
  • Running the frontend, backend, and landing page
  • Testing setup
  • Best practices for contributing (PR etiquette, commit message formats, etc.)
  • Tech stack and repo structure

🔧 Changes Made

  • Added CONTRIBUTING.md with:
    • Project setup instructions for all directories
    • Testing instructions
    • Contribution guidelines and branch naming conventions
    • Tech stack and repo overview
    • Helpful links and default ports

📷 Screenshots or Visual Changes

Not applicable — Markdown file only


🤝 Collaboration

Collaborated with: @Aditya30ag


Checklist

Summary by CodeRabbit

  • Documentation
    • Added a comprehensive CONTRIBUTING.md file with guidelines for contributing, project setup instructions, testing procedures, branch and commit conventions, and support resources.

Added CONTRIBUTING.md file
Copy link
Contributor

coderabbitai bot commented Jun 27, 2025

Walkthrough

A new CONTRIBUTING.md file has been introduced, outlining contribution guidelines, setup instructions, testing procedures, branch and commit conventions, and repository structure for the InPactAI project. This document aims to guide contributors through onboarding, development, and submission processes.

Changes

File(s) Change Summary
CONTRIBUTING.md Added comprehensive contribution guidelines, setup instructions, and project overview.

Assessment against linked issues

Objective Addressed Explanation
Add CONTRIBUTING.md: Guidelines for setup, submitting issues/PRs, coding practices (#73)
Add CODE_OF_CONDUCT.md, SECURITY.md, LICENSE.md files for community and legal documentation (#73) Only CONTRIBUTING.md was added; other community files are not present in this change.

Poem

In the garden of code where contributors hop,
A new guide now blooms—no need to stop!
With branches and tests, and setup so clear,
The path for new bunnies is friendly and near.
So nibble the docs and let’s all unite—
For InPactAI’s future is looking quite bright!
🐇✨


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
🪧 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.
    • @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 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.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

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 generate sequence diagram to generate a sequence diagram of the changes in 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
Contributor

@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: 0

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

18-24: Add an upstream remote step for smoother syncs

Many new contributors forget to keep their fork in sync with the main repository. A quick step right after cloning prevents painful re-base surprises later.

 git clone https://github.com/<your-username>/InPactAI.git
 cd InPactAI
 git checkout -b feature/your-feature-name
+# Add the main repo as upstream to easily pull future updates
+git remote add upstream https://github.com/AOSSIE-Org/InPactAI.git

32-36: Specify the required Node version

Projects built with Vite often rely on recent Node features. Stating the minimum supported Node (e.g., >=18) avoids the “works on my machine” trap and saves newcomers troubleshooting time.


60-66: Make virtual-env activation cross-platform

source venv/bin/activate fails on Windows. A short note covering both shells keeps Windows contributors unblocked.

 source venv/bin/activate          # macOS / Linux
+# On Windows (PowerShell):
+# .\venv\Scripts\Activate.ps1

70-73: Prefer the modern docker compose CLI

Docker Compose v2 bundles with the Docker CLI; the dashed form is now legacy. Switching prevents “command not found” on fresh Docker installs.

-docker-compose up --build
+docker compose up --build

78-78: Wrap bare URLs to satisfy markdown-lint

Enclosing the URLs in angle brackets or back-ticks silences MD034 and renders consistently across Markdown viewers.

-> ℹ️ Default ports: Frontend & Landing Page → http://localhost:5173, Backend → http://localhost:8000
+> ℹ️ Default ports: Frontend & Landing Page → <http://localhost:5173>, Backend → <http://localhost:8000>

101-108: Remove the colon after “like” to fix grammar

LanguageTool flags the colon that follows a preposition. Dropping it keeps the sentence correct and still readable.

- - Use meaningful branch names like:
+ - Use meaningful branch names like
...
- - Commit messages should follow conventions like:
+ - Commit messages should follow conventions like

101-108: Consider linking to the Conventional Commits spec

You’re already nudging contributors toward feat: / fix: prefixes. Linking the official spec (https://www.conventionalcommits.org/) clarifies the full grammar and edge cases.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between d8b9ae5 and 5b01d28.

📒 Files selected for processing (1)
  • CONTRIBUTING.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
CONTRIBUTING.md

[typographical] ~101-~101: Do not use a colon (:) before a series that is introduced by a preposition (‘like’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...idelines - Use meaningful branch names like: - feature/add-authentication - fix/...

(RP_COLON)


[typographical] ~105-~105: Do not use a colon (:) before a series that is introduced by a preposition (‘like’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...mmit messages should follow conventions like: - feat: added reset password function...

(RP_COLON)

🪛 markdownlint-cli2 (0.17.2)
CONTRIBUTING.md

78-78: Bare URL used
null

(MD034, no-bare-urls)


78-78: Bare URL used
null

(MD034, no-bare-urls)

@ssz2605 ssz2605 closed this Jul 4, 2025
@ssz2605 ssz2605 reopened this Jul 5, 2025
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.

[DOCS] Add standard community files (CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, LICENSE) for GSoC practices.
1 participant