issue 1

[bgreiner]

This is an issue.

Some code.

[bgreiner]

#3

[kabalin]

Ben, a couple of other interesting hacks here:

• if you can create a milestone (e.g. named after upcoming release) and labels to categorise and order issues, you can then use closed milestones to see which issues have been fixed in the given release.
• if you write "fixes Test bugfixes2 #2" in the commit message that you push to repo, it will mark corresponding issue on tracker as "closed".
• you can refer to other commits here, just paste some symbols from the beginning of individual commit hash, e.g. c4a4db6

There are more ideas, if you have not found this page already: https://guides.github.com/features/issues/ or for more in-depth guide see https://help.github.com/categories/managing-your-work-on-github/