Skip to content

fix: add shellcheck and fix a few warnings #22569

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

leshikus
Copy link

@leshikus leshikus commented Apr 4, 2025

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Toolchain Guide
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.
  • Optional. My organization is added to USERS.md.
  • Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

@leshikus leshikus requested review from a team as code owners April 4, 2025 12:27
Copy link

bunnyshell bot commented Apr 4, 2025

❌ Preview Environment deleted from Bunnyshell

Available commands (reply to this comment):

  • 🚀 /bns:deploy to deploy the environment

@leshikus
Copy link
Author

leshikus commented Apr 4, 2025

Using shellcheck can potentially improve the quality of the project shell scripts.

@leshikus leshikus force-pushed the master branch 2 times, most recently from 60d40a3 to e00edaf Compare April 4, 2025 12:41
@leshikus leshikus closed this Apr 4, 2025
@leshikus leshikus reopened this Apr 4, 2025
Copy link

bunnyshell bot commented Apr 4, 2025

❗ Preview Environment deployment failed on Bunnyshell

See: Environment Details | Pipeline Logs

Available commands (reply to this comment):

  • 🚀 /bns:deploy to redeploy the environment
  • /bns:delete to remove the environment

Signed-off-by: Alexei Fedotov <[email protected]>
Copy link

codecov bot commented Apr 4, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.01%. Comparing base (73495d0) to head (6899b28).

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #22569      +/-   ##
==========================================
+ Coverage   55.96%   56.01%   +0.04%     
==========================================
  Files         343      343              
  Lines       57527    57527              
==========================================
+ Hits        32197    32225      +28     
+ Misses      22679    22656      -23     
+ Partials     2651     2646       -5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@olivergondza
Copy link
Contributor

Thanks a lot for this improvement! I am filing #22686 that fixes many of those warnings.

I advocate not to exclude SC2086, SC2046, SC2068, SC2206, SC2048, SC2128, SC2207. The linked PR makes an effort to address them, and they have a tendency to cause subtle problems.

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.

2 participants