Skip to content

chore(Tactic/GRewrite): rewrite grw family tactic docstrings (#36283) #23032

chore(Tactic/GRewrite): rewrite grw family tactic docstrings (#36283)

chore(Tactic/GRewrite): rewrite grw family tactic docstrings (#36283) #23032

Triggered via push April 14, 2026 13:33
Status Success
Total duration 17m 42s
Artifacts 2

bors.yml

on: push
ci (staging)  /  Upload to cache
1m 30s
ci (staging) / Upload to cache
ci (staging)  /  Post-Build Step
2m 45s
ci (staging) / Post-Build Step
ci (staging)  /  Post-CI job
6s
ci (staging) / Post-CI job
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
ci (staging) / Lint style
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ci (staging) / Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: leanprover-community/gh-problem-matcher-wrap@20007cb926a46aa324653a387363b52f07709845. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ci (staging) / Post-CI job
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 8BitJonny/gh-get-current-pr@4056877062a1f3b624d5d4c2bedefa9cf51435c9. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
cache-staging
324 MB
sha256:4fc3c60dc8307c2ea7b609e25de43e35814ac64083b050daac803d4bea658c21
import-graph
285 KB
sha256:ac736274d14b354ef877ad9f0ae2312061d1a5dd39fddb493024fd6b2a974b84