A method of breaking down all of your tasks into a single framework.
There are often many tasks to attend to in your life, and organizing them can be annoying. As such, I've decided to share my method of task management.
note: GitHub doesn't allow a forked repository to be private, so unless you want to tell everyone about your current task list, you need to create it yourself. Feel free to take this markdown README with you as a self-reminder of the structure or to tell others!
Begin by simply creating your own private repository! The key to this method
is using the projects feature. You can organize current tasks by using
this feature.
Break down big plans into simple pieces with projects. Three columns are used for managing the projects:
These are blocked, todo, and needs-research.
These are only in-progress issues.
These are completed, abandoned, and dropped.
Issues are broken up by labels as topics.
A lone issue that needs to be dealt with, unrelated to any big projects.
Use checkboxes to break down an issue in a project to small steps.
Issues that are a part of a project.
A non-concrete idea for something that needs to be done in the future.
With these labels, the issue status is kept track of.
These are issues that can be freely picked from to continue work on a project.
These are issues that need to be researched before deciding what to do with it.
These are issues which need progress from other issues in order to be worked on.
These are issues which are currently being worked on.
These are issues which have been fully completed in the project.
These are issues which have lost the spark for it.
These are issues which have been dropped due to becoming unnecessary
There's basically nothing in this repository though, what can I do with it? The short answer here is: whatever you want! Expand on the idea as much or as little as you need. Feel free to create PRs on this original repository to help others with ideas too!
If you begin to find that you want to keep track of some specific files as part of an ongoing task, then do this:
- create a branch in the repo
- add those files in a commit
- this could be as simple as a
documentsdirectory and adding it there - personal note: I recommend keeping the root directory clean here
- this could be as simple as a
- create a merge request into your own main branch
- mention the issue with
closes #[commit number] - merge the branch and now you have a link to where the file came from