Pull requests and review

Branches pushed to a repository can be compared in a pull request. Pull requests can request reviewers, collect comments and reply threads on specific changed lines, and be approved, sent back with Request changes, discussed, closed, or merged when Git can merge the selected branches without conflicts.

Review threads can be resolved or reopened by repository writers and admins. Approvals apply to the current head commit; when a new commit is pushed, prior approvals are dismissed and must be renewed. Protected branches block merges while a review requests changes.

In-app notifications alert repository participants when they are assigned an issue, requested as a reviewer, mentioned with @email-prefix, or receive a reply or review decision.

CODEOWNERS

Pull requests read code ownership rules from the base branch, checking .github/CODEOWNERS, then CODEOWNERS, then docs/CODEOWNERS. The last matching rule determines the owners for each changed file.

Matching individual @owner entries to Finluth accounts uses the account email, email prefix, or display name, and only repository writers and admins can be requested. Newly matched owners are added as reviewers and notified; the pull request shows the source file, matched paths, and any unsupported or unresolved entries.

Team owners use @workspace/team-slug or @team-slug and request reviews from that team's repository writers. Glob patterns support *, **, and ?; negation and bracket character classes are skipped with a warning.