Skip to content

Latest commit

 

History

History
54 lines (38 loc) · 2.25 KB

CONTRIBUTING.md

File metadata and controls

54 lines (38 loc) · 2.25 KB

Contributing

Thank you for your invested time to make this project even better. This guide supports developers in contributing issues and code.

Issues

When opening an issue, describe your issue as clear as possible. If useful, provide code or an example repository.

Workflow

This project uses the GitHub Flow.

Testing & Linting

The following commands support you at developing good code:

  • npm run code-analysis: Run the static code analysis
  • npm run test: Run the tests
  • npm run lint: Run the linter

Commit changes

Refer to this blogpost by cbeams when committing changes. Issue numbers can be added in braces to the end of the commit message.

It is also required to test your changes. Detailled information about test coverage will be published to coveralls.

Pull request

Remember to

  • bump a version,
  • update CHANGELOG.md and README.md

Publishing

After the pull request is merged, a tag can be created. When pushing a tag, GitHub Actions will automatically push the packaged project to the Visual Studio Marketplace and Open VSX Registry.

This is done by executing the commands:

vsce publish -p TOKEN --packagePath PACKAGE.vsix
npx ovsx publish -p TOKEN PACKAGE.vsix

Get tokens under:

Quality Gateway

SonarCloud

Find analysis on sonarcloud.io

DeepSource

Find analysis on deepsource.io

CodeFactor

CodeFactor

Find analysis on codefactor.io

Security

Find analysis on snyk.io