From c3155a50f51b6d422d0ee15aa29b84bf7590343e Mon Sep 17 00:00:00 2001 From: iximeow Date: Sun, 25 Jun 2023 04:44:36 -0700 Subject: try formatting differently? --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 91994c6..77def1f 100644 --- a/README.md +++ b/README.md @@ -9,12 +9,12 @@ notably: * anyone can run CI jobs (if the server is willing to talk to you) * (soon) the CI runner should be able to run locally in a `watch` manner - CI builds should be testable before reaching CI * i explicitly intend this system to support non-github triggers - [ ] say, post-recv hooks in other git repos - [ ] or a patched cgit to show build statuses - [ ] or a cron job for non-build-oriented work that should none the less be repeatable +- [ ] say, post-recv hooks in other git repos +- [ ] or a patched cgit to show build statuses +- [ ] or a cron job for non-build-oriented work that should none the less be repeatable * i expect this system to have first-class support for capturing metrics from builds and reporting on changes - [ ] and yes, i expect build-o-tron to double as a performance testing environment - [ ] including replaying a history of build jobs on a new runner to establish performance baselines and differences +- [ ] and yes, i expect build-o-tron to double as a performance testing environment +- [ ] including replaying a history of build jobs on a new runner to establish performance baselines and differences * it knows how to send emails nagging me about builds and their outcomes. other tools can do this too i'm sure, but i can make these useful. [ ] in the future, figure out how to do certain kinds of limited deployments after successful goodfile executions. probably goodfile extensions to do those deployments, so success implies successful deployments. -- cgit v1.1