Skip to content

Conversation

@ArBridgeman
Copy link
Collaborator

closes #649

Checklist

Note: If any of the items in the checklist are not relevant to your PR, just check the box.

For any Pull Request

Is the following correct:

  • the title of the Pull Request?
  • the title of the corresponding issue?
  • there are no other open Pull Requests for the same update/change?
  • that the issue which this Pull Request fixes ("Fixes...") is mentioned?

When Changes Were Made

Did you:

  • update the changelog?
  • update the cookiecutter-template?
  • update the implementation?
  • check coverage and add tests: unit tests and, if relevant, integration tests?
  • update the User Guide & other documentation?
  • resolve any failing CI criteria (incl. Sonar quality gate)?

When Preparing a Release

Have you:

  • thought about version number (major, minor, patch)?
  • checked Exasol packages for updates and resolved open vulnerabilities, if easily possible?

@ArBridgeman ArBridgeman force-pushed the feature/649_restrict_noxconfig_usage branch from a49a72d to 221c089 Compare January 9, 2026 12:29
@sonarqubecloud
Copy link

sonarqubecloud bot commented Jan 9, 2026

@ArBridgeman ArBridgeman merged commit 7a1f59b into main Jan 9, 2026
123 checks passed
@ArBridgeman ArBridgeman deleted the feature/649_restrict_noxconfig_usage branch January 9, 2026 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Extend usage of import-linter

3 participants