Pull Request Naming and Description Convention

#PR Naming

#<story-id> story description

Example

#869522144 Build HQ for meetings

#PR Description Template (Markdown)

The description should contain the following headings and the related content:

#### What does this PR do?
#### Description of Task to be completed?
#### How should this be manually tested?
#### Any background context you want to provide?
#### What are the relevant pivotal tracker stories?
#### Screenshots (if appropriate)
#### Questions: