Files
playwright/.github/copilot-instructions.md

635 B

PR Review Guidelines

When reviewing pull requests:

  • Only comment on semantically meaningful issues: bugs, incorrect logic, security problems, or API contract violations.
  • Skip style, formatting, naming, and whitespace observations unless they cause functional problems.
  • Keep each comment short — one or two sentences maximum.
  • Do not write long descriptions or summaries of what the code does.
  • Do not suggest refactors or improvements unrelated to the PR's stated goal.
  • NEVER produce a review body or top-level PR overview comment. The review body MUST be empty. Put findings only in inline comments on specific lines.