Issues on GitHub are un-ordered. That is; While they do have numbers these are merely unique identifiers and not necessarily something that you should put too much meaning into. The issue numbers tell you something about the sequence the issues were created in - but nothing about the sequence you should implement them in.
Think of the issues as your backlog; a gross list of all kinds of stuff that may come from any source and that may - or may not - be important or even relevant.
You will bring order to your backlog in just a while - a process often referred to as grooming the backlog. 95% of all projects works by some kind of agile methodology. If you do too, then you would probably need a Kanban board or Scrum board to plan your work.
For that you need a GitHub Project.
Open a browser for this repo on GitHub. gh offers you a nifty shortcut to achieve that - run
gh browse
A note on gh browse
---
`gh browse` even takes a few _flags_ or _options_ that can take you directly to a specific part of the website for yout repository or organisation.
Study the manual for [gh browse](https://cli.github.com/manual/gh_browse)
---
Go to the Projects tab and create and link a new project (Link a project is default - but for this exercise you should choose to create a New project):
This will be like a personal ToDo list. Pick a good name for your board - and select the board view as your initial layout.
You can toggle the add issue bar by hitting <ctrl>+<space> and then click on + to get access to the Add item from repository menu.
[ ] Bring all issues from your repository into the ToDo list
Read through all the issues
You can rearrange the order of the issues in a column (sometimes referred to as a swimlane) through drag'n'drop.
Start by dragging this issue that your are working on "README FIRST" to the "In progress" column.
Carefully read through all the issues - to prepare yourself for what's going to happen and to make sure that you have all necessary information. Some of the issues may be blockers to others or impose a natural order or priority.
[ ] Organize the issues in Kanban style - that means that the priority and order of the issues is simply determined by reading them top-down; The next issue is always the top-most issue in the ToDo column. Sweet and simple!
When you are done - close this issue and continue working from your new Kanban board.
DID YOU NOTICE - that when you closed this issue it was automatically moved from the "In progress" to the "Done" Column!
Now work the issues in the order you organized them in your project - Start by dragging them to "In progress" and close each issue when it's done.
Bring all repository issues into a new project
Issues on GitHub are un-ordered. That is; While they do have numbers these are merely unique identifiers and not necessarily something that you should put too much meaning into. The issue numbers tell you something about the sequence the issues were created in - but nothing about the sequence you should implement them in.
Think of the issues as your backlog; a gross list of all kinds of stuff that may come from any source and that may - or may not - be important or even relevant.
You will bring order to your backlog in just a while - a process often referred to as grooming the backlog. 95% of all projects works by some kind of agile methodology. If you do too, then you would probably need a Kanban board or Scrum board to plan your work.
For that you need a GitHub Project.
Open a browser for this repo on GitHub.
ghoffers you a nifty shortcut to achieve that - runA note on
--- `gh browse` even takes a few _flags_ or _options_ that can take you directly to a specific part of the website for yout repository or organisation. Study the manual for [gh browse](https://cli.github.com/manual/gh_browse) ---gh browseGo to the Projects tab and create and link a new project (Link a project is default - but for this exercise you should choose to create a New project):
You will be offered a link to study "Planning and tracking with Projects" - or you can jump right in.
This will be like a personal ToDo list. Pick a good name for your board - and select the board view as your initial layout.
You can toggle the add issue bar by hitting
<ctrl>+<space>and then click on+to get access to the Add item from repository menu.[ ] Bring all issues from your repository into the ToDo list
Read through all the issues
You can rearrange the order of the issues in a column (sometimes referred to as a swimlane) through drag'n'drop.
Start by dragging this issue that your are working on "README FIRST" to the "In progress" column.
Carefully read through all the issues - to prepare yourself for what's going to happen and to make sure that you have all necessary information. Some of the issues may be blockers to others or impose a natural order or priority.
[ ] Organize the issues in Kanban style - that means that the priority and order of the issues is simply determined by reading them top-down; The next issue is always the top-most issue in the ToDo column. Sweet and simple!
When you are done - close this issue and continue working from your new Kanban board.
DID YOU NOTICE - that when you closed this issue it was automatically moved from the "In progress" to the "Done" Column!
Now work the issues in the order you organized them in your project - Start by dragging them to "In progress" and close each issue when it's done.
Minimize WIP!