在代码评审及评论前更新Pull Request是否符合专业规范？

Absolutely—this is not just allowed, it’s strongly encouraged in professional code review workflows, and here’s why:

• Respect reviewers’ time: There’s no need to make a reviewer spend time pointing out trivial errors you’ve already caught and fixed. Updating the PR upfront keeps the review focused on meaningful feedback (like logic gaps, architectural choices, or readability improvements) instead of typos, missing semicolons, or minor variable name fixes.
• Maintain a clean baseline: Starting the review with the most accurate version of your work sets a better tone for the process. It shows you’re proactive about delivering quality code before asking others to invest their time.
• Small fixes = no need for fanfare: For 1-2 simple errors, you can just push your corrected commits directly to your feature branch. The PR will automatically sync with the latest changes, and since no one’s started reviewing yet, there’s no risk of confusing anyone. If you want to keep your commit history clean, you can even use git commit --amend (if the fix is for your last commit) or an interactive rebase to squash the correction into earlier commits—just make sure you force-push only if no one else is working on your branch (which is almost always the case for personal feature branches).

If you’d added larger changes that alter the original PR’s scope, it might be polite to leave a quick comment on the PR noting the update—but for tiny, obvious fixes? No need to overcomplicate it.

This approach is totally standard and viewed as a responsible practice by most engineering teams.

内容的提问来源于stack exchange，提问作者Kalpashree Bal