Pull request (PR)
Also: PR · pull request · 合併請求 · merge request
A formal request saying 'I have made these changes — please decide whether to take them in'. It is a human review process, not a command.
When you will meet it
In a real team an AI agent usually does not push code straight to the main line; it opens a PR and waits for you to review it. If you cannot read a PR page you never realise you hold a veto, and end up passively accepting whatever the agent hands over — and this is the main gatekeeping move of the agent era.
An analogy
Like returning an edited manuscript to the editor's desk with all changes marked: the editor sees exactly which lines you touched, can comment in the margin, ask for revisions, or reject it outright. Until it is accepted, not one word of the original moves.
Minimal example
# PR 主要在網站上看，但也可以用 GitHub CLI 在命令列處理：
gh pr list # 目前有哪些 PR 等著處理（要先 gh auth login）
gh pr create --fill # 用目前的分支和 commit 訊息開一個 PR
gh pr diff 123 # 看第 123 號 PR 逐行改了什麼A PR page has four areas to read: Files changed (the line-by-line diff), Checks (did the automated tests pass), Commits (how the work was split up) and Conversation (reviewer comments). Look at Checks before Files changed — if the automated tests already failed, reading the diff line by line is wasted effort.
What people get wrong
- Assuming a PR has already applied the changes to the main line. Nothing on the main line moves until it is merged; a PR is only a request.
- Fast-approving a PR because an AI opened it. Agents write very fluent commit messages and PR descriptions, and fluency has nothing whatsoever to do with correctness.