gmgauthier/grokkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 23 Wiki Activity

docs(workon): clarify references to workon command in documentation
All checks were successful
CI / Test (push) Successful in 32s
Details
CI / Lint (push) Successful in 25s
Details
CI / Build (push) Successful in 20s
Details

Browse Source 
Update the description in todo/queued/workon.md to specifically mention the `workon` command instead of the generic "feature" for better clarity.
This commit is contained in:
Gregory Gauthier 2026-03-31 15:18:20 +01:00
parent 8031190d81
commit 4dff2039b0
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
todo/queued/workon.md
View File

@ -13,7 +13,7 @@
Grokkit is being customized to suit my own development workflow. So, there are a number of features that may not be translatable to other developers' habits. As such, this feature assumes that the repository has a "todo" folder with a "queued", "doing" and "completed" subfolder, that function as the in-situ ticketing system. If the "todo" folder is not present, grokkit will create it.
Also, if no IDE is specified in the config, the feature will default to not opening the editor. If `cnadd` is not available, the feature will default to not logging the beginning of the work.
Also, if no IDE is specified in the config, the `workon` command will default to not opening the editor. If `cnadd` is not available, the `workon` command will default to not logging the beginning of the work.
**Benefits**: