Skip to content

fix: bd doctor detects committed runtime/sensitive files that should be gitignored (GH#2535) #7286

fix: bd doctor detects committed runtime/sensitive files that should be gitignored (GH#2535)

fix: bd doctor detects committed runtime/sensitive files that should be gitignored (GH#2535) #7286

Triggered via pull request March 12, 2026 16:33
Status Success
Total duration 2m 56s
Artifacts

ci.yml

on: pull_request
Check version consistency
7s
Check version consistency
Check doc flags freshness
54s
Check doc flags freshness
Check for .beads changes
18s
Check for .beads changes
Test (Windows - smoke)
1m 17s
Test (Windows - smoke)
Check formatting
15s
Check formatting
Lint
1m 8s
Lint
Test Nix Flake
42s
Test Nix Flake
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
Test Nix Flake
Process completed with exit code 1.
Test (macos-latest)
icu4c@78 78.2 is already installed and up-to-date. To reinstall 78.2, run: brew reinstall icu4c@78
Test (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/