Rules and learning

Rules

Rules are short, plain-English statements of how your team writes code. MergeHarbor applies the rules that match the files a pull request changes.

Create rules in three ways:

• In the console — Memory → Rules → New rule. Scope a rule to the organization or a repository, and optionally to path globs.
• In a pull request — comment @mergeharbor remember <rule>, or scope it with @mergeharbor remember for services/**, jobs/**: <rule>.
• From feedback — when engineers consistently react to similar comments with 👍 or 👎, MergeHarbor proposes a rule that captures the pattern, with the evidence.

Approval

Organization owners choose who may create rules from pull-request comments (everyone, administrators, or nobody) and whether new rules require approval. Rules learned from feedback always start as proposed and take effect only after an administrator approves them.

Knowledge base

Add design documents, conventions, and architecture notes under Memory → Knowledge base, for every repository or selected ones. The reviewer searches them when they are relevant to a change.

Cross-repository context

For services that depend on each other, link related repositories under Memory → Cross-repo context. The reviewer can then search code and symbols in those repositories while reviewing.

Feedback

Reactions on review comments are collected automatically on GitHub, GitLab, and Gitea. On Bitbucket, rate comments in the console. Comments similar to ones your team has rejected are suppressed in later reviews.