Skip to content

Commit e88b8c7

Browse files
committed
Update documentation with exclusion & add summary to unreleased
1 parent 2064c8a commit e88b8c7

File tree

2 files changed

+21
-0
lines changed

2 files changed

+21
-0
lines changed

doc/changes/unreleased.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,18 @@
11
# Unreleased
22

3+
## Summary
4+
5+
This version of the PTB resolves many bugfixes associated with the cookiecutter template
6+
and creating a new project that uses the PTB.
7+
8+
If any directories or files specified in your `noxconfig.py` via `Config.source` should
9+
not be included in a Sonar analysis, it is recommended to add the following to
10+
your `pyproject.toml` under the `[tool.sonar]` section:
11+
12+
```toml
13+
exclusions = "<source-directory>/version.py,<source_directory>/<directory-to-ignore>/*"
14+
```
15+
316
## Bugfixes
417

518
* #489: Fixed .pre-commit-config.yaml to use existing nox tasks

doc/user_guide/getting_started.rst

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -229,6 +229,7 @@ For a **public** project
229229
projectKey = "com.exasol:<project-key>"
230230
hostUrl = "https://sonarcloud.io"
231231
organization = "exasol"
232+
exclusions = "<source-directory>/version.py,<source_directory>/<directory-to-ignore>/*"
232233
6. Post-merge, update the branch protections to include SonarQube analysis
233234

234235
* This should only be done when tests exist for the project, & that the project is
@@ -253,8 +254,15 @@ For a **private** project
253254
projectKey = "com.exasol:<project-key>"
254255
hostUrl = "https://sonar.exasol.com"
255256
organization = "exasol"
257+
exclusions = "<source-directory>/version.py,<source_directory>/<directory-to-ignore>/*"
256258
6. Post-merge, update the branch protections to include SonarQube analysis from exasonarqubeprchecks
257259

260+
* This should only be done when tests exist for the project, & that the project is
261+
at a state in which enforced code coverage would not be a burden. For new projects,
262+
we recommend creating an issue to add the SonarQube analysis to the branch protections
263+
at a later point. In such scenarios, SonarQube analysis will still report its analysis
264+
results to the PR, but it will not prevent the PR from being merged.
265+
258266
9. Go 🥜
259267
+++++++++++++
260268
You are ready to use the toolbox. With *nox -l* you can list all available tasks.

0 commit comments

Comments
 (0)