Skip to content

Conversation

@haberbyte
Copy link
Contributor

Description

Develop what, but also why this PR exists. The "Why" is as much, if not more important than the "What". I use this approach very often when I write commit messages, because if the code is clear enough it should already answer the "what" question. The "why" is often more subtle.

Tasks

  • Write tests

Implementation notes

I don't always use this section, but I do when I find there's something particularly tricky end/or nifty in the code.

References

Support ticket
Jira story
Invision design

Screenshots (if needed)

Screenshot 1
Screenshot 2

Risks

  • [HIGH | medium | low] Does it work across browsers (including IE!)?
  • [HIGH | medium | low] Does it work in the different products (Support, Chat, Connect)?
  • [HIGH | medium | low] Are there any performance implications?
  • [HIGH | medium | low] Any security risks?
  • [HIGH | medium | low] What features does this touch?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants