Thank you for your interest in contributing to Snapshots for AI! We welcome contributions from the community to help make this extension even better.
- Fork the repository
- Clone your fork
- Create a new branch for your feature or bug fix
- Make your changes
- Submit a pull request
- Install Node.js and npm
- Clone the repository
- Run
npm install
to install dependencies - Open the project in VS Code
- Press F5 to start debugging
- Node.js (v14 or higher)
- npm (v6 or higher)
- Visual Studio Code (for testing)
-
Clone the repository:
git clone https://github.com/gbti/vscode-snapshots-for-ai.git cd vscode-snapshots-for-ai
-
Install dependencies:
npm install
-
Compile the extension:
npm run compile
For extension maintainers, the following deployment commands are available:
# Local Development (no publish)
npm run deploy # Increment patch version without publishing
npm run deploy:patch # Same as above, explicit patch version
# Publishing Commands
npm run deploy:minor # Increment minor version and publish
npm run deploy:major # Increment major version and publish
Each deployment command will:
- Increment the version number according to semantic versioning
- Clean the output directories
- Install dependencies
- Compile TypeScript
- Package the extension
- Publish to the marketplace (only for minor and major versions)
Note: To publish the extension, you need to set up the following environment variables:
VSCODE_PUBLISHER_ID
: Your VS Code marketplace publisher IDVSCE_PAT
: Personal Access Token for the VS Code marketplace
You can copy .env.example
to .env
and fill in these values.
- Press F5 in VS Code to launch a development instance
- The extension will be automatically loaded
- Package the extension:
npx @vscode/vsce package
- Install the generated
.vsix
file in WindSurf
- Package the extension as above
- Install the
.vsix
file in Cursor - Test functionality in Cursor's environment
npm run test
- Write clear commit messages
- Follow the existing code style
- Add appropriate comments and documentation
- Update the README.md if necessary
- Add tests for new features
- Update the README.md with details of changes if needed
- Update the version number following semantic versioning
- The PR will be merged once you have the sign-off of a maintainer
Please note that this project is released with a Contributor Code of Conduct. By participating in this project, you agree to abide by its terms.