balls array.
Open the pull request that needs review. In this example the PR is awaiting review from Alice and Siddharth Barahalikar.

- Click the plus icon to the left of a line to open a small comment box tied to that specific line.
- To comment on multiple contiguous lines, click and drag to select them — the resulting comment will reference the selection.
- Comments can be standalone or grouped into a pending review. Starting a review collects comments until you submit them as a single review action.
“This block mutates
gameState.balls while iterating — that can cause exponential growth. Please avoid mutating the array while iterating and also ensure we cap the total number of balls.”
Review workflows and submission options
When you start a review, comments are added as pending on the PR. When submitting the review you choose one of three outcomes:
- Comment — general feedback that does not block merging
- Approve — indicates the PR is ready to merge
- Request changes — prevents merging until required changes are made
Avoid mutating an array while iterating over it (for example, pushing into the same array inside a
forEach). Instead, collect new items separately or push a known small number of items derived from an existing base element.
#1), GitHub will automatically close that linked issue on merge.



If your repository enforces branch protection or requires multiple approvals, make sure you understand those rules before merging. Deleting the source branch is optional—only delete it when you no longer need it for additional work.
Helpful links and references
- GitHub Pull Requests documentation — official docs for reviewing and merging
- GitHub Code review guides — tips for reviewers and authors
- Use the plus icon to comment on a single line; select multiple lines to create a multi-line comment that references a block of code.
- Start a review to collect multiple inline comments before submitting (you can Comment / Approve / Request changes).
- Avoid mutating arrays while iterating — instead, snapshot an element or collect new items separately and cap additions to prevent exponential growth.
- Push fixes to the same branch; the PR will update automatically so reviewers can re-check and approve before merging.