François Mockers 97dcb279fb CI tests can exit directly after taking a screenshot (#19806) ... # Objective - Currently, CI tests take a screenshot at frame X and exits at frame Y with X < Y, and both number fixed - This means tests can take longer than they actually need when taking the screenshot is fast, and can fail to take the screenshot when it's taking too long ## Solution - Add a new event `ScreenshotAndExit` that exit directly after the screenshot is saved		2025-06-24 22:44:30 +00:00
..
build-easefunction-graphs	Add print_stdout and print_stderr lints (#17446) (#18233)	2025-03-11 19:35:48 +00:00
build-templated-pages	Upgrade to Rust Edition 2024 (#17967)	2025-02-24 03:54:47 +00:00
build-wasm-example	Add debug build option to build-wasm-example (#19312)	2025-05-24 01:43:57 +00:00
ci	Allow passing number of thread for building and testing to CI (#19359)	2025-06-16 21:19:47 +00:00
compile_fail_utils	bevyengine.org -> bevy.org (#19503)	2025-06-05 23:09:28 +00:00
example-showcase	CI tests can exit directly after taking a screenshot (#19806)	2025-06-24 22:44:30 +00:00
publish.sh	don't wait during publishing (#18563)	2025-03-26 21:27:29 +00:00