Skip to content

Conversation

@ArBridgeman
Copy link
Collaborator

@ArBridgeman ArBridgeman commented Feb 3, 2026

closes #686

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 refactoring/686_output_yaml_values branch from 193ac43 to 1098983 Compare February 4, 2026 11:02
@ArBridgeman ArBridgeman force-pushed the refactoring/686_output_yaml_values branch from 1098983 to c1511ae Compare February 4, 2026 13:58
@ArBridgeman ArBridgeman force-pushed the refactoring/686_output_yaml_values branch from c1511ae to 4f37476 Compare February 4, 2026 13:59
@ArBridgeman ArBridgeman deployed to manual-approval February 4, 2026 14:00 — with GitHub Actions Active
@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 4, 2026

@ArBridgeman ArBridgeman marked this pull request as ready for review February 4, 2026 14:13
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.

Use yaml-reader to output GitHub workflows

2 participants