Fix hardcoded script name in usage output to use dynamic basename

[Copilot]

Problem

The add-items-to-project.sh script had hardcoded references to add-to-project.sh in its usage message, which was incorrect and confusing for users. The usage output showed the wrong script name regardless of how the script was actually named or called.

Solution

Replaced the hardcoded script name references with $(basename "$0") to dynamically display the actual script filename in the usage output.

Changes Made

• Line 5: "Usage: add-to-project.sh ..." → "Usage: $(basename "$0") ..."
• Line 7: "Example: add-to-project.sh ..." → "Example: $(basename "$0") ..."
• Line 8: "Example: add-to-project.sh ..." → "Example: $(basename "$0") ..."

Before vs After

Before (hardcoded):

Usage: add-to-project.sh <org_or_user>/<project_number> <search_query>
Example: add-to-project.sh ekroon/1 1 is:open is:issue
Example: add-to-project.sh ekroon/1 1 is:open is:pr

After (dynamic):

Usage: add-items-to-project.sh <org_or_user>/<project_number> <search_query>
Example: add-items-to-project.sh ekroon/1 1 is:open is:issue
Example: add-items-to-project.sh ekroon/1 1 is:open is:pr

Benefits

• ✅ Usage output now correctly shows the actual script filename
• ✅ Works correctly when called with full path
• ✅ Works correctly when called via symlink (shows symlink name)
• ✅ More maintainable - no need to update usage if script is renamed
• ✅ All other script functionality remains unchanged

This is a minimal, surgical change that improves user experience without affecting any core functionality.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.