Which two techniques commonly reduce GitHub Actions feedback time without sacrificing necessary checks? (Choose two.)
Select all correct answers, then click Submit.
Short Explanation and Infographic
Cancel stale PR runs with concurrency and cache dependencies with solid keys—classic CI speedups. Deleting tests or rebuilding the whole monorepo on docs edits is false economy.
Full explanation below image
Full Explanation
High-performing Actions programs treat minutes and queue time as budgets. Concurrency cancel-in-progress drops obsolete PR runs. Caching (actions/cache or setup-* cache features) avoids redownloading the universe. Path filters and conditional jobs skip irrelevant work. Matrices should be purposeful, not combinatorial explosions. Deleting tests loses quality signal. Always building every monorepo package on docs changes wastes capacity. Also consider larger runners only where profiles prove CPU-bound bottlenecks, and keep artifacts lean. Measure p95 workflow duration and cache hit rates to guide investment.