📌 Information
Having a good method of tracking what's finished and what needs to be done is crucial once a project grows large enough. Of course, for team-driven development having a full-featured issue tracker such as GitHub or similar is preferable, but for solo-developers GitHub can feel like an over-engineered solution to a simple problem.
(The name "Brakoll" is derived from the swedish word "koll", which is the act of surveying or scanning something.)
The idea for this project was inspired directly by this video.
📦 Install
💻 Usage
Adding a new issue
When you want to add something to your issue list you simply type it out in your project (I would advise you to create a snippet for this; for example "issue").
// *brakoll - d: fix typo in debug print, p: 10, t: debug, s: open
- d: description of the issue (obligatory)
- p: priority from 0 to infinity where the highest number is the most critical priority (optional - fallback: 0)
- t: tag (optional - fallback: n/a)
- s: status [ (op)en | (pr)ogress | (cl)osed ] (optional - fallback: open)
[!IMPORTANT]
Issues are currently only single-line! If you want a long description, write it all on a single line or alternatively refer to a bigger document somewhere else inside your description. The prefix "*brakoll" is required but whatever is before it on the line is of no importance to the parser and will be ignored, e.g "#", "//", "--" or any other comment syntax.
Here's a way to integrate Brakoll into your neovim config using luasnip:
local ls = require
local s = ls.
local t = ls.
local i = ls.
return
Subcommands and flags
All the issues listed, sorted by priority and status:
brakoll
Filter issues by tag:
brakoll -t <tag>
Filter issues by status:
brakoll -s <status>
Summary of all issues:
brakoll summary
Display help and version information:
brakoll help
📜 License
This project is licensed under the MIT License.