Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

issue 1 #4

Open
bgreiner opened this issue Dec 2, 2016 · 2 comments
Open

issue 1 #4

bgreiner opened this issue Dec 2, 2016 · 2 comments

Comments

@bgreiner
Copy link
Member

bgreiner commented Dec 2, 2016

This is an issue.

Some code.
bgreiner referenced this issue Dec 2, 2016
@bgreiner
lets commit this
365f8e0 
kljjjlkjkljl
@bgreiner
Copy link
Member Author

bgreiner commented Dec 2, 2016

#3

@kabalin
Copy link
Member

kabalin commented Dec 2, 2016 •
edited
Loading

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/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kabalin @bgreiner