Skip to content

Feature/717 restrict allowed workflow names to WorkflowPatcher#718

Merged
ArBridgeman merged 7 commits intomainfrom
feature/717-restrict-workflow-names
Feb 19, 2026
Merged

Feature/717 restrict allowed workflow names to WorkflowPatcher#718
ArBridgeman merged 7 commits intomainfrom
feature/717-restrict-workflow-names

Conversation

@ArBridgeman
Copy link
Collaborator

@ArBridgeman ArBridgeman commented Feb 19, 2026

closes #717

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 changed the title Feature/717 restrict workflow names Feature/717 restrict allowed workflow names to WorkflowPatcher Feb 19, 2026
@sonarqubecloud
Copy link

@ArBridgeman ArBridgeman merged commit 93e573c into main Feb 19, 2026
67 checks passed
@ArBridgeman ArBridgeman deleted the feature/717-restrict-workflow-names branch February 19, 2026 11:54
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.

Restrict allowed workflow names to WorkflowPatcher

2 participants

Comments