Removed boilerplate executable from published gem

[hsbt]

👋 I found tracking_number gem contained console executable generated by bundle gem for published gem. It will be installed PATH directory. I'm bit of surprised that behavior.

Summary by CodeRabbit

• Chores
  • Updated the gem’s configuration to remove the automatic inclusion of command-line tools.
  • Command-line functionality now requires explicit configuration if needed, while all other aspects remain unchanged.

[coderabbitai]

Walkthrough

The pull request removes the line in tracking_number.gemspec that set the executables attribute by running a shell command to list files in the bin directory. With this change, the gem will no longer automatically configure executables based on the contents of that directory. All other attributes, such as test_files, require_paths, homepage, and licenses, remain unchanged.

Changes

File	Change Summary
tracking_number.gemspec	Removed the line that set s.executables by executing a shell command that mapped bin directory files to names.

Poem

I'm just a rabbit with a playful cheer,
Leaping through code with a spring in my ear.
One old line hopped away from its nest,
Leaving the gem a bit lighter than the rest.
Hop along, dear code, to a simpler, joyful quest!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 77a5509 and 20d1438.

📒 Files selected for processing (1)

• tracking_number.gemspec (0 hunks)

💤 Files with no reviewable changes (1)

• tracking_number.gemspec

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[jkeen]

Thanks @hsbt!

[github-actions]

🎉 This PR is included in version 2.1.1 🎉

The release is available on:

• v2.1.1
• GitHub release

Your semantic-release bot 📦🚀