Skip to content

Instantly share code, notes, and snippets.

@michaelmiller2116
Last active October 22, 2019 19:22
Show Gist options
  • Save michaelmiller2116/c180b904d20fcc925a53809ff6a0b54c to your computer and use it in GitHub Desktop.
Save michaelmiller2116/c180b904d20fcc925a53809ff6a0b54c to your computer and use it in GitHub Desktop.
This md serves as a template for submitting PR's that includes checklists for testing, styles etc., a description of the PR, the fix, and HOW it was tested. Src: Phillip Johnston, August 4, 2017, https://embeddedartistry.com/blog/2017/8/4/a-github-pull-request-template-for-your-projects

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

Asana stories covered

Please add links to any and all Asana stories that this PR covers

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Test A
  • Test B

Test Configuration:

  • Firmware version:
  • Hardware:
  • Toolchain:
  • SDK:

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment