Skip to content

fix: don't always use an exclusive lock in nargo check #7120

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
TomAFrench merged 1 commit into from
Jan 20, 2025

fix: don't always use an exclusive lock in `nargo check`

36ad0e6
Select commit
Loading
Failed to load commit list.
Merged

fix: don't always use an exclusive lock in nargo check #7120

fix: don't always use an exclusive lock in `nargo check`
36ad0e6
Select commit
Loading
Failed to load commit list.

Workflow runs completed with no jobs