Skip to content

feat:script to check ts-ignore #3246

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

Merged

Conversation

shivasankaran18
Copy link

@shivasankaran18 shivasankaran18 commented Feb 18, 2025

What kind of change does this PR introduce?
Added py script to check ts-ignore in the PR files
Modified pull-request.yml to have a single job pyhton checks(biome,code coverage, check ts-ignore)

Issue Number: 3229

Fixes : #3229

If relevant, did you update the documentation?

Summary

Does this PR introduce a breaking change?

Checklist

CodeRabbit AI Review

  • I have reviewed and addressed all critical issues flagged by CodeRabbit AI
  • I have implemented or provided justification for each non-critical suggestion
  • I have documented my reasoning in the PR comments where CodeRabbit AI suggestions were not implemented

Test Coverage

  • I have written tests for all new changes/features
  • I have verified that test coverage meets or exceeds 95%
  • I have run the test suite locally and all tests pass

Other information

Have you read the contributing guide?

Summary by CodeRabbit

  • New Features

    • Enhanced our automated code validation with an additional check for TypeScript directives to ensure quality.
  • Chores

    • Streamlined the background verification process by consolidating multiple checks into a unified workflow for improved efficiency and reliability.
    • Updated the workflow to improve clarity and maintainability.
    • Introduced a script to detect and report the usage of @ts-ignore comments in TypeScript files.

Copy link

coderabbitai bot commented Feb 18, 2025

Warning

Rate limit exceeded

@palisadoes has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 26 minutes and 43 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between f02db61 and 48989d7.

📒 Files selected for processing (1)
  • .github/workflows/scripts/detect_ts_ignore.py (1 hunks)

Walkthrough

The pull request updates the GitHub Actions workflow by consolidating separate jobs into a single job named python_checks within the pull-request.yml file. The new job handles Python-related checks by renaming existing steps (focused on biome ignore and code coverage disable checks) and adding a new step for running TypeScript ignore checks. Additionally, a new script (detect_ts_ignore.py) is introduced to scan specified TypeScript files for occurrences of the @ts-ignore directive, using command-line arguments and error handling for robust execution.

Changes

File(s) Change Summary
.github/workflows/pull-request.yml Removed jobs check_biome_ignore and check_code_coverage_disable; added new job python_checks that consolidates checks. Within python_checks, steps were renamed to Run Biome Ignore Check and Run Code Coverage Disable Check, and a new step Run TS Ignore Check was added.
.github/workflows/scripts/detect_ts_ignore.py Introduced a new script with the function check_ts_ignore(files) and an entry point for execution. The script scans provided files for @ts-ignore directives, reports their location, and handles file errors accordingly.

Possibly related PRs

  • Biome linting disable check script #2827: The changes in the main PR are related to the modifications in the workflow that include biome ignore checks, which directly connect to the changes in the retrieved PR that also focus on biome ignore checks.
  • Enhance Linting and Code Coverage Checks with New Scripts and Job Separation #2810: The changes in the main PR are related to the introduction of a new job for TypeScript ignore checks, which aligns with the enhancements made in the retrieved PR that also focuses on checks for code coverage disable statements and eslint disable comments.
  • added codecov code for showing statistics #2871: The changes in the main PR are related to the introduction of a new job for TypeScript ignore checks, which aligns with the modifications in the retrieved PR that also involve updates to the GitHub Actions workflow, specifically regarding coverage checks and job dependencies.

Suggested labels

ignore-sensitive-files-pr

Suggested reviewers

  • palisadoes
  • varshith257

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?

❤️ 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.

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. (Beta)
  • @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.

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.

Copy link

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🔭 Outside diff range comments (1)
.github/workflows/pull-request.yml (1)

185-185: ⚠️ Potential issue

Update job dependencies after consolidation.

The Run-Tests job still depends on the removed check_code_coverage_disable job.

Apply this diff to fix the dependencies:

-    needs: [Code-Quality-Checks, check_code_coverage_disable]
+    needs: [Code-Quality-Checks, python_checks]
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8e9a5e1 and 1709ab0.

📒 Files selected for processing (2)
  • .github/workflows/pull-request.yml (2 hunks)
  • .github/workflows/scripts/detect_ts_ignore.py (1 hunks)
🧰 Additional context used
🪛 Ruff (0.8.2)
.github/workflows/scripts/detect_ts_ignore.py

4-4: Missing return type annotation for public function check_ts_ignore

Add return type annotation: int

(ANN201)


4-4: Missing type annotation for function argument files

(ANN001)


18-18: Unnecessary open mode parameters

Remove open mode parameters

(UP015)


25-25: Do not catch blind exception: Exception

(BLE001)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Analyse Code With CodeQL (typescript)
🔇 Additional comments (2)
.github/workflows/scripts/detect_ts_ignore.py (1)

31-37: LGTM! Well-structured CLI implementation.

The main entry point is well-implemented with proper argument parsing and exit code handling.

.github/workflows/pull-request.yml (1)

51-79: LGTM! Well-structured job consolidation.

The Python checks are now consolidated into a single job with clear step names and proper file handling.

Copy link

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 4

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1709ab0 and da90539.

📒 Files selected for processing (1)
  • .github/workflows/scripts/detect_ts_ignore.py (1 hunks)
🧰 Additional context used
🪛 Ruff (0.8.2)
.github/workflows/scripts/detect_ts_ignore.py

25-25: Replace aliased errors with OSError

Replace with builtin OSError

(UP024)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Analyse Code With CodeQL (typescript)
🔇 Additional comments (1)
.github/workflows/scripts/detect_ts_ignore.py (1)

1-4: LGTM!

The imports are appropriate, and the function signature is well-defined with proper type annotations.

Copy link

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

coderabbitai[bot]
coderabbitai bot previously approved these changes Feb 18, 2025
@shivasankaran18
Copy link
Author

@palisadoes could you review my PR ?

Copy link

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between eebf3cb and 3e3d341.

📒 Files selected for processing (1)
  • .github/workflows/scripts/detect_ts_ignore.py (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
.github/workflows/scripts/detect_ts_ignore.py (1)
Learnt from: shivasankaran18
PR: PalisadoesFoundation/talawa-api#3246
File: .github/workflows/scripts/detect_ts_ignore.py:25-25
Timestamp: 2025-02-18T17:15:18.046Z
Learning: In Python 3, `IOError` is an alias for `OSError`, so using just `OSError` in except clauses is preferred for cleaner code.
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Analyse Code With CodeQL (typescript)
🔇 Additional comments (2)
.github/workflows/scripts/detect_ts_ignore.py (2)

8-17: LGTM!

The function signature has proper type annotations and the docstring is well-formatted with matching type information.


35-41: Add validation for TypeScript files.

The script should validate that the provided files are TypeScript files to avoid unnecessary processing.

Apply this diff to add file validation:

     parser = argparse.ArgumentParser(description="Check for @ts-ignore in changed files.")
     parser.add_argument("--files", nargs="+", help="List of changed files", required=True)
     args = parser.parse_args()
 
+    # Filter TypeScript files
+    ts_files = [f for f in args.files if f.endswith(('.ts', '.tsx'))]
+    if not ts_files:
+        print("ℹ️ No TypeScript files to check.")
+        sys.exit(0)
+
-    exit_code = check_ts_ignore(args.files)
+    exit_code = check_ts_ignore(ts_files)
     sys.exit(exit_code)

Copy link

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3e3d341 and 750d888.

📒 Files selected for processing (1)
  • .github/workflows/scripts/detect_ts_ignore.py (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
.github/workflows/scripts/detect_ts_ignore.py (1)
Learnt from: shivasankaran18
PR: PalisadoesFoundation/talawa-api#3246
File: .github/workflows/scripts/detect_ts_ignore.py:25-25
Timestamp: 2025-02-18T17:15:18.046Z
Learning: In Python 3, `IOError` is an alias for `OSError`, so using just `OSError` in except clauses is preferred for cleaner code.
🪛 Ruff (0.8.2)
.github/workflows/scripts/detect_ts_ignore.py

32-32: SyntaxError: Expected an indented block after if statement

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Analyse Code With CodeQL (typescript)
🔇 Additional comments (3)
.github/workflows/scripts/detect_ts_ignore.py (3)

1-7: LGTM! Well-structured script setup.

The script has a proper shebang line, necessary imports, and a well-defined regex pattern constant.


8-17: LGTM! Well-documented function with proper type annotations.

The function is well-documented with Google-style docstrings and includes appropriate type annotations.


37-43: LGTM! Well-structured main entry point.

The argument parsing and exit code handling are implemented correctly.

Copy link

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

coderabbitai[bot]
coderabbitai bot previously approved these changes Feb 19, 2025
@shivasankaran18
Copy link
Author

@palisadoes could you review my PR now?

Copy link
Contributor

@palisadoes palisadoes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please see comments

Copy link

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

1 similar comment
Copy link

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

Copy link

codecov bot commented Feb 19, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 46.52%. Comparing base (8e9a5e1) to head (48989d7).
Report is 12 commits behind head on develop-postgres.

Additional details and impacted files
@@                 Coverage Diff                  @@
##           develop-postgres    #3246      +/-   ##
====================================================
+ Coverage             45.48%   46.52%   +1.04%     
====================================================
  Files                   455      455              
  Lines                 33935    33940       +5     
  Branches                757      812      +55     
====================================================
+ Hits                  15435    15791     +356     
+ Misses                18496    18149     -347     
+ Partials                  4        0       -4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

♻️ Duplicate comments (1)
.github/workflows/scripts/detect_ts_ignore.py (1)

31-32: ⚠️ Potential issue

Move success message outside the file loop.

The success message is currently inside the file loop, which means it will be printed for each file that doesn't have violations. This makes the output noisy and confusing.

Apply this diff to fix the success message placement:

-        if not ts_ignore_found:
-            print("✅ No '@ts-ignore' comments found in the files.")

    return 1 if ts_ignore_found else 0
+    if not ts_ignore_found:
+        print("✅ No '@ts-ignore' comments found in the files.")
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 750d888 and 07452c6.

📒 Files selected for processing (2)
  • .github/workflows/pull-request.yml (3 hunks)
  • .github/workflows/scripts/detect_ts_ignore.py (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
.github/workflows/scripts/detect_ts_ignore.py (1)
Learnt from: shivasankaran18
PR: PalisadoesFoundation/talawa-api#3246
File: .github/workflows/scripts/detect_ts_ignore.py:25-25
Timestamp: 2025-02-18T17:15:18.046Z
Learning: In Python 3, `IOError` is an alias for `OSError`, so using just `OSError` in except clauses is preferred for cleaner code.
🪛 Ruff (0.8.2)
.github/workflows/scripts/detect_ts_ignore.py

36-36: Missing return type annotation for public function main

Add return type annotation: None

(ANN201)

⏰ Context from checks skipped due to timeout of 90000ms (1)
🔇 Additional comments (1)
.github/workflows/pull-request.yml (1)

51-79: LGTM!

The python_checks job is well-structured and correctly consolidates Python-related checks. The job:

  1. Sets up Python environment
  2. Gets changed files
  3. Runs all three checks: biome ignore, code coverage disable, and ts ignore

Copy link

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

@shivasankaran18
Copy link
Author

@coderabbitai full review

Copy link

coderabbitai bot commented Feb 19, 2025

✅ Actions performed

Full review triggered.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🔭 Outside diff range comments (3)
.github/workflows/scripts/detect_ts_ignore.py (3)

47-48: ⚠️ Potential issue

Fix formatting issues.

Remove the extra blank line at the end of the file to fix Black formatting issues.

Apply this diff to fix the formatting:

if __name__ == "__main__":
    main()
-    
-

47-48: ⚠️ Potential issue

Fix formatting issues.

The file has formatting issues that need to be fixed:

  1. Remove the extra blank line at the end of the file.
  2. Run Black formatter to fix code style issues.

Run the following command to fix formatting:

black .github/workflows/scripts/detect_ts_ignore.py

47-48: ⚠️ Potential issue

Fix formatting issues.

The file has formatting issues that are causing the Black check to fail:

  1. Trailing whitespace on line 47
  2. Empty line at the end of file

Run black to automatically fix these issues:

black .github/workflows/scripts/detect_ts_ignore.py
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8e9a5e1 and 939710b.

📒 Files selected for processing (2)
  • .github/workflows/pull-request.yml (3 hunks)
  • .github/workflows/scripts/detect_ts_ignore.py (1 hunks)
👮 Files not reviewed due to content moderation or server errors (2)
  • .github/workflows/scripts/detect_ts_ignore.py
  • .github/workflows/pull-request.yml
🧰 Additional context used
🧠 Learnings (1)
.github/workflows/scripts/detect_ts_ignore.py (1)
Learnt from: shivasankaran18
PR: PalisadoesFoundation/talawa-api#3246
File: .github/workflows/scripts/detect_ts_ignore.py:25-25
Timestamp: 2025-02-18T17:15:18.046Z
Learning: In Python 3, `IOError` is an alias for `OSError`, so using just `OSError` in except clauses is preferred for cleaner code.
🪛 GitHub Actions: Pull request workflow
.github/workflows/scripts/detect_ts_ignore.py

[error] 1-1: Black formatting check failed. 1 file would be reformatted. Run 'black' to fix code style issues in this file.

🔇 Additional comments (8)
.github/workflows/scripts/detect_ts_ignore.py (4)

36-43: LGTM!

The main function correctly handles argument parsing, executes the check, and manages the exit code.


36-43: LGTM!

The function is well-structured with proper argument parsing, error handling, and type annotations.


1-7: LGTM!

The imports are appropriate, and defining the pattern as a constant follows best practices.

🧰 Tools
🪛 GitHub Actions: Pull request workflow

[error] 1-1: Black formatting check failed. 1 file would be reformatted. Run 'black' to fix code style issues in this file.


36-43: LGTM!

The main function is well-structured with proper type annotations and argument parsing.

.github/workflows/pull-request.yml (4)

51-79: LGTM!

The python_checks job effectively consolidates Python checks into a single job, improving workflow efficiency. The job correctly:

  • Runs all three checks (biome ignore, code coverage disable, and ts ignore)
  • Uses the changed files output from the changed-files action
  • Maintains proper step ordering and dependencies

51-79: LGTM!

The job is well-structured and correctly consolidates all Python checks into a single job. The steps are properly ordered and use the correct Python version.


51-79: LGTM!

The consolidated python_checks job is well-structured and includes all necessary steps for running Python-related checks.


185-185: LGTM!

The job dependency has been correctly updated to use the new consolidated python_checks job.

coderabbitai[bot]
coderabbitai bot previously approved these changes Feb 19, 2025
@palisadoes
Copy link
Contributor

Run the python checks in your local branch before adding more commits.

@shivasankaran18
Copy link
Author

implemented the changes @palisadoes

@palisadoes
Copy link
Contributor

palisadoes commented Feb 20, 2025

  1. Please make coderabbit.ai approves your work.
  2. Make sure all tests pass and are valid.

Copy link

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🔭 Outside diff range comments (1)
.github/workflows/pull-request.yml (1)

51-79: 🧹 Nitpick (assertive)

Add job documentation and timeout.

Consider these improvements:

  1. Add comments to explain the job's purpose
  2. Add a timeout to prevent long-running checks

Apply this diff:

   python_checks:
+    # Job to run various Python-based checks:
+    # - Biome ignore check
+    # - Code coverage disable check
+    # - TypeScript ignore check
     name: Run Python Checks
     runs-on: ubuntu-latest
+    timeout-minutes: 5
     steps:
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 939710b and cefd5cf.

📒 Files selected for processing (2)
  • .github/workflows/pull-request.yml (3 hunks)
  • .github/workflows/scripts/detect_ts_ignore.py (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
.github/workflows/scripts/detect_ts_ignore.py (1)
Learnt from: shivasankaran18
PR: PalisadoesFoundation/talawa-api#3246
File: .github/workflows/scripts/detect_ts_ignore.py:25-25
Timestamp: 2025-02-18T17:15:18.046Z
Learning: In Python 3, `IOError` is an alias for `OSError`, so using just `OSError` in except clauses is preferred for cleaner code.
🪛 Ruff (0.8.2)
.github/workflows/scripts/detect_ts_ignore.py

29-29: Trailing comma missing

Add trailing comma

(COM812)


56-56: Trailing comma missing

Add trailing comma

(COM812)


59-59: Trailing comma missing

Add trailing comma

(COM812)

⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Run tests for talawa api
  • GitHub Check: Analyse Code With CodeQL (typescript)
🔇 Additional comments (2)
.github/workflows/scripts/detect_ts_ignore.py (1)

1-8: 🧹 Nitpick (assertive)

Add trailing comma to improve maintainability.

The regex pattern constant could benefit from a trailing comma for better git diffs when the pattern needs to be extended.

Apply this diff:

-TS_IGNORE_PATTERN = r"(?://|/\*)\s*@ts-ignore\b"
+TS_IGNORE_PATTERN = r"(?://|/\*)\s*@ts-ignore\b",

Likely an incorrect or invalid review comment.

.github/workflows/pull-request.yml (1)

185-185: LGTM! Job dependencies updated correctly.

The Run-Tests job now correctly depends on the consolidated python_checks job.

Copy link

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 5

♻️ Duplicate comments (1)
.github/workflows/scripts/detect_ts_ignore.py (1)

81-81: ⚠️ Potential issue

Fix critical bug in file handling.

The script filters TypeScript files but then uses the unfiltered list, which could process non-TypeScript files.

-    exit_code = check_ts_ignore(args.files)
+    exit_code = check_ts_ignore(ts_files)
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cefd5cf and 9adebf8.

📒 Files selected for processing (1)
  • .github/workflows/scripts/detect_ts_ignore.py (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
.github/workflows/scripts/detect_ts_ignore.py (1)
Learnt from: shivasankaran18
PR: PalisadoesFoundation/talawa-api#3246
File: .github/workflows/scripts/detect_ts_ignore.py:25-25
Timestamp: 2025-02-18T17:15:18.046Z
Learning: In Python 3, `IOError` is an alias for `OSError`, so using just `OSError` in except clauses is preferred for cleaner code.
🪛 Ruff (0.8.2)
.github/workflows/scripts/detect_ts_ignore.py

29-29: Logging statement uses f-string

(G004)


34-34: Trailing comma missing

Add trailing comma

(COM812)


38-38: Trailing comma missing

Add trailing comma

(COM812)


41-41: Logging statement uses f-string

(G004)


41-41: Trailing comma missing

Add trailing comma

(COM812)


45-45: Logging statement uses f-string

(G004)


47-47: Use logging.exception instead of logging.error

Replace with exception

(TRY400)


47-47: Logging statement uses f-string

(G004)


68-68: Trailing comma missing

Add trailing comma

(COM812)


71-71: Trailing comma missing

Add trailing comma

(COM812)

⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Run tests for talawa api
  • GitHub Check: Analyse Code With CodeQL (typescript)
🔇 Additional comments (2)
.github/workflows/scripts/detect_ts_ignore.py (2)

85-86: LGTM!

The entry point is correctly implemented following Python best practices.


10-13: 🧹 Nitpick (assertive)

Add trailing comma for better git diffs.

Adding trailing commas helps with cleaner git diffs when adding new configuration options.

 logging.basicConfig(
     level=logging.INFO,
-    format="%(levelname)s: %(message)s",
+    format="%(levelname)s: %(message)s",
 )

Likely an incorrect or invalid review comment.

Copy link

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

♻️ Duplicate comments (1)
.github/workflows/scripts/detect_ts_ignore.py (1)

87-87: ⚠️ Potential issue

Fix: Use filtered TypeScript files.

The script is using unfiltered files instead of the filtered TypeScript files.

-    exit_code = check_ts_ignore(args.files)
+    exit_code = check_ts_ignore(ts_files)
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9adebf8 and f02db61.

📒 Files selected for processing (1)
  • .github/workflows/scripts/detect_ts_ignore.py (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
.github/workflows/scripts/detect_ts_ignore.py (1)
Learnt from: shivasankaran18
PR: PalisadoesFoundation/talawa-api#3246
File: .github/workflows/scripts/detect_ts_ignore.py:25-25
Timestamp: 2025-02-18T17:15:18.046Z
Learning: In Python 3, `IOError` is an alias for `OSError`, so using just `OSError` in except clauses is preferred for cleaner code.
🪛 Ruff (0.8.2)
.github/workflows/scripts/detect_ts_ignore.py

31-31: Logging statement uses f-string

(G004)


41-41: Trailing comma missing

Add trailing comma

(COM812)


44-44: Logging statement uses f-string

(G004)


44-44: Trailing comma missing

Add trailing comma

(COM812)


48-48: Logging statement uses f-string

(G004)


50-50: Logging statement uses f-string

(G004)


50-50: Redundant exception object included in logging.exception call

(TRY401)

⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Run tests for talawa api
  • GitHub Check: Analyse Code With CodeQL (typescript)
🔇 Additional comments (2)
.github/workflows/scripts/detect_ts_ignore.py (2)

1-15: LGTM! Well-structured file setup.

The file setup is clean and follows best practices:

  • Proper shebang line
  • Clear module docstring
  • Organized imports
  • Appropriate logging configuration
  • Well-defined regex pattern constant

91-92: LGTM! Standard entry point pattern.

The entry point follows the standard Python pattern for script execution.

Copy link

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

@shivasankaran18
Copy link
Author

@palisadoes could you review the PR .? .. improved the code quality of the script

@palisadoes
Copy link
Contributor

Please test with files that have all the ts-ignore variants that the script is supposed to test and notify me.

@palisadoes palisadoes added the ignore-sensitive-files-pr The contributor has a legitimate reason for editiing protected files label Feb 20, 2025
@shivasankaran18
Copy link
Author

yeah ok @palisadoes ..will do

@shivasankaran18
Copy link
Author

shivasankaran18 commented Feb 20, 2025

Screenshot 2025-02-20 122623
@palisadoes ran the script for checking all the files in the repo.. do we need to avoid the checking of files in the node_modules too?

@palisadoes
Copy link
Contributor

  1. Not in node_modules.
  2. Please fix that file.

@shivasankaran18
Copy link
Author

yeah @palisadoes ... this now currently does not check node_modules as they are not committed to git .. I just asked to ensure should I add that check too .. this for now looks great

@shivasankaran18
Copy link
Author

@palisadoes could you review this PR..?

@palisadoes palisadoes merged commit d188f2d into PalisadoesFoundation:develop-postgres Feb 22, 2025
15 of 17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ignore-sensitive-files-pr The contributor has a legitimate reason for editiing protected files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants