During collaboration in the workflow, which activity is typical?

During collaboration in the workflow, which activity is typical?

• A. Ignore feedback from reviewers
• B. Close the pull request without review
• C. Discuss and review code with team members
• D. Delete the branch after commit

Answer: (C)

Collaboration in a development workflow hinges on open communication and feedback through code reviews. Discussing and reviewing code with team members is the typical activity because it surfaces issues early, ensures code quality and consistency, and spreads knowledge across the team before changes are merged. Ignoring feedback undermines collaboration, closing a pull request without review bypasses the essential review step, and deleting the branch after the commit isn’t a routine collaborative activity and can erase important context. Therefore, discussing and reviewing code with the team best reflects how collaboration usually works.

Collaboration in a development workflow hinges on open communication and feedback through code reviews. Discussing and reviewing code with team members is the typical activity because it surfaces issues early, ensures code quality and consistency, and spreads knowledge across the team before changes are merged. Ignoring feedback undermines collaboration, closing a pull request without review bypasses the essential review step, and deleting the branch after the commit isn’t a routine collaborative activity and can erase important context. Therefore, discussing and reviewing code with the team best reflects how collaboration usually works.