Skip to content

Fix a few ShellCheck warnings and stylistic inconsistencies #1908

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.

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
merged 2 commits into from
Mar 22, 2025

Conversation

EliahKagan
Copy link
Member

This was originally intended to be part of much broader changes, to more scripts, along the same lines, and adding a ShellCheck CI job. That will likely still happen, but it's not clear when it will get done. Rather than wait, this brings in the small benefits of these changes.

This was originally intended to be part of much broader changes, to
more scripts, along the same lines, and adding a ShellCheck CI job.
That will likely still happen, but it's not clear when it will get
done. Rather than wait, this brings in the small benefits of these
changes.
This was regenerated via `cargo nextest --workspace --no-fail-fast`
and verifying that there were no failures, then committing the
one changed file, on an Arch Linux system with Git 2.49.0.

This is the only tracked archive that changes due to the script
changes in the previous commit. The other changed scripts are
either to scripts whose generated archives are `.gitignore`d, or
to scripts that are not fixture scripts (so no archives at all).
@EliahKagan EliahKagan enabled auto-merge March 22, 2025 15:41
@EliahKagan EliahKagan merged commit c8c42b4 into GitoxideLabs:main Mar 22, 2025
21 checks passed
@EliahKagan EliahKagan deleted the run-ci/scripts branch March 22, 2025 16:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant