-
Notifications
You must be signed in to change notification settings - Fork 4
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.
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
Ensure up-to-date dependencies in ESLint workflows. #218
Conversation
Removed the redundant restore-keys from the ESLint workflows for both frontend and backend to ensure we use up-to-date dependencies and avoid fallback issues when new dependencies are added. Signed-off-by: Nikolay Martyanov <[email protected]>
WalkthroughThe main change involves the removal of the Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
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 as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Files selected for processing (2)
- .github/workflows/eslint-back.yml (1 hunks)
- .github/workflows/eslint-front.yml (1 hunks)
Files skipped from review due to trivial changes (2)
- .github/workflows/eslint-back.yml
- .github/workflows/eslint-front.yml
Description
This PR updates the ESLint workflows for both frontend and backend by removing the redundant restore-keys. This change ensures that the workflows always use up-to-date dependencies and do not fall back to outdated ones when new dependencies are added.
Related Issues
None
How Was This Tested?
Will be tested as part of the PR review
Checklist
Before submitting your PR, please review the following:
Additional Comments (if any):
Test
Summary by CodeRabbit
restore-keys
parameter.