chore: add .npm to gitignore (wispbyte)

[calebephrem]

No description provided.

[beetle-ai]

Summary by Beetle

This PR adds .npm/ to the .gitignore file to prevent npm cache directories from being tracked in version control. This is a standard housekeeping change that ensures build artifacts and package manager cache files remain local to each developer's environment.

📁 File Changes Summary (Consolidated across all commits):

File	Status	Changes	Description
.gitignore	Modified	+1/-0	Added .npm/ directory to the ignore list to exclude npm cache files from version control

Total Changes: 1 file changed, +1 addition, -0 deletions

🎯 Key Changes:

• npm cache exclusion: Added .npm/ to .gitignore to prevent npm's local cache directory from being committed to the repository
• Consistency with existing patterns: Follows the existing pattern of ignoring build artifacts and local data (similar to node_modules/ and data/ already present)
• Developer environment isolation: Ensures that npm cache files specific to individual developer machines don't pollute the repository

📊 Impact Assessment:

• Security: ✅ Positive - Prevents accidental exposure of cached package data that might contain sensitive information or local file paths. Reduces repository attack surface by excluding unnecessary files.
• Performance: ✅ Positive - Slightly improves git operations by reducing the number of files git needs to scan. Prevents unnecessary file tracking that could bloat repository size over time.
• Maintainability: ✅ Positive - Improves repository hygiene by following npm best practices. Reduces noise in git status output and prevents merge conflicts on cache files. Aligns with standard Node.js project conventions.
• Testing: ⚪ Neutral - No impact on testing. This is a configuration change that doesn't affect code execution or test behavior. The change is non-functional and doesn't require test coverage.

⚙️ Settings

Severity Threshold: Medium — Balanced feedback — medium and high severity issues only. — Change in Settings
Custom Rules: Define your own review rules — Set Custom Rules
PR Summary: Configure PR summary — Change in Settings

📖 User Guide

• Once repos are connected, PR analysis is automatically enabled. You can disable analysis for this repo from beetleai.dev/analysis
• Comment @beetle on any PR to start analysis manually
• Comment @beetle stop to stop any ongoing analysis

---

Follow us: Beetle · X · LinkedIn

[beetle-ai]

✅ You're good to merge this PR! No issues found. Great job!

Settings

⚙️ Settings

Severity Threshold: Medium — Balanced feedback — medium and high severity issues only. — Change in Settings
Custom Rules: Define your own review rules — Set Custom Rules
PR Summary: Configure PR summary — Change in Settings

📖 User Guide

• Once repos are connected, PR analysis is automatically enabled. You can disable analysis for this repo from beetleai.dev/analysis
• Comment @beetle on any PR to start analysis manually
• Comment @beetle stop to stop any ongoing analysis

[beetle-ai]

Summary by Beetle

This PR removes the automated PR labeling workflow that was previously used to automatically label pull requests based on conventional commit message types (feat, fix, chore, etc.). The workflow is being removed because it doesn't function properly with forked repositories, which is a common limitation of GitHub Actions workflows that require write permissions. The functionality will be replaced by a GitHub App, which can properly handle forked repository scenarios.

📁 File Changes Summary (Consolidated across all commits):

File	Status	Changes	Description
.github/workflows/pr_labeler.yml	Deleted	+0/-65	Removed the PR Commit Auto Labeler workflow that automatically parsed conventional commit messages and applied corresponding labels to pull requests. The workflow used GitHub Actions script to analyze commit messages against a regex pattern and add labels like feat, fix, chore, docs, perf, refactor, style, and test.

Total Changes: 1 file changed, +0 additions, -65 deletions

🎯 Key Changes:

• Workflow Removal: Completely removed the automated PR labeling GitHub Actions workflow
• Forked Repository Limitation: The workflow had permissions issues with forked repositories, making it ineffective for external contributors
• Future Replacement: The commit message indicates this functionality will be replaced by a GitHub App, which has better support for forked repositories
• Conventional Commits Support: The removed workflow supported standard conventional commit types (feat, fix, chore, docs, perf, refactor, style, test)
• Pagination Support: The workflow included pagination logic to handle PRs with more than 100 commits

📊 Impact Assessment:

• Security: ✅ Positive Impact - Removing a workflow that requires pull-requests: write and issues: write permissions reduces the attack surface. The future GitHub App replacement will likely use more secure OAuth-based authentication with fine-grained permissions.
• Performance: ⚪ Neutral Impact - Minimal performance impact. The workflow only ran on PR events (opened, reopened, synchronize, edited) and was relatively lightweight. Removing it slightly reduces CI/CD overhead, but the difference is negligible.
• Maintainability: ✅ Positive Impact - Removing non-functional code improves maintainability. The workflow wasn't working as intended for forked repos, so keeping it would create confusion. The planned GitHub App replacement will be more maintainable as it's designed to handle forked repository scenarios properly.
• Testing: ⚪ Neutral Impact - This change doesn't affect test coverage or testing infrastructure. The workflow was for automation convenience rather than core functionality. No tests need to be updated or added for this removal.

⚙️ Settings

Severity Threshold: Medium — Balanced feedback — medium and high severity issues only. — Change in Settings
Custom Rules: Define your own review rules — Set Custom Rules
PR Summary: Configure PR summary — Change in Settings

📖 User Guide

• Once repos are connected, PR analysis is automatically enabled. You can disable analysis for this repo from beetleai.dev/analysis
• Comment @beetle on any PR to start analysis manually
• Comment @beetle stop to stop any ongoing analysis

---

Follow us: Beetle · X · LinkedIn

[beetle-ai]

✅ You're good to merge this PR! No issues found. Great job!

Settings

⚙️ Settings

Severity Threshold: Medium — Balanced feedback — medium and high severity issues only. — Change in Settings
Custom Rules: Define your own review rules — Set Custom Rules
PR Summary: Configure PR summary — Change in Settings

📖 User Guide

• Once repos are connected, PR analysis is automatically enabled. You can disable analysis for this repo from beetleai.dev/analysis
• Comment @beetle on any PR to start analysis manually
• Comment @beetle stop to stop any ongoing analysis