Tucker McKnight <tucker@pangolin.lan> | Sun Jan 04 2026
some task descriptions
178 179 180 181 182
},
"active": "ed8907ba19d17623",
"lastOpenFiles": [
"page.md",
"index.md"
]178 179 180 181 182 183 184
},
"active": "ed8907ba19d17623",
"lastOpenFiles": [
"tasks/branch-globs.md.html",
"tasks",
"page.md",
"index.md"
]1 2 3 4 5 6
These markdown files are used to keep track of tasks like an issue tracker.
- [ ] a task
- [ ] another task
[test link](./page.md)1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
These markdown files are used to keep track of tasks like an issue tracker.
Right now I'm just using this space to brainstorm improvements to the repo.
The goal is to eventually have extensive documentation here.
> Note: to link to other pages, add a `.html` to the end of the page you
> are linking to. When the site is rendered, markdown files get rendered
> at a URL like `path/to/file.md.html`. So to link to that page, do
> `[link text](./path/to/file.md.html)`.
## Tasks and Works in Progress
### Branch Globs
- Goal: allow users to specify a glob pattern (like `deploy/**`) instead of spelling out every branch name in full in their config file
- [Project page](./tasks/branch-globs.md.html)
### Better Template Readability
- Goal: Do not simply have a bunch of strings as the HTML for the default virtual
template. Maybe look into using mithril for server-side rendering?
### Tag snapshots
- Goal: have HTML pages generated for user-specified tags in the repo, not
just each branch head.
-1 0 1 2
# Branch Globs
> Goal: allow users to specify a glob pattern (like `deploy/**`) instead of spelling out every branch name that will be included in their repository.
Git branch: `branch-globs`