fix(ci): a bare '# shellcheck' comment is parsed as a directive

[hyperpolymath]

Line 351's comment was literally '# shellcheck'. Comments beginning '# shellcheck' are DIRECTIVES, so this was read as a malformed one and the file failed to parse. Reworded to '# ShellCheck linting'.

Found by an estate-wide shellcheck sweep of 5,111 tracked scripts across 375 repos. This file was one of 11 that fail to parse (SC1073/SC1072) — shellcheck stops analysing at the failure, so everything after it was never checked either.

Verified: shellcheck -S error now reports 0 findings for this file.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: ac07e056-63a4-4ee7-9bf4-b98a0199cb75

📥 Commits

Reviewing files that changed from the base of the PR and between c4db2ef and 2ce8641.

📒 Files selected for processing (1)

• ci-scripts/lint.sh

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

📜 Recent review details

⏰ Context from checks skipped due to timeout. (2)

• GitHub Check: Codacy Static Code Analysis
• GitHub Check: Gitar

⚠️ CI failures not shown inline (2)

GitHub Actions: Automatic Dependency Submission (NuGet) / 0_submit-nuget.txt: Automatic Dependency Submission (NuGet)

Conclusion: failure

View job details

##[group]Run # Find all project files
 �[36;1m# Find all project files�[0m
 �[36;1mproject_files=$(find . -type f \( -name "*.csproj" -o -name "*.sln" -o -name "*.vbproj" -o -name "*.vcxproj" -o -name "*.fsproj" \) | grep -v '/obj/' | grep -v '/bin/' | head -20)�[0m
 �[36;1m�[0m
 �[36;1mif [ -z "$project_files" ]; then�[0m
 �[36;1m  echo "valid-project=false" >> "$GITHUB_OUTPUT"�[0m
 �[36;1m  echo "### :warning: No .NET project files found" >> $GITHUB_STEP_SUMMARY�[0m
 �[36;1m  echo "" >> $GITHUB_STEP_SUMMARY�[0m
 �[36;1m  echo "**This repository does not appear to contain any .NET project files.**" >> $GITHUB_STEP_SUMMARY�[0m
 �[36;1m  echo "" >> $GITHUB_STEP_SUMMARY�[0m
 �[36;1m  echo "Searched for: *.csproj, *.sln, packages.config, *.vbproj, *.vcxproj, *.fsproj" >> $GITHUB_STEP_SUMMARY�[0m
 �[36;1m  echo "" >> $GITHUB_STEP_SUMMARY�[0m
 �[36;1m  echo "If this is a .NET project, ensure your project files are committed to the repository." >> $GITHUB_STEP_SUMMARY�[0m
 �[36;1m  echo "::error::No .NET project files found in repository"�[0m

---

GitHub Actions: Automatic Dependency Submission (NuGet) / submit-nuget: Automatic Dependency Submission (NuGet)

Conclusion: failure

View job details

##[group]Run # Find all project files
 �[36;1m# Find all project files�[0m
 �[36;1mproject_files=$(find . -type f \( -name "*.csproj" -o -name "*.sln" -o -name "*.vbproj" -o -name "*.vcxproj" -o -name "*.fsproj" \) | grep -v '/obj/' | grep -v '/bin/' | head -20)�[0m
 �[36;1m�[0m
 �[36;1mif [ -z "$project_files" ]; then�[0m
 �[36;1m  echo "valid-project=false" >> "$GITHUB_OUTPUT"�[0m
 �[36;1m  echo "### :warning: No .NET project files found" >> $GITHUB_STEP_SUMMARY�[0m
 �[36;1m  echo "" >> $GITHUB_STEP_SUMMARY�[0m
 �[36;1m  echo "**This repository does not appear to contain any .NET project files.**" >> $GITHUB_STEP_SUMMARY�[0m
 �[36;1m  echo "" >> $GITHUB_STEP_SUMMARY�[0m
 �[36;1m  echo "Searched for: *.csproj, *.sln, packages.config, *.vbproj, *.vcxproj, *.fsproj" >> $GITHUB_STEP_SUMMARY�[0m
 �[36;1m  echo "" >> $GITHUB_STEP_SUMMARY�[0m
 �[36;1m  echo "If this is a .NET project, ensure your project files are committed to the repository." >> $GITHUB_STEP_SUMMARY�[0m
 �[36;1m  echo "::error::No .NET project files found in repository"�[0m

🔇 Additional comments (1)

ci-scripts/lint.sh (1)

351-351: LGTM!

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated the shell linting section label for improved clarity.

Walkthrough

The lint script now uses # ShellCheck linting as the section comment. ShellCheck discovery, execution, counters, and error handling remain unchanged.

Changes

Lint script comment update

Layer / File(s)	Summary
ShellCheck section comment ci-scripts/lint.sh	Renames the shell-checking section comment. No functional behaviour changes.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 2ce86

This is a localized comment rewording that restores shellcheck parsing without changing runtime behavior; no actionable merge-blocking risk remains after normal checks and review.

Poem

A rabbit hops past the linting sign
The ShellCheck label now looks fine
No commands change
No counters rearrange
Just clearer words in a neat little line

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the ShellCheck parsing issue and the corrective change. It is concise and directly related to the main change.
Description check	✅ Passed	The description accurately explains the malformed ShellCheck directive, the comment change, the affected error codes, and the verification result.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[gitar-bot]

Important

You are using the Gitar free plan. Upgrade to unlock code review, CI analysis, auto-apply, custom automations, and more.

_Gitar

[codacy-production]

Pull Request Overview

This PR corrects a syntax issue in the CI lint script where a plain comment starting with # shellcheck was being misinterpreted as a malformed directive, preventing ShellCheck from completing its analysis. Codacy reports that the changes are up to standards.

While the change is direct, there is currently no confirmation that the script successfully passes ShellCheck parsing after this modification. Addressing this validation gap will ensure the SC1073 and SC1072 errors are resolved and that the script is now fully analyzed in CI.

Test suggestions

• Verify that ShellCheck parses the lint script without errors.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify that ShellCheck parses the lint script without errors.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}