Alternative Plugins

Similar functionality is provided by the following plugins:

• find-owners plugin
• owners plugin

find-owners plugin (deprecated)

Status: deprecated, from Gerrit 3.4 on the code-owners plugin should be used instead
Repository: plugins/find-owners
Documentation: about, syntax, REST API, config

Functionality

• Basic support for defining code owners:
  • Code owners can be specified in OWNERS files that can appear in any directory in the source branch.
  • Code owners can be specified by email.
  • Inheritance from parent directories is supported and can be disabled.
  • Including an OWNERS file from another directory in the same project or from another project on the same host is possible (same branch is assumed).
  • File globs can be used.
  • See documentation for the supported syntax.
    
    
• Prolog rule to prevent submitting changes without owner approvals.
  • A change can be exempted from owners approval by setting a footer in the commit message.
    
    
• Basic UI:
  • Supports to discover users that can grant owner approval on a change (weighed suggestion) and add them as reviewer to the change.
  • Missing owner approvals are visualized on a change.
  • Owner approval is granted by voting on the Code-Review label.
    
    
• REST endpoints:
  • Action REST endpoint:
    • GET /changes/<change-id>/revisions/<revision-id>/find-owners
    • returns a RestResult which contains:
      • a file to list of owners map
      • a list of owner infos with weight infos
      • fields for debugging
      • fields for change, patch set, current reviewers and changed files
  • GetOwners REST endpoint:
    • GET /changes/<change-id>/owners
    • Delegates to Action REST endpoint (see above)
  • Also see REST endpoint documentation

---

Back to @PLUGIN@ documentation index

Part of Gerrit Code Review