Skip to content

chore: remove unnecessary lint-staged config and dependency #78

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

chore: remove unnecessary lint-staged config and dependency #78

wants to merge 1 commit into from

Conversation

G4URAV001
Copy link

@G4URAV001 G4URAV001 commented May 4, 2025 •
edited
Loading

fixes PSMRI/AMRIT#98

Description
Removed unnecessary lint-staged configuration and dependency from the project. The lint-staged configuration was targeting TypeScript, CSS, and HTML files in the src directory, but none of these file types exist in the repository as it's a Java-based project. Also removed the pre-commit Git hook that was using lint-staged since it's no longer needed.

Changes made:

  • Removed the lint-staged configuration from package.json
  • Removed the lint-staged dependency from package.json
  • Removed the pre-commit hook from .husky directory
  • Updated package-lock.json by running npm install

These changes help clean up the project by removing unused configurations and dependencies, making the repository more maintainable.

Type of change

  • Bug fix
  • New feature
  • Enhancement
  • Refactoring
  • Documentation
  • Other ( please specify )

How Has This Been Tested?
The changes have been verified by:

  • Confirming no TypeScript, CSS, or HTML files exist in the src directory
  • Verifying that the package.json and package-lock.json files are valid after removing the dependency
  • Confirming that npm install runs successfully after the changes

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • Any dependent changes have been merged and published in downstream modules

image

Summary by CodeRabbit

  • Chores
    • Removed pre-commit linting and formatting checks.
    • Removed the lint-staged package and its configuration from the project.

@coderabbitai coderabbitai
Copy link

coderabbitai bot commented May 4, 2025 •
edited
Loading

Walkthrough

This change removes the lint-staged tool and its configuration from the project. The .husky/pre-commit hook file, which previously invoked lint-staged, has been deleted. Additionally, the lint-staged configuration and its dependency have been removed from the package.json file. No other scripts or dependencies were modified, and no exported or public entities were changed.

Changes

File(s) Change Summary
.husky/pre-commit Deleted the pre-commit hook that ran npx lint-staged on staged files.
package.json Removed lint-staged configuration and deleted lint-staged from dependencies.

Possibly related PRs

Poem

The linting stage has hopped away,
No more hooks before commit day.
With Husky quiet, the code feels light,
No staged checks in the burrow tonight.
A rabbit waves goodbye, so neat—
To lint-staged’s tidy little seat!
🐇✨

📜 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 d74cc05 and 45a7aac.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (2)
  • .husky/pre-commit (0 hunks)
  • package.json (1 hunks)
💤 Files with no reviewable changes (1)
  • .husky/pre-commit
🔇 Additional comments (1)
package.json (1)

19-19: Remove redundant lint-staged dependency
The lint-staged package has been correctly removed from devDependencies, matching the project’s Java-only codebase and cleaning up unused tooling.

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
🪧 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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @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.

@G4URAV001
Copy link
Author

cc: @drtechie

@sonarqubecloud SonarQubeCloud
Copy link

sonarqubecloud bot commented May 4, 2025

Quality Gate Passed 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Remove Unused lint-staged Configuration for Non-Existing ts and css Files
1 participant
@G4URAV001