Skip to content

fix: address all PR review comments on config-driven rules engine#11

Closed
Copilot wants to merge 1 commit intoconfig-driven-rules-enginefrom
copilot/sub-pr-9-again
Closed

fix: address all PR review comments on config-driven rules engine#11
Copilot wants to merge 1 commit intoconfig-driven-rules-enginefrom
copilot/sub-pr-9-again

Conversation

Copy link

Copilot AI commented Mar 18, 2026

Five issues flagged in code review on the config-driven rules engine refactor.

Changes

CI / Workflow

  • Add apk add --no-cache make step before make calls — Alpine images ship without make

Makefile

  • :Z SELinux relabel option is now conditional on Podman being the detected engine; Docker uses a plain bind-mount

modules/ukko.jsmailing_list handler

  • Domain validation moved from email.includes('.') to fqdn.includes('.') (domain portion only), preventing undefined sublabels for addresses with dots in the local-part (e.g. user.name@localhost)

test/ukko.test.js

  • endswith test was a no-op (no endswith rules exist in config); now pushes a temporary rule in try/finally to exercise the code path deterministically
  • Fallback suppression test was conditional on finding a From-header fallback rule (none exists); replaced with a hard assertion: GitHub From + List-Id present → github label assigned, lists/* absent

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

Copilot AI changed the title [WIP] Refactor config-driven rules engine fix: address all PR review comments on config-driven rules engine Mar 18, 2026
Copilot AI requested a review from T0MASD March 18, 2026 11:52
@T0MASD T0MASD marked this pull request as ready for review March 18, 2026 11:57
@T0MASD T0MASD closed this Mar 18, 2026
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