Add Watchflow governance rules (3 rules, 1 high-priority)

[dkargatzis]

Adds Watchflow rule recommendations based on repository analysis.

Need to update rules later? Analyze your repository again to get updated recommendations.

Summary by CodeRabbit

• Chores
  • Updated pull request workflow rules with three new quality gate enforcements: mandatory issue linking to ensure better traceability between pull requests and tracked issues, required CI workflow execution to verify code quality before merging, and conventional commit title pattern validation to maintain consistency in commit messages across the project.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

The .watchflow/rules.yaml file has been refactored to replace a block of PR-related rules with three new top-level rule definitions: require_linked_issue, required_workflows, and title_pattern. Each new rule includes descriptions, severities, and categories, shifting from per-rule evaluation conditions to explicit quality gates and traceability requirements.

Changes

Cohort / File(s)	Summary
Workflow Rule Configuration \.watchflow/rules.yaml	Replaced PR-related rules (descriptive title, minimum contributors, test presence, code-owner review, push restrictions) with three new top-level rules: issue linking enforcement, CI workflow requirements, and conventional commit title pattern enforcement.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 Hops with glee through rules renewed,
Issue links and workflows brew,
Titles now in patterns true,
Quality gates shine crystal blue!
✨

🚥 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 'Add Watchflow governance rules (3 rules, 1 high-priority)' clearly and specifically describes the main change: adding three new governance rules to the .watchflow/rules.yaml file, with one marked as high-priority.
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 watchflow/rules

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @.watchflow/rules.yaml:
- Around line 18-25: The rule entry with key/title_pattern is missing the
required parameters map; add a parameters: section under the same rule and
define title_pattern as a regex string that enforces Conventional Commit titles
(e.g., allowing scopes and a description), ensuring you update the existing
block that contains key: title_pattern, name: Enforce Conventional Commit
Titles, description, severity, category, and reasoning to include parameters:
title_pattern with the regex pattern shown in the review.

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f5a3be1 and 28302ec.

📒 Files selected for processing (1)

• .watchflow/rules.yaml

🔇 Additional comments (2)

.watchflow/rules.yaml (2)

2-9: LGTM!

The require_linked_issue rule is well-structured with clear description and reasoning. The high severity appropriately reflects the significant unlinked issue rate mentioned.

---

10-17: The rule configuration is correct as-is. Watchflow uses a simplified schema where rules are defined generically (key, name, description, severity, category, reasoning) without rule-specific configuration fields. The required_workflows rule follows the same pattern as the other two rules in the file (require_linked_issue and title_pattern), and the description clearly indicates the intent: "Ensure all PRs pass CI workflows before merging."

Likely an incorrect or invalid review comment.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

Watchflow title_pattern rule pattern field required documentation

💡 Result:

In Watchflow, title_pattern is a rule parameter (a string) used to enforce a pull request title format via a regular expression in your repository’s .watchflow/rules.yaml file. Example: parameters.title_pattern: "^[A-Z]+-[0-9]+: .+". [1]

It’s not a standalone “pattern” field at the top level—Watchflow rules are defined under rules: and commonly include fields like description, severity, event_types, and a parameters: map where rule-specific inputs (like title_pattern) live. [2]

If you’re using a “PR title must match …” rule, then title_pattern is effectively required for that rule to work, because it defines what the title must match. [1]

Sources: [1] [2]

---

Add parameters: section with regex pattern to enforce Conventional Commit titles.

The rule lacks the required title_pattern parameter. In Watchflow, title_pattern must be defined within a parameters: map as a regex string. Without it, the rule cannot validate PR titles. Update the rule to:

- key: title_pattern
  name: Enforce Conventional Commit Titles
  description: Require PR titles to follow Conventional Commit patterns (feat:, fix:,
    etc.) for better changelog generation and clarity.
  severity: medium
  category: quality
  reasoning: No explicit mention of commit message standards; enforcing title patterns
    improves commit hygiene and project governance.
  parameters:
    title_pattern: "^(feat|fix|docs|style|refactor|perf|test|build|ci|chore|revert)(\\(.+\\))?: .+"

🤖 Prompt for AI Agents

In @.watchflow/rules.yaml around lines 18 - 25, The rule entry with
key/title_pattern is missing the required parameters map; add a parameters:
section under the same rule and define title_pattern as a regex string that
enforces Conventional Commit titles (e.g., allowing scopes and a description),
ensuring you update the existing block that contains key: title_pattern, name:
Enforce Conventional Commit Titles, description, severity, category, and
reasoning to include parameters: title_pattern with the regex pattern shown in
the review.