fix: The CLI tool uses .gitignore to filter packaged files during deployment.

[KaneOne]

What does this PR do?

fix: The CLI tool uses .gitignore to filter packaged files during deployment.

Summary by CodeRabbit

New Features

• Deployment packages now automatically exclude files matching .gitignore patterns, simplifying the packaging process while maintaining existing deployment behavior.

[coderabbitai]

Walkthrough

The change adds .gitignore support to the deployment packaging process in the deployment utility. When packaging files, the code now loads patterns from a .gitignore file in the directory being packaged, if present. The tar creation filtering logic is extended to skip files matching these ignore patterns after normalizing paths. The root or current directory receives special handling to remain included. All existing packaging behavior is preserved, including gzip compression and original working directory context.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding .gitignore support to filter files during deployment packaging.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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 and usage tips.}