Improve README around the Context object (#1203) #377
main-checks.yml
on: push
checks
/
pre-commit
30s
checks
/
readme-snippets
11s
Matrix: checks / test
Annotations
16 warnings and 4 notices
|
checks / test (3.11, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0QRCSaAAAAABQVrDFJYLbQbtx6JYiWXYTQkwyQUEyMDMwMTA2MDIzAEVkZ2U=
|
|
checks / test (3.11, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.13, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0SRCSaAAAAACuJ+R+c7eESrsuQ8cVQKjZRE0yRURHRTA5MTcARWRnZQ==
|
|
checks / test (3.13, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.10, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0TRCSaAAAAAB7+SNWia29RKn5m4YpZhHyRE0yRURHRTA5MTgARWRnZQ==
|
|
checks / test (3.10, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.12, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0ThCSaAAAAACLAcDDgpgnSLycUe0ErEknQlkzRURHRTA1MjAARWRnZQ==
|
|
checks / test (3.12, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.12, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0jRCSaAAAAAA3tPSjRSjxR5BIWT7lluw1RE0yRURHRTA3MTYARWRnZQ==
|
|
checks / test (3.12, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.13, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0kBCSaAAAAABd2h01NqwyT7wzVnGU4eNmUEhYMzFFREdFMDIwNwBFZGdl
|
|
checks / test (3.13, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.11, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0jRCSaAAAAAAxqDHDxpFWTZo6l39zoJm8QkwyQUEyMDMwMTA1MDUzAEVkZ2U=
|
|
checks / test (3.11, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.10, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0jBCSaAAAAAAMzFTOopgITp0JkhXJNBQqQlkzRURHRTA1MTQARWRnZQ==
|
|
checks / test (3.10, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.12, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
|
checks / test (3.13, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
|
checks / test (3.11, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
|
checks / test (3.10, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|