You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+9-2Lines changed: 9 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -99,10 +99,10 @@ We have several types of tests:
99
99
* View tests: these live in `src/view/variant-analysis/__tests__/`
100
100
* VSCode integration tests:
101
101
*`test/vscode-tests/activated-extension` tests: These are intended to cover functionality that require the full extension to be activated but don't require the CLI. This suite is not run against multiple versions of the CLI in CI.
102
-
*`test/vscode-tests/no-workspace` tests: These are intended to cover functionality that is meant to work before you even have a workspace open but don't require the extension to be activated.
102
+
*`test/vscode-tests/no-workspace` tests: These are intended to cover functionality around not having a workspace. The extension is not activated in these tests.
103
103
*`test/vscode-tests/minimal-workspace` tests: These are intended to cover functionality that need a workspace but don't require the full extension to be activated.
104
104
* CLI integration tests: these live in `test/vscode-tests/cli-integration`
105
-
* These tests are intended to be cover functionality that is related to the integration between the CodeQL CLI and the extension. These tests are run against all supported versions of the CLI in CI.
105
+
* These tests are intended to cover functionality that is related to the integration between the CodeQL CLI and the extension. These tests are run against each supported versions of the CLI in CI.
106
106
107
107
The CLI integration tests require an instance of the CodeQL CLI to run so they will require some extra setup steps. When adding new tests to our test suite, please be mindful of whether they need to be in the cli-integration folder. If the tests don't depend on the CLI, they are better suited to being a VSCode integration test.
108
108
@@ -229,6 +229,13 @@ Pre-recorded scenarios are stored in `./src/mocks/scenarios`. However, it's poss
229
229
1. Double-check the `CHANGELOG.md` contains all desired change comments and has the version to be released with date at the top.
230
230
* Go through all recent PRs and make sure they are properly accounted for.
231
231
* Make sure all changelog entries have links back to their PR(s) if appropriate.
232
+
* For picking the new version number, we default to increasing the patch version number, but make our own judgement about whether a change is big enough to warrant a minor version bump. Common reasons for a minor bump could include:
233
+
* Making substantial new features available to all users. This can include lifting a feature flag.
234
+
* Breakage in compatibility with recent versions of the CLI.
235
+
* Minimum required version of VS Code is increased.
236
+
* New telemetry events are added.
237
+
* Deprecation or removal of commands.
238
+
* Accumulation of many changes, none of which are individually big enough to warrant a minor bump, but which together are. This does not include changes which are purely internal to the extension, such as refactoring, or which are only available behind a feature flag.
232
239
1. Double-check that the node version we're using matches the one used for VS Code. If it doesn't, you will then need to update the node version in the following files:
233
240
*`.nvmrc` - this will enable `nvm` to automatically switch to the correct node version when you're in the project folder
234
241
*`.github/workflows/main.yml` - all the "node-version: <version>" settings
0 commit comments