Why this matters: Open source contributions are public, permanent, and reviewed by developers across the world. A well-written issue gets fixed faster. A clear PR gets merged. And professional communication in a popular repo builds your reputation as a developer — especially if English is not your first language.

Useful language for open source

Reporting issues

  • "Steps to reproduce: 1. Navigate to… 2. Click…"
  • "Expected behaviour: The form should submit."
  • "Actual behaviour: A 500 error is returned."
  • "Environment: Node 20.5, macOS 14.3, Chrome 124."

Submitting PRs

  • "This PR fixes #123 by adding input validation."
  • "Changes: updated the API handler to reject null values."
  • "Testing: added unit tests for the edge cases mentioned in the issue."
  • "Breaking change: the `options` param is now required."

Responding to feedback

  • "Done — refactored as suggested."
  • "Could you clarify what you mean by X?"
  • "I see your point — I've updated the implementation."
  • "Thanks for the review! All comments addressed."