Skip to content

Instantly share code, notes, and snippets.

@hcopperm
hcopperm / gist:e2eba762b43132852ecc
Last active August 29, 2015 14:06
pull-request-template.md
**{TICKET}: Short Description**
## Status
**READY/IN DEVELOPMENT/HOLD**
## Description
A few sentences describing the overall goals of the pull request's commits.
{TICKET}: Short description
## Status
**READY/IN DEVELOPMENT/HOLD**
## Migrations
YES | NO
## Description
A few sentences describing the overall goals of the pull request's commits.

Status

READY/IN DEVELOPMENT/HOLD

Migrations

YES | NO

Description

A few sentences describing the overall goals of the pull request's commits.

Related PRs

Fix #{issue number}

Status

READY/IN DEVELOPMENT/ON HOLD

Description

A few sentences describing the purpose of this pull request

Steps to test

Describe how to test any UI or API changes that might not be covered by your automated tests.

{
"trips": [
{
"actual_ends_at": null,
"actual_fare": null,
"actual_net_fare": null,
"actual_starts_at": null,
"carpool": false,
"coupon_redemption": null,
"id": 16092,
Fix #{issue number}
## Title
One line description of your change (this will go in the release notes email)
## Status
**READY/IN DEVELOPMENT/ON HOLD**
## Description
A few sentences describing the purpose of this pull request
Bracket Line Up
What Rubocop wants:
```
render({
json: @property_transaction,
scope: {
user: current_user,
property_transaction: @property_transaction,
}
})

{Link to JIRA ticket}

Description

A few sentences describing the overall goals of the pull request's commits. Make sure to include enough context for a reviewer who might not have much background.

Testing description

Include a description of what you've done to test the PR. For example, did you deploy it to staging and test against real data?

Visual design

If this is a design-related ticket, include screenshots of your changes