Issues are typically used to track bugs or features, however Issues can be used for just about any task you want to track.
Okay, so now we have a repository on GitHub. 0:00 As we talked about briefly in the first stage, 0:03 issues are typically used to track bugs or 0:05 features, but really, issues can be used for just about any task you want to track. 0:07 It could be your to-do list or a list of goals you want to accomplish. 0:12 The issue remains open while it's yet to be complete, and 0:16 then you can close the issue once it's been taken care of. 0:18 Let's open some issues in our repo. 0:21 We'll navigate to the Issues tab from the main view, and 0:24 we'll click on the New Issue button. 0:27 There are a couple things we might want to do and track. 0:30 We could use a README with more information in it so 0:33 people know what the repo is about. 0:35 I'll create this issue to add a README file. 0:38 This'll be our title, and in the description we can add more context. 0:46 And you'll click Submit New Issue. 1:00 If you have additional comments you can add them below the main issue body. 1:04 Back in the issues tab, we now have one issue open. 1:08 We could also open another issue to track the courses in our 1:12 Treehouse learning track. 1:15 I'm on the python learning track so I'll add an issue, 1:16 Python Track Courses to be Completed. 1:19 In the body of the issue, we'll use Markdown to style the text. 1:29 Markdown is a syntax GitHub uses to add text formatting to issues, 1:33 pull requests, and files with the .md or .markdown extension. 1:37 We'll talk about markdown and finish this issue in the next video. 1:42
You need to sign up for Treehouse in order to download course files.Sign up