19 Commits

Author	SHA1	Message	Date
bigdaz	750cdda3ed	[bot] Update dist directory	2024-04-18 19:41:35 +00:00
bigdaz	439ed0a0ac	[bot] Update dist directory	2024-04-18 01:09:48 +00:00
bigdaz	6cec5d49d4	[bot] Update dist directory	2024-04-12 16:35:47 +00:00
bigdaz	d576690f96	[bot] Update dist directory	2024-04-12 06:42:43 +00:00
bigdaz	6e48e8e40c	[bot] Update dist directory	2024-04-12 04:56:19 +00:00
bigdaz	5eedb47e5a	[bot] Update dist directory	2024-04-12 04:48:13 +00:00
bigdaz	fcf9eeaf01	Update dist directory	2024-04-11 20:05:19 +00:00
bigdaz	1fd792382e	Update dist directory	2024-04-11 18:41:42 +00:00
bigdaz	1c25312b02	Update dist directory	2024-04-11 15:50:31 +00:00
bigdaz	c31cff66cf	Update dist directory	2024-04-10 23:21:27 +00:00
bigdaz	ffea2635eb	Update dist directory	2024-04-10 18:26:18 +00:00
bigdaz	60be407ece	Update dist directory	2024-04-10 13:41:02 +00:00
daz	dec6c472c1	Build outputs	2024-04-09 15:30:42 -06:00
daz	cfe478af6a	Build outputs	2024-04-09 08:50:24 -06:00
Daz DeBoer	e235596c88	Only process build results once (#133) ... On long-lived machines, it's possible that the `.build-results` directory isn't cleared between invocations. This will result in the job summary including results from previous jobs. By marking each build-results file as 'processed' at the end of the job, we can avoid this scenario.	2024-04-08 19:44:46 -06:00
daz	59a5222069	Build outputs	2024-04-08 15:14:28 -06:00
daz	dd32675981	Build outputs	2024-04-07 22:43:28 -06:00
daz	8691214514	Build outputs	2024-04-07 16:57:18 -06:00
daz	d6f94a4073	Build outputs	2024-04-07 11:00:35 -06:00