fix(ci): store regex in variables to fix notify-parent parse error

[mateodelnorte]

Summary

• Stores regex patterns in bash variables before using them in [[ =~ ]] tests
• Fixes bash parse error: ( in [:(] character class was interpreted as unmatched subshell opener
• Error: unexpected EOF while looking for matching ')' (exit code 2)
• Broken since cascading notification support was added

Root cause

# Broken — bash parses ( as subshell opener before regex engine sees it
if [[ "$MSG" =~ ^feat[:(] ]]; then ...

# Fixed — variable content passes directly to regex engine
re_feat='^feat[:(]'
if [[ "$MSG" =~ $re_feat ]]; then ...

Context

• Part of [[tasks/meta-64]] / [[incidents/notify-parent-broken]]
• Same fix applied to all 5 affected child repos

Test plan

• Workflow passes on next push to main after merge

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Improved CI workflow event detection and exposed key event metadata to downstream steps.
  • Unified how workflow outputs are produced and written, ensuring consistent output delivery across trigger types.
  • Streamlined commit-type detection using consolidated pattern matching for more reliable classification.

Note: No user-facing changes in this release.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

Walkthrough

Reworks .github/workflows/notify-parent.yml to expose event/payload via environment variables, add a reusable write_output helper that writes to $GITHUB_OUTPUT, normalize outputs for repository_dispatch and other events, switch event branching to compare EVENT_NAME, and replace inline type-detection with predeclared regex variables.

Changes

Cohort / File(s)

Summary

Notify workflow .github/workflows/notify-parent.yml

Adds environment variables exposing event and payload, introduces write_output helper to append key/value pairs to $GITHUB_OUTPUT, emits outputs for repository_dispatch and non-dispatch flows via that helper, replaces direct event checks with EVENT_NAME and replaces inline type-detection with named regex variables (re_feat, re_fix, re_chore, re_docs, re_test, re_refactor) mapping matches to type (defaults to other).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• ci: add cascading notification support #15 — Modifies the same .github/workflows/notify-parent.yml area, updating repository_dispatch handling and the same output fields.

Poem

🐇
I nudged the envs and fetched the payload light,
I stitched outputs tidy in the GitHub night.
Regex paws tapped, labels found their home,
write_output thumps — a neat little poem. ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly addresses the main change: storing regex patterns in variables to fix a bash parse error in the notify-parent workflow.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/notify-parent-regex

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[greptile-apps]

Greptile Summary

Fixes a bash parse error in the notify-parent workflow by storing regex patterns in variables before using them in [[ =~ ]] tests.

• The character class [:(] was causing bash to interpret ( as an unmatched subshell opener before the regex engine could process it
• Storing patterns in variables (e.g., re_feat='^feat[:(]') prevents premature parsing and passes the pattern directly to the regex engine
• All 6 commit type patterns (feat, fix, chore, docs, test, refactor) have been updated consistently
• This restores cascading notification functionality that was broken since the feature was added

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The fix is straightforward and well-understood: storing regex patterns in variables is a standard bash best practice for avoiding parse errors. The regex patterns remain functionally identical, and testing confirms they match both colon and parenthesis variants correctly. No logic changes, only syntax improvements.
• No files require special attention

Important Files Changed

Filename	Overview
.github/workflows/notify-parent.yml	Stores regex patterns in bash variables to prevent parse error in [[ =~ ]] tests, fixing cascading notification workflow

_{Last reviewed commit: e87511d}