Skip to content

Latest commit

 

History

History
24 lines (21 loc) · 1.48 KB

PULL_REQUEST_TEMPLATE.md

File metadata and controls

24 lines (21 loc) · 1.48 KB

Any of the checked boxes below indicate that I took action:

For all non-trivial changes that modify the behavior or public API:

  • Before submitting a pull request, I started a discussion on the Gradle developer list or can reference a JIRA issue.
  • I wrote a design document. A design document can be brief but explains the use case or problem you are trying to solve, touches on the planned implementation approach as well as the test cases that verify the behavior. Optimally, design documents should be submitted as a separate pull request. Samples can be found in the Gradle GitHub repository. Please let us know if you need help with creating the design document. We are happy to help!
  • The pull request contains an appropriate level of unit and integration test coverage to verify the behavior. Before submitting the pull request I ran a build on your local machine via the command ./gradlew quickCheck <impacted-subproject>:check.
  • The pull request updates the Gradle documentation like user guide, DSL reference and Javadocs where applicable.