# github issues top level comments for tasks v0.0.1
note: In last 2 video we went over how we connect designs to our project management application. From here on we will show you how our version controlling process works on GitHub
----
![](https://i.imgur.com/hYruyCK.png)
note: In this video I will go over how the tasks and information are structure in the main top level comment.
----
![](https://i.imgur.com/fWeIwh4.png)
note: Then we will go over markdown. Which is a form of markup language.
----
![](https://i.imgur.com/YC0CBCN.png)
note: We start out our comment with a @todo tag, where we place all our task.
----
![](https://i.imgur.com/ZPY9Jyb.png)
note: Each issue must produce at least 1 @output.
----
![](https://i.imgur.com/hT4Twfg.png)
note: Each task or task groups created within this issue must also have at least 1 @output. There may be multiple outputs produced and used wihtin the issue but the last output(s) will be considered as the produced output of that issue.
----
![](https://i.imgur.com/urAJFkO.png)
note: The indentation of the task group is important. You must keep the @input & @output with the same hirerachy as the tasks listed within that group
----
![](https://i.imgur.com/qyM1Ou9.png)
note: Now let’s go through how to do these changes.
----
![](https://i.imgur.com/lecYdtx.png)
note: When writing a new comment you will see these two options. Write and Preview. In the write section you will write all your markdown text. Let’s start by creating a task
----
![](https://i.imgur.com/80govTS.png)
note: Simply write a minus with open and closed sqaure brackets, followed by the task name.
----
![](https://i.imgur.com/bbalPtR.png)
note: Now clicking on preview you will see a new task is created.
----
![](https://i.imgur.com/ZqR8Pdr.png)
note: The empty space between the square brackets means the task is open.
----
![](https://i.imgur.com/iGwvUZr.png)
note: Placing an X in between
----
![](https://i.imgur.com/dGEoFLY.png)
note: will mark the task as done.
----
![](https://i.imgur.com/eQSbN4X.png)
note: To create a subtask, simply go to the next line, write the task in the same manner but this time with 3 spaces infront of the minus sign.
----
![](https://i.imgur.com/N3JSZub.png)
note: This will indent your tasks as such.
----
![](https://i.imgur.com/24SQLJe.png)
note: To link something as @input. Write `@input` with backticks. Notice this time we didn't put brackets because this input is not a task
----
![](https://i.imgur.com/nIiRkat.png)
note: Then following that you write the emoji name within 2 colons, e.g. (:question: or :package:)
----
![](https://i.imgur.com/A6RWP3w.png)
note: After that you can link the file but placing the file name withing a sqaure bracket and backticks and placing that file link in normal/circle brackets right after. Remember there must not be any white space between the brackets. otherwise it will not work. Lastly, you can mention the link of the issue this input document is from.
----
![](https://i.imgur.com/mC6aJZM.png)
note: To mention the issue you can simply write the issue number starting with the hashtage then selecting that issue (e.g. #116)
----
![](https://i.imgur.com/DLrRDs3.png)
note: You can do the same for output (= `@output`) to make it appear as (= @output)
----
![](https://i.imgur.com/iWB2PbP.png)
note: Now toggle to preview to see the changes before you comment.
----
![](https://i.imgur.com/xFMoTA7.png)
note: As shown in the previous video. to edit a comment simply click on the three dots on the top right corner,
----
![](https://i.imgur.com/0jQxuTl.png)
note: then select edit. Now before we finish this video, there are few concept to understand.
----
![](https://i.imgur.com/cPJIlkj.png)
note: 1. Every github issue is also a task somewhere in the project
----
![](https://i.imgur.com/cPJIlkj.png)
note: 2. There is one root issue per project. (So all these task you are see in this issue are indirectly linked to the project’s main root issue.)
----
![](https://i.imgur.com/YEP0NqO.png)
note: 3. a task on issue1 can be a normal task with an output
----
![](https://i.imgur.com/2HWkbi3.png)![](https://i.imgur.com/Vim0OQH.png)
note: 4. a task on issue1 can be a sub-task in a task group with or without an output
----
![](https://i.imgur.com/Vim0OQH.png)
note: 5. a task on issue1 can be a link to another github issue2 in which case: it does not have output,
----
![](https://i.imgur.com/CM6z3hd.png)
note: because all outputs are listed in that issue2
----
![](https://i.imgur.com/6cciAF4.png)
note: an output of an issue can be listed/linked as input on another issue. if that is the case, that task in issue1 has to be listed before the output of issue2 is used as an input in another task in issue1.
----
What if there is a task with no output?
note: Lastly, if some work or tasks seem to be associated with no output, then this should be first discussed before proceeding.
----
Thank you
note: This will be all for this video. Thanks for watching
{"metaMigratedAt":"2023-06-17T14:41:55.339Z","metaMigratedFrom":"YAML","title":"github issues top level comments for tasks v0.0.1","breaks":true,"contributors":"[{\"id\":\"6e613247-7f39-4f32-b571-d0e5e788b14f\",\"add\":5508,\"del\":408}]"}