References

---

• Freira, M., Caetano, J., Oliveira, J., & Marques-Neto, H. (2018). Analyzing The Impact Of Feedback In GitHub On The Software Developer’s Mood. In 2018 International Conference on Software Engineering & Knowledge Engineering.
• Garner, R. (2022, March 30). What Is a Pull Request & Why Is It Important for Code Review? LinearB. https://linearb.io/blog/what-is-a-pull-request/
• Hombergs, T. (2017, January 2). Github’s Fork & Pull Workflow for Git Beginners. https://reflectoring.io/github-fork-and-pull/
• Martin, R. C. (2003). Agile software development: principles, patterns, and practices. Prentice Hall PTR.
• Morina, F. (2022, December 1). Benefits of Using Pull Requests for Collaboration and Code Review. NVIDIA Technical Blog. https://developer.nvidia.com/blog/benefits-of-using-pull-requests-for-collaboration-and-code-review/
• Urna, H. (2020, May 19). Pull Request Workflow with Git. Medium. https://medium.com/@urna.hybesis/pull-request-workflow-with-git-6-steps-guide-3858e30b5fa4

Writing and Reviewing PRs

---

• Reviewing changes in pull requests (GitHub Docs)
• Creating a pull request template for your repository (GitHub Docs)
• Conventional Comments — a style for clear, kind review feedback

GenAI for Pull Requests

---

• General-purpose assistants (e.g., ChatGPT, Claude) can draft a PR description from a diff, generate a PR template, summarize a large changeset, and do a first-pass review. They miss project intent and can be confidently wrong — verify the output, and the human owns the merge decision. For research code, check data/IP policy before sharing a private diff.