Skip to content

Commit 53a5e8c

Browse files
Updated CONTRIBUTING.md
1 parent c686e77 commit 53a5e8c

1 file changed

Lines changed: 5 additions & 6 deletions

File tree

.github/CONTRIBUTING.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,23 +5,22 @@ Thanks for your interest in contributing! Here's what you need to know.
55
## Getting started
66

77
1. Fork the repository and clone your fork
8-
2. Run `npm install` to install Node dependencies
9-
3. Run the setup script for Python: `scripts/setup.ps1` (Windows) or `scripts/setup.sh` (Linux/macOS)
10-
4. Open the project in VS Code and press `F5` to launch the extension in a dev host window
8+
2. Run the script to setup the development environment: `scripts/init-dev-env.ps1` (Windows) or `scripts/init-dev-env.sh` (Linux/macOS)
9+
3. Open the project in VS Code and press `F5` to launch the extension in a dev host window
1110

1211
## Before submitting a PR
1312

1413
- Make sure the extension builds: `npm run build`
1514
- Run `npm run fix` to lint and format both TypeScript and Python
16-
- Keep changes focused one concern per PR
15+
- Keep changes focused - one concern per PR
1716
- Reference any related issue in your PR description (e.g. `Closes #123`)
1817
- Don't include unrelated formatting or whitespace changes
1918

2019
## Code style
2120

22-
- TypeScript source lives in `src/`, Python scripts in `python/`
21+
- TypeScript source lives in `src/`, Python scripts in `python/`, and local dependencies in `vendor/`
2322
- Follow the existing patterns in the file you're editing
24-
- Run `npm run fix` before submitting this runs both TypeScript and Python linting and formatting in one step
23+
- Run `npm run fix` before submitting - this runs both TypeScript and Python linting and formatting in one step
2524

2625
## Questions?
2726

0 commit comments

Comments
 (0)