diff options
| author | Hyteq <DerpsDer.es@gmail.com> | 2025-06-23 13:40:14 +0300 |
|---|---|---|
| committer | Hyteq <DerpsDer.es@gmail.com> | 2025-06-23 13:40:14 +0300 |
| commit | c55b7796a6b284f7184d7978bef0bc0706d81e20 (patch) | |
| tree | db8434509d72d4c620c65d03ca301ae37a5c8e9f | |
| parent | fd7ac5fd42e21dc963d9cc0477665e5fc574dac7 (diff) | |
| download | opencut-c55b7796a6b284f7184d7978bef0bc0706d81e20.tar.gz | |
fix: package json commands
| -rw-r--r-- | .github/CONTRIBUTING.md | 21 |
1 files changed, 12 insertions, 9 deletions
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 51893058..793d175e 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -6,8 +6,9 @@ Thank you for your interest in contributing to OpenCut! This document provides g 1. Fork the repository 2. Clone your fork locally -3. Install dependencies: `bun install` -4. Start the development server: `bun run dev` +3. Navigate to the web app directory: `cd apps/web` +4. Install dependencies: `bun install` +5. Start the development server: `bun run dev` ## Development Setup @@ -18,9 +19,10 @@ Thank you for your interest in contributing to OpenCut! This document provides g ### Local Development 1. Copy `.env.example` to `.env.local` and configure your environment variables -2. Start the database: `docker-compose up -d` -3. Run database migrations: `bun run db:migrate` -4. Start the development server: `bun run dev` +2. Start the database: `docker-compose up -d` (run from project root) +3. Navigate to the web app: `cd apps/web` +4. Run database migrations: `bun run db:migrate` +5. Start the development server: `bun run dev` ## How to Contribute @@ -37,16 +39,17 @@ Thank you for your interest in contributing to OpenCut! This document provides g ### Code Contributions 1. Create a new branch: `git checkout -b feature/your-feature-name` 2. Make your changes -3. Write tests for new functionality -4. Ensure all tests pass: `bun test` -5. Run the linter: `bun run lint` +3. Navigate to the web app directory: `cd apps/web` +4. Run the linter: `bun run lint` +5. Format your code: `bunx biome format --write .` 6. Commit your changes with a descriptive message 7. Push to your fork and create a pull request ## Code Style - We use Biome for code formatting and linting -- Run `bun run format` before committing +- Run `bunx biome format --write .` from the `apps/web` directory to format code +- Run `bun run lint` from the `apps/web` directory to check for linting issues - Follow the existing code patterns ## Pull Request Process |