Skip to content

feat(kotlin): forward migration-naming-pattern to check-migration-order [NOJIRA] - #370

Merged
hauke-d merged 1 commit into
mainfrom
feat/kotlin-migration-naming-pattern
Oct 2, 2026
Merged

hauke-d merged 1 commit into
mainfrom
feat/kotlin-migration-naming-pattern

Conversation

@hauke-d

@hauke-d hauke-d commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

Summary

  • pull-request-kotlin.yml accepts migration-naming-pattern and passes it to the check-migration-order action's naming-pattern, so callers can override the Flyway filename regex enforced on newly added migrations.
  • Its default is the action's regex. An empty value can't be used as the default, because a composite action receives '' instead of falling back to its own default, and the script requires a non-empty pattern.
  • Documented in docs/workflow-guide.md and CLAUDE.md.

Why

Repos whose migration filenames don't follow the default V<yyyy>.<mm>.<dd>.<hh>.<mm>__*.sql shape had no way to adjust the check through the shared workflow.

Test plan

  • Caller that doesn't set the input: Check Migration Order behaves as before
  • Caller that sets migration-naming-pattern: a new migration is validated against the custom pattern

@hauke-d
hauke-d marked this pull request as ready for review October 1, 2026 13:22
@hauke-d
hauke-d requested a review from a team as a code owner October 1, 2026 13:22
@hauke-d
hauke-d requested review from mtib and prasad-manu and removed request for a team October 1, 2026 13:22
@hauke-d
hauke-d merged commit 8e7857b into main Oct 2, 2026
1 check passed
@hauke-d
hauke-d deleted the feat/kotlin-migration-naming-pattern branch October 2, 2026 11:48
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.

2 participants