Contributing

January 20, 2026 · View on GitHub

:+1::tada: First off, thanks for taking the time to contribute! :tada::+1:

We welcome contributions of any kind including documentation, organization, tutorials, bug reports, issues, feature requests, feature implementations, pull requests, answering questions on the mailing list, helping to manage issues, etc.

Asking Support Questions

We use mailing list ntt@groups.io where users and developers can ask questions. Please don't use the GitHub issue tracker to ask questions.

Reporting Issues

If you believe you have found an issue, please use the GitHub issue tracker to report the Problem. If you're not sure if it's a bug or not, start by asking on the mailing list ntt@groups.io.

Building the extension

Install dependencies:

npm install

Create package:

vsce package

Pull Requests

Fork and clone the repository
Create a new branch: git checkout -b my-branch-name
Make your change and remember to add tests (if possible)
Build the project locally and run local tests (if there are any)
Push to your fork and submit a pull request
Pat your self on the back and wait for your pull request to be reviewed and merged.

Here are a few things you can do that will increase the likelihood of your pull request being accepted:

Write tests.
Format your code.
Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, submit them as separate pull requests.
Write good commit messages.

Release the extension

Draft a new release.
Enter the version tag (e.g. v0.10.3)
Fill out remaining information
Press "Publish release"

Note: Automatic releasing requires a Azure DevOps Personal Access Token as the secret variable VSCE_PAT.

These tokens have a limited validity, you might have to create a new one.

The version is derived from the tag name, you don't need to increase it manually.

Issue and Pull Request Labels

Labels help us track and manage issues and pull requests.

Label Name		Description
`enhancement`	search	Feature Requests
`bug`	[search][search-label-bug]	Something isn't working
`duplicate`	search	This issue or pull request already exists
`good first issue`	search	Good for newcomers
`help wanted`	search	Extra attention is needed
`invalid`	search	This doesn't seem right
`question`	search	Further information is requested
`wontfix`	search	This will not be worked on