Skip to content

Instantly share code, notes, and snippets.

@eprislac
Last active January 24, 2019 00:11
Show Gist options
  • Save eprislac/44f5ccdc80bd2317de6f658ad6a10de9 to your computer and use it in GitHub Desktop.
Save eprislac/44f5ccdc80bd2317de6f658ad6a10de9 to your computer and use it in GitHub Desktop.
pull_request_template.md

RELATED STORY

<story_type_all_caps(BUG | FEATURE | CHORE)> - <story_title>
[#<story_number>]

DESCRIPTION

Add description here - should describe the problem

STEPS TO REPRODUCE ISSUE

Only if this PR is to address a bug, should be an ordered (numbered) list

CHANGELIST

Changes you made - should be an unordered list, not too deep on details

RESEARCH AND RESOURCES

This should be refs to patterns and libraries utilized, to books referenced, links to blog posts, stack overflow articles, etc..., so knowlege can be shared amongst everyone in the development team, and perhaps more importantly, so that we can document concrete reasons for changes made.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment