2016-03-05 20:49:05 +00:00
|
|
|
### Purpose
|
|
|
|
|
|
|
|
|
|
Describe the purpose of this change. If there is an existing issue that is
|
|
|
|
|
resolved by this pull request, ensure that the commit subject is on the form
|
|
|
|
|
`Some short description (fixes #1234)` where 1234 is the issue number.
|
|
|
|
|
|
|
|
|
|
### Testing
|
|
|
|
|
|
|
|
|
|
Describe what testing has been done, and how the reviewer can test the change
|
|
|
|
|
if new tests are not included.
|
|
|
|
|
|
|
|
|
|
### Screenshots
|
|
|
|
|
|
|
|
|
|
If this is a GUI change, include screenshots of the change. If not, please
|
|
|
|
|
feel free to just delete this section.
|
2016-03-11 08:36:06 +00:00
|
|
|
|
|
|
|
|
### Authorship
|
|
|
|
|
|
|
|
|
|
Every author of a code contribution (Go, Javascript, HTML, CSS etc, with the
|
|
|
|
|
possible exception of minor typo corrections and similar) is recorded in the
|
|
|
|
|
AUTHORS and NICKS files and the in-GUI credits. If this is your first
|
|
|
|
|
contribution, a maintainer will add you properly before accepting the
|
|
|
|
|
contribution. You need not do so yourself or worry about the fact that the
|
|
|
|
|
"authors" automated test fails. However, if your name (such as you want it
|
|
|
|
|
presented in the credits) is not visible on your Github profile or in your
|
|
|
|
|
commit messages, please assist by providing it here.
|
