Thank you for your interest in contributing! This guide explains how to propose changes and how to build and publish a new release.
- Fork the repository and create a feature branch.
- Make your changes and ensure all tests pass:
npm run lint npm run test - Open a Pull Request targeting the
mainbranch.
Releases are published to the VSCode Marketplace and require the following steps:
- Bump the version in
package.json(e.g., from1.0.0to1.0.1). - Generate the changelog for the new version:
uv tool run towncrier build --version=<new-version> --yes
- Commit the updated
package.jsonandCHANGELOG.md. - Open a PR with these changes and wait for it to be reviewed and merged into
main.
Once your PR is merged:
- Create a new git tag for the release:
git tag v<new-version> git push --tags
This will trigger CI to publish the extension to the VSCode Marketplace.
- Ensure your PR includes only relevant changes for the release.
- All code must pass linting and tests before merging.
- For questions, open an issue or ask in the project discussions.
Thank you for helping improve