Apply team conventions to branches, commits and pull requests

With Pro or Pro AI, a team can keep its conventions in a template set in Maestro. Someone with the appropriate access configures the set and activates it for the organization. Sign in and sync Riff to use the active set on your computer.

Try a convention on a real change

1. Create a branch for a checkout fix. A rule such as ^fix/[a-z0-9-]+$ accepts fix/empty-cart. Riff evaluates the name while you type and shows the team's example or pattern when it does not match.
2. In the commit panel, select a template such as fix({area}): {summary}. Enter checkout for the area and handle empty carts for the summary. Insert the result and review the text in the composer. The first line becomes the subject and subsequent lines become the body.
3. When opening a pull request, select a PR template, fill in its variables and apply it. Review the resulting title and description, check the source and target branches, then create the request.

Understand what the validation controls

Suggestion and Warning display feedback and let you proceed. Blocking prevents creating a branch whose name fails an applicable blocking rule. For a commit template it prevents inserting the template with missing required fields. For a PR template it prevents applying that template until its required fields are complete. The resulting text remains editable. Invalid branch expressions are ignored by validation.

For commit authorship, signed-in users can use their Gapfy name and email. An organization can require that identity. Where personal choice is allowed, check the identity preference before committing. To measure how existing commit titles match the organization's active message pattern, run a compliance check.