|
1 | 1 | # CLI Task Tracker |
2 | 2 |
|
3 | | -CLI Task Tracker is a simple yet powerful command-line application designed to help you manage your tasks directly from your terminal. Built entirely in Python, the project uses only built-in modules (`json`, `sys`, and `datetime`), ensuring a lightweight solution with no external dependencies. |
| 3 | +CLI Task Tracker is a simple yet powerful command-line application designed to help you manage your tasks directly |
| 4 | +from your terminal. Built entirely in Python, the project uses only built-in modules (`json`, `sys`, and `datetime`), |
| 5 | +ensuring a lightweight solution with no external dependencies. |
4 | 6 |
|
5 | 7 | ## Table of Contents |
6 | 8 | - [Overview](#overview) |
@@ -36,11 +38,67 @@ No additional packages are required since only built-in modules are used. |
36 | 38 | ### Steps to Install |
37 | 39 | 1. **Clone the Repository:** |
38 | 40 | ``` bash |
39 | | - git clone https://github.com/yourusername/cli-task-tracker.git |
| 41 | + git clone https://github.com/MXD-K1/cli-task-tracker.git |
40 | 42 | cd cli-task-tracker |
41 | 43 | ``` |
| 44 | +2. **Run it on your terminal:** |
| 45 | + ``` bash |
| 46 | + python task-tarcker-cli.py # your commands go here |
| 47 | + ``` |
| 48 | + |
42 | 49 | ## Usage |
43 | | -none |
| 50 | +Here is a list of the available commands: |
| 51 | + 1. **Adding a Task:** |
| 52 | + - To add a new task, simply use: |
| 53 | + ``` bash |
| 54 | + python cli_task_tracker.py add "Buy groceries" |
| 55 | + ``` |
| 56 | + Output: `Successfully added Buy groceries (ID: 3)` |
| 57 | + |
| 58 | + - To add a description to an existing task: |
| 59 | + ``` bash |
| 60 | + python cli_task_tracker.py add 3 -d "Buy groceries and cook diner" |
| 61 | + ``` |
| 62 | + |
| 63 | + - To add a description to a new task: |
| 64 | + ``` bash |
| 65 | + python cli_task_tracker.py add "Buy groceries" -d "Buy groceries and cook diner |
| 66 | + ``` |
| 67 | + |
| 68 | + 2. **Updating a Task:** |
| 69 | + - To add a new task, simply use: |
| 70 | + ``` bash |
| 71 | + python cli_task_tracker.py update 1 "Buy groceries and cook diner" |
| 72 | + ``` |
| 73 | + |
| 74 | + 3. **Deleting a Task:** |
| 75 | + |
| 76 | + Remove a task using its ID: |
| 77 | + ``` bash |
| 78 | + python cli_task_tracker.py delete 1 |
| 79 | + ``` |
| 80 | + 4. **Listing Tasks:** |
| 81 | + - View all tasks: |
| 82 | + ``` bash |
| 83 | + python cli_task_tracker.py list |
| 84 | + ``` |
| 85 | + - Filter tasks by status: |
| 86 | + ``` bash |
| 87 | + python cli_task_tracker.py list todo |
| 88 | + python cli_task_tracker.py list in-progress |
| 89 | + python cli_task_tracker.py list done |
| 90 | + ``` |
| 91 | + 5. **Marking Tasks (Changing Task Status):** |
| 92 | + - Mark a task as in-progress: |
| 93 | + ``` bash |
| 94 | + python cli_task_tracker.py mark-in-progress 1 |
| 95 | + ``` |
| 96 | + - Mark a task as either `todo`, `in-progress`, or `done`: |
| 97 | + ``` bash |
| 98 | + python cli_task_tracker.py mark 1 done |
| 99 | + python cli_task_tracker.py mark 1 todo |
| 100 | + python cli_task_tracker.py mark 1 in-progress |
| 101 | + ``` |
44 | 102 |
|
45 | 103 | ## Task Data Structure |
46 | 104 | Each task is stored in a JSON file with the following properties: |
@@ -79,31 +137,30 @@ Thank you for considering contributing to **CLI Task Tracker**! Your contributio |
79 | 137 | ``` bash |
80 | 138 | git checkout -b feature/your-feature-name |
81 | 139 | ``` |
82 | | - |
83 | | - When making your changes: |
| 140 | +4. **Make Your Changes:** |
84 | 141 | - Ensure your code follows the project’s style. |
85 | 142 | - Write clear, concise commit messages. |
86 | 143 | - Update documentation **if** needed. |
87 | 144 |
|
88 | | -4. **Commit Your Changes**: |
89 | | - |
90 | | -``` bash |
91 | | -git commit -am "Add [feature/bug fix]: Brief description of changes" |
92 | | -``` |
93 | | -Push Your Branch: |
94 | | - |
95 | | -bash |
96 | | -git push origin feature/your-feature-name |
97 | | -Open a Pull Request (PR): |
98 | | - |
99 | | -Navigate to the original repository on GitHub. |
100 | | - |
101 | | -Open a new PR and describe your changes in detail. |
102 | | - |
103 | | -Link to any related issues and explain why your contribution is valuable. |
| 145 | +5. **Commit Your Changes:** |
| 146 | + ``` bash |
| 147 | + git commit -am "Add [feature/bug fix]: Brief description of changes" |
| 148 | + ``` |
| 149 | +6. **Push Your Branch:** |
| 150 | + |
| 151 | + ``` bash |
| 152 | + git push origin feature/your-feature-name |
| 153 | + ``` |
| 154 | +7. **Open a Pull Request (PR):** |
| 155 | + - Navigate to the original repository on GitHub. |
| 156 | + - Open a new PR and describe your changes in detail. |
| 157 | + - Link to any related issues and explain why your contribution is valuable. |
104 | 158 |
|
105 | | -Code Style and Standards |
| 159 | +### Code Style and Standards |
106 | 160 |
|
| 161 | + - Follow the established code style for the project. |
| 162 | + - Test your changes thoroughly before submitting a PR. |
| 163 | + - Keep commits focused and descriptive. |
107 | 164 |
|
108 | 165 | ## License |
109 | 166 | This project is licensed under the **MIT License** – a permissive open-source license that allows users to freely use, |
|
0 commit comments