Jump to Content
Reviewpad
Product GuideChangelogDiscussionsCommunity DiscordBlogGitHub
Log InReviewpad
Log In
Product GuideChangelogDiscussionsCommunity DiscordBlogGitHub

Getting Started

  • Welcome to Reviewpad!
  • First Revy Action: PR Size Label

Use Cases

  • Ship/Show/Ask
  • Automated Labelling
    • Label based on file paths
    • Label based on author groups
    • Label potential missing changes
    • Label critical changes with code queries
    • Label critical changes with semantic code annotations
    • Remove label based on file paths
  • Reviewer Assignment
    • Assign senior reviewers to new joiners
    • Assign review to 3 developers
    • Assign review to a team
  • Auto-merge

Revy File Specification

  • Introduction to Revy
  • Revy Syntax
  • Revy Semantics
  • Aladino Specification
    • Aladino Syntax
    • Aladino Semantics
    • Aladino Built-ins

Installation

  • GitHub Action
  • GitHub Action with a GitHub Token

Tooling

  • VSCode Revy YAML Schema

Product Development

  • Security Information

Contact Us

  • Community Discord

Company

  • About Us
  • Blog
  • Join Our Team
  • Code Review Interface
  • Press Kit

Legal

  • Terms and Conditions
  • Privacy Policy
  • Legal Information
Powered by 

Automated Labelling

Suggest Edits

Pull Requests labels are widely used by software developers to communicate certain required actions.

Out of the box, Reviewpad supports the action of adding labels to pull requests.

Together with the other built-in capabilities, you can automate flexible PR labeling workflows.

Updated about 2 months ago


What’s Next

Check out specific use cases for automated labelling:

  • Label based on file paths
  • Label based on author groups
  • Label potential missing changes
  • Label critical changes with code queries
  • Label critical changes with semantic code annotations
  • Remove label based on file paths
Did this page help you?