xc
xc copied to clipboard
Markdown defined task runner.
I'm enjoying using the interactive mode. One thing I've noticed, is that I'll often run `xc`, select `docker-build` and it will start. Then I'll make some changes, and want to...
Given: - a task `X` with zero or more inputs - a task `Y` with one or more inputs - a `requires` relationship from `X` to `Y` When: - i...
xtrace output is useful in some cases, but in general would be better if not enabled. This is on by default and it seems there is no way to disable...
Having tasks auto-documented by using `xc` is a strong selling point for the tool, however for projects/repo's with a huge amount of existing tasks, it's daunting to transition if you'd...
The docs site currently has no custom 404 page.
It would be nice if `xc` supported task definition documents in formats other than markdown — for example AsciiDoc, reStructuredText, and other [lightweight markup formats](https://en.wikipedia.org/wiki/Lightweight_markup_language). Note: This is just speculative...
It would be useful if the documentation compared xc with its closest alternatives, [maid](https://github.com/egoist/maid) and [mask](https://github.com/jacobdeichert/mask). It looks like maid, mask, and xc are the three prominent task runners based...
When I try to use tab completions in Fish shell I see the following (Go lang) error: ```fish xc despanic: COMP_POINT env should be integer, got: goroutine 1 [running]: github.com/posener/complete/v2.Complete({0x1042e5481,...
I have a use case where I want to share some state between tasks. Take this simplistic example: ```md # `runme` Test ## Tasks ### hello /```bash export FOO=bar /```...