Refacted: src/setup/askForTalawaApiUrl/askForTalawaApiUrl.test.ts from Jest to Vitest

[aryanrule]

What kind of change does this PR introduce?
Refracting src/setup/askForTalawaApiUrl/askForTalawaApiUrl.test.ts from Jest to Vitest

Issue number :
Fixes #2749

Did you add tests for your changes?
Yes

Snapshots/Videos:

If relevant, did you update the documentation?

Does this PR introduce a breaking change?

No

Other information

No

Have you read the contributing guide?

Yes

Summary by CodeRabbit

Based on the comprehensive changes, here are the release notes:

• New Features

  • Added comprehensive localization support for English, French, Spanish, Hindi, and Chinese
  • Introduced new configuration files for build and testing environments
  • Enhanced GitHub Actions workflows for improved CI/CD processes

• Documentation

  • Updated README with new project guidelines
  • Added detailed installation and contribution guidelines
  • Introduced new documentation structure and references

• Improvements

  • Upgraded project dependencies and tooling
  • Implemented stricter linting and code quality checks
  • Enhanced error handling and user experience

• Localization

  • Added multi-language support with translations for common UI elements
  • Implemented internationalization framework

• Testing

  • Added comprehensive test configurations
  • Introduced mock implementations for testing
  • Enhanced test coverage and quality checks

[coderabbitai]

Walkthrough

This pull request introduces comprehensive changes to the Talawa Admin project, focusing on configuration, localization, testing infrastructure, and development workflows. The modifications span multiple areas including environment setup, GitHub Actions workflows, linting configurations, localization files, and testing frameworks. The changes aim to enhance code quality, improve developer experience, and provide multi-language support for the application.

Changes

File/Directory	Change Summary
.coderabbit.yaml	New configuration file for YAML language server with review and chat settings
.env.example	Added environment variables for Talawa Admin configuration
.eslintignore, .eslintrc.json	Updated linting configurations and added new rules
.github/workflows/	Introduced new workflows for CI/CD, code quality checks, and issue management
config/	Added Babel and Vite configuration files
public/locales/	Added localization files for English, French, Hindi, Spanish, and Chinese
scripts/	Introduced new utility scripts for testing, Git hooks, and environment setup
setup.ts	New script for interactive environment configuration

Assessment against linked issues

Objective	Addressed	Explanation
Refactor askForTalawaApiUrl.test.ts to Vitest	❓	No direct evidence of this specific test file's migration in this PR

Possibly related PRs

• Refactor : src/components/CheckIn/CheckInWrapper.test.tsx from Jest to Vitest #2709: Refactoring tests from Jest to Vitest
• Updated pr template with checklist #2454: Updating pull request template for CodeRabbit AI review
• Added GitHub PR Workflow Check: Talawa Admin app starts (No Docker) #2452: Workflow check for Talawa Admin app startup

Suggested reviewers

• @palisadoes
• @varshith257

Poem

🐰 A Rabbit's Code Odyssey 🌈

Configuration dancing, workflows sing,
Locales bloom in languages' wing,
Linting rules sharp, tests running bright,
Talawa Admin takes its coding flight!

Hop, hop, hooray! 🚀

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.95%. Comparing base (2e18c32) to head (b3149ba).

Additional details and impacted files

@@                  Coverage Diff                  @@
##           develop-postgres    #3053       +/-   ##
=====================================================
+ Coverage             29.13%   88.95%   +59.81%     
=====================================================
  Files                   300      321       +21     
  Lines                  7568     8409      +841     
  Branches               1652     1894      +242     
=====================================================
+ Hits                   2205     7480     +5275     
+ Misses                 5177      686     -4491     
- Partials                186      243       +57     

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

[palisadoes]

The test failure cause is that you have not merged your code with the latest upstream. In this case, merge your local branch with the latest upstream, commit and then push to your origin.

[aryanrule]

sir , do i need to merge develop-postgres in my branch and then pushing my branch to the origin ?

[palisadoes]

Please merge your local branch with the latest upstream, commit and then push to your origin. The tests should pass then

[coderabbitai]

Actionable comments posted: 29

🧹 Nitpick comments (52)

.github/workflows/stale.yml (2)

1-11: Consider enhancing the header documentation

The header references a README.md file but doesn't provide immediate context about the workflow's purpose. Consider adding a brief description of the workflow's functionality directly in the header for better maintainability.

 ##############################################################################
 ##############################################################################
 #
 # NOTE!
 #
 # Please read the README.md file in this directory that defines what should 
 # be placed in this file
+# Purpose: This workflow automatically manages stale issues and pull requests
+# by marking them as stale after 10 days of inactivity and closing them
+# after 180 days of inactivity.
 #
 ##############################################################################
 ##############################################################################

🧰 Tools

🪛 yamllint (1.35.1)

[error] 6-6: trailing spaces

(trailing-spaces)

---

18-21: Remove trailing spaces

The permissions configuration is correct, but there are trailing spaces that should be removed.

 permissions:
   issues: write
-  pull-requests: write  
-  
+  pull-requests: write

🧰 Tools

🪛 yamllint (1.35.1)

[error] 20-20: trailing spaces

(trailing-spaces)

---

[error] 21-21: trailing spaces

(trailing-spaces)

public/locales/en/errors.json (3)

2-2: Fix double punctuation in error message

The message has both "!" and "." at the end which is redundant.

-  "talawaApiUnavailable": "Talawa-API service is unavailable!. Is it running? Check your network connectivity too.",
+  "talawaApiUnavailable": "Talawa-API service is unavailable! Is it running? Check your network connectivity too.",

---

5-5: Fix capitalization in error message

"Authorised" should not be capitalized in the middle of a sentence.

-  "notAuthorised": "Sorry! you are not Authorised!",
+  "notAuthorised": "Sorry! You are not authorised!",

---

10-10: Fix typo in error message

"occured" should be "occurred".

-  "errorLoading": "Error occured while loading {{entity}} data"
+  "errorLoading": "Error occurred while loading {{entity}} data"

public/locales/en/translation.json (1)

14-88: Consider consolidating duplicate translations

The loginPage and userLoginPage sections contain many identical translations. Consider creating a common section for shared translations to improve maintainability and reduce duplication.

Example of duplicated strings:

• "atleast_8_char_long"
• "Password_and_Confirm_password_mismatches"
• "captchaError"
  And many more...

Also applies to: 57-88

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

1-77: Clean up trailing spaces

Multiple lines contain trailing spaces. While this doesn't affect functionality, it's good practice to remove them for consistency.

Use your editor's trailing space removal feature or run the following command:

sed -i 's/[[:space:]]*$//' .github/workflows/pull-request-target.yml

🧰 Tools

🪛 yamllint (1.35.1)

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 13-13: trailing spaces

(trailing-spaces)

---

[error] 15-15: trailing spaces

(trailing-spaces)

---

[error] 27-27: trailing spaces

(trailing-spaces)

---

[error] 28-28: trailing spaces

(trailing-spaces)

---

[error] 29-29: trailing spaces

(trailing-spaces)

---

[error] 31-31: trailing spaces

(trailing-spaces)

---

[error] 33-33: trailing spaces

(trailing-spaces)

---

[error] 34-34: trailing spaces

(trailing-spaces)

---

[error] 36-36: trailing spaces

(trailing-spaces)

---

[error] 41-41: trailing spaces

(trailing-spaces)

---

[error] 46-46: trailing spaces

(trailing-spaces)

---

[error] 71-71: trailing spaces

(trailing-spaces)

scripts/githooks/check-localstorage-usage.js (1)

87-93: Use trailing commas if your lint/prettier config requires them.

Your static-analysis hints suggest adding trailing commas at lines 89 and 92. This is likely a code-style preference from your Prettier configuration. If you adopt trailing commas, you can fix it by adding a comma before the closing parenthesis.

 console.info(
   '\x1b[34m%s\x1b[0m',
-  '\nInfo: Consider using custom hook functions.'
+  '\nInfo: Consider using custom hook functions.',
 );
 console.info(
   'Please use the getItem, setItem, and removeItem functions provided by the custom hook useLocalStorage.\n'
-);
+);

🧰 Tools

🪛 eslint

[error] 89-89: Insert ,

(prettier/prettier)

---

[error] 92-92: Insert ,

(prettier/prettier)

schema.graphql (5)

32-41: Add validation for Address fields.

The Address type and its input should include validation for postal codes and country codes.

 type Address {
   city: String
-  countryCode: String
+  countryCode: CountryCode!
   dependentLocality: String
   line1: String
   line2: String
-  postalCode: String
+  postalCode: String @constraint(
+    pattern: "^[0-9A-Z]{3,10}$"
+  )
   sortingCode: String
   state: String
 }

Also applies to: 43-52

---

915-930: Add moderation capabilities to Post type.

Posts should include moderation status and reporting functionality.

 type Post {
   # ... existing fields ...
+  moderationStatus: ModerationStatus!
+  reports: [Report!]
   updatedAt: DateTime!
 }

+enum ModerationStatus {
+  APPROVED
+  PENDING
+  REJECTED
+  FLAGGED
+}

+type Report {
+  _id: ID!
+  reporter: User!
+  reason: String!
+  createdAt: DateTime!
+}

---

861-876: Standardize pagination implementation.

The schema uses different pagination patterns (offset-based and cursor-based). Standardize on cursor-based pagination for better scalability.

Use the ConnectionPageInfo type consistently across all paginated queries instead of mixing with PageInfo.

Also applies to: 1433-1436

---

103-103: Add descriptions for scalar types.

Scalar types lack descriptions explaining their format and validation rules.

Add descriptions for all scalar types, for example:

-scalar DateTime
+"""
+An ISO-8601 encoded UTC date string.
+Format: YYYY-MM-DDTHH:mm:ss.sssZ
+"""
+scalar DateTime

Also applies to: 209-209, 211-211, 263-263, 459-459, 883-883, 913-913, 1119-1119, 1138-1138, 1292-1292

---

1449-1454: Standardize enum naming conventions.

The UserType enum uses inconsistent naming patterns. Consider using snake_case for all enum values.

 enum UserType {
-  ADMIN
-  NON_USER
-  SUPERADMIN
-  USER
+  ADMIN_USER
+  NON_USER
+  SUPER_ADMIN
+  REGULAR_USER
 }

public/locales/hi/common.json (3)

9-10: Consider differentiating between singular and plural forms of "admin"

The same word "व्यवस्थापक" is used for both "admin" and "admins". Consider using "व्यवस्थापकगण" for the plural form to better distinguish between singular and plural.

---

79-79: Review placeholder positioning for better Hindi readability

In Hindi, the natural sentence structure might be different from English. Consider:

1. For "searchResultsFor": Move "के लिए" before {{text}} for better flow
2. For success messages: Move {{item}} to the beginning of the sentence

Example improvements:

- "searchResultsFor": "{{text}} के लिए खोज परिणाम",
+ "searchResultsFor": "के लिए {{text}} खोज परिणाम",

- "addedSuccessfully": "{{item}} सफलतापूर्वक जोड़ा गया",
+ "addedSuccessfully": "{{item}} को सफलतापूर्वक जोड़ा गया",

Also applies to: 83-85

---

86-87: Consider shorter translations for session messages

The current translations, while accurate, are quite lengthy. Consider more concise versions while maintaining clarity:

- "sessionWarning": "आपका सत्र निष्क्रियता के कारण जल्द ही समाप्त हो जाएगा। कृपया अपने सत्र को बढ़ाने के लिए पृष्ठ के साथ बातचीत करें।",
+ "sessionWarning": "निष्क्रियता के कारण सत्र समाप्त होने वाला है। कृपया पृष्ठ का उपयोग जारी रखें।",

- "sessionLogOut": "निष्क्रियता के कारण आपका सत्र समाप्त हो गया है। कृपया जारी रखने के लिए पुनः लॉगिन करें।",
+ "sessionLogOut": "सत्र समाप्त। कृपया पुनः लॉगिन करें।",

.husky/post-merge (1)

4-4: Consider more robust error handling for npm install.
If npm install fails, the hook will continue, potentially causing an inconsistent local environment. You might want to check the exit status of npm install and abort the merge if the installation fails.

 git diff HEAD^ HEAD --exit-code -- ./package.json || npm install
+if [ $? -ne 0 ]; then
+  echo "npm install encountered an error. Please fix and re-run."
+  exit 1
+fi

.husky/pre-commit (2)

5-5: Clarify whether lint fixes should run automatically.
You’ve commented out npm run lint:fix. If you do want to auto-fix lint errors on commit, uncomment it. Otherwise, it might be best to remove it for clarity.

-# npm run lint:fix
+npm run lint:fix

---

10-10: Avoid staging all changes automatically.
Running git add . can stage changes not previously staged. Consider only re-staging the files fixed by these commands to avoid unintended commits.

- git add .
+ # Consider limiting to staged files only, e.g.:
+ git add $(git diff --name-only --staged)

scripts/githooks/update-toc.js (1)

11-12: Remove extra blank line to comply with Prettier rules.
Prettier flags the blank line as an unnecessary whitespace. Removing it helps maintain a consistent code style.

execSync(command, { stdio: 'inherit' });

- 
});
+});

🧰 Tools

🪛 eslint

[error] 11-12: Delete ··⏎

(prettier/prettier)

scripts/custom-test-env.js (2)

5-5: Define a valid tag for @pdfme or remove it.
Your TSDoc configuration may not recognize the @pdfme tag. If you need a custom tag, configure it in your TSDoc settings; otherwise, remove or replace it.

🧰 Tools

🪛 eslint

[error] 5-5: tsdoc-undefined-tag: The TSDoc tag "@pdfme" is not defined in this configuration

(tsdoc/syntax)

---

9-15: Add an explicit return type for setup().
TypeScript rules recommend explicit return types, especially for overriden methods.

 export default class CustomTestEnvironment extends Environment {
-  async setup() {
+  async setup(): Promise<void> {
     await super.setup();
     if (typeof this.global.TextEncoder === 'undefined') {
       this.global.TextEncoder = TextEncoder;
       this.global.TextDecoder = TextDecoder;
     }
   }
 }

🧰 Tools

🪛 eslint

[error] 9-9: Missing return type on function.

(@typescript-eslint/explicit-function-return-type)

---

[error] 9-9: Missing return type on function.

(@typescript-eslint/explicit-module-boundary-types)

config/vite.config.ts (1)

27-28: Correct the misleading comment about the port.
The comment suggests a default port of 3000, but the code sets it to 4321. Updating the comment clarifies the intended port for future maintainers.

-// this sets a default port to 3000
+// this sets a default port to 4321

scripts/__mocks__/@pdfme/generator.ts (2)

3-13: Validate template and inputs more comprehensively.
Currently, the code only checks if template.schemas.length and inputs.length are zero. Consider validating for undefined or null values before checking lengths.

 if (!template || !template.schemas || template.schemas.length === 0 ||
     !inputs || inputs.length === 0) {
   throw new Error('Template or inputs cannot be empty.');
 }

---

10-13: Log the validation error for debugging.
Adding a more descriptive log message can help when diagnosing PDF generation issues.

 } catch (err) {
   console.error('Error generating mock PDF:', err);
   throw err;
 }

.github/workflows/check-tsdoc.js (2)

14-35: Improve error handling for directory traversal.
Consider terminating the script after logging the directory read error, or re-throwing it. This will prevent silent failures if the script cannot read the directory.

} catch (err) {
  console.error(`Error reading directory ${dir}: ${err.message}`);
+ process.exit(1);
}

---

37-46: Refine the TSDoc detection logic.
The current regex checks for any /** comment, but it may match comments that are not necessarily structured as TSDoc. You could refine the pattern to detect TSDoc tags or placeholders for more accurate results.

.github/workflows/talawa_admin_md_mdx_format_adjuster.py (1)

39-44: Consider memory usage for large files.

While reading the entire file into memory can be convenient for smaller files, it might be inefficient for extremely large Markdown files. If your repository holds potentially large documentation, consider a streaming approach to parse and process the files in chunks.

.github/workflows/eslint_disable_check.py (1)

61-61: Rename unused variable to underscore for clarity.

The dirs variable is not used inside the loop. Renaming it to _dirs helps convey that it's intentionally unused, improving code readability:

-for root, dirs, files in os.walk(os.path.join(directory, 'src')):
+for root, _dirs, files in os.walk(os.path.join(directory, 'src')):

🧰 Tools

🪛 Ruff (0.8.2)

61-61: Loop control variable dirs not used within loop body

Rename unused dirs to _dirs

(B007)

setup.ts (1)

87-95: Consider edge cases when updating WebSocket URLs.

Replacing http(s):// with ws(s):// is straightforward, but consider edge cases where endpoints might have unusual prefixes. Also, ensure you handle trailing slashes or query parameters consistently.

.github/workflows/compare_translations.py (1)

135-135: Raise exceptions with cause
Consider raising a chained exception using raise ValueError(...) from e to preserve the original stack trace context and distinguish decoding issues from higher-level exceptions.

🧰 Tools

🪛 Ruff (0.8.2)

135-135: Within an except clause, raise exceptions with raise ... from err or raise ... from None to distinguish them from errors in exception handling

(B904)

.github/workflows/countline.py (1)

246-264: Potential improvement for multi-line or block comments
Currently, only lines starting with # or / are skipped. If your repository uses multi-line comments (e.g., /* ... */ in some languages), you may want to enhance comment detection to avoid miscounting lines.

.github/ISSUE_TEMPLATE/feature-request.md (1)

25-28: Replace bare URL with a markdown link
To address Markdownlint’s “no-bare-urls” rule, embed the link in markdown, for example:

[Potential internship candidates](https://github.com/PalisadoesFoundation/talawa/issues/359)

🧰 Tools

🪛 Markdownlint (0.37.0)

28-28: null
Bare URL used

(MD034, no-bare-urls)

---

25-25: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

.github/workflows/codeql-codescan.yml (1)

17-17: Fix YAML formatting issues.

There are some minor YAML formatting inconsistencies:

• Trailing spaces
• Indentation mismatches

Apply these changes:

• Remove trailing spaces after '**'
• Fix indentation to use consistent spacing (6 spaces for steps, 11 spaces for action parameters)

Also applies to: 20-20, 31-31, 37-37

🧰 Tools

🪛 yamllint (1.35.1)

[error] 17-17: trailing spaces

(trailing-spaces)

.github/pull_request_template.md (2)

22-25: Enhance issue reference section formatting.

Consider making the issue reference format more explicit to ensure consistent linking.

-**Issue Number:**
-
-Fixes #<!--Add related issue number here.-->
+**Issue Number:** (Required)
+
+Fixes #<!--Add issue number (e.g., Fixes #123)-->

---

28-33: Clarify test requirements section.

The test section could be more specific about expectations.

-<!--Yes or No. Note: Add unit tests or automation tests for your code.-->
+<!--
+Answer: Yes/No
+
+If Yes: Describe which tests were added
+If No: Explain why tests are not needed
+-->
-<!--Add snapshots or videos wherever possible.-->
+<!--Add snapshots/videos demonstrating the changes (if applicable)-->

DOCUMENTATION.md (3)

24-26: Fix grammar and URL formatting.

There are some grammar and formatting issues in the Docusaurus section.

-    - A local version of `docs.talawa.io` should automatically launched in your browser at http://localhost:3000/
+    - A local version of `docs.talawa.io` should automatically launch in your browser at `http://localhost:3000`

🧰 Tools

🪛 LanguageTool

[grammar] ~25-~25: The modal verb ‘should’ requires the verb’s base form.
Context: ...f docs.talawa.io should automatically launched in your browser at http://localhost:300...

(MD_BASEFORM)

---

[grammar] ~26-~26: Did you mean the formatting language “Markdown” (= proper noun)?
Context: ...ttp://localhost:3000/ 1. Add/modify the markdown documents to the docs/ directory of t...

(MARKDOWN_NNP)

🪛 Markdownlint (0.37.0)

25-25: null
Bare URL used

(MD034, no-bare-urls)

---

26-29: Improve Markdown formatting consistency.

Ensure consistent capitalization and formatting for technical terms.

-1. Add/modify the markdown documents to the `docs/` directory of the `talawa-docs` repository
+1. Add/modify the Markdown documents to the `docs/` directory of the `talawa-docs` repository
-1. Always monitor the local website in your brower to make sure the changes are acceptable. 
+1. Always monitor the local website in your browser to make sure the changes are acceptable.

🧰 Tools

🪛 LanguageTool

[grammar] ~26-~26: Did you mean the formatting language “Markdown” (= proper noun)?
Context: ...ttp://localhost:3000/ 1. Add/modify the markdown documents to the docs/ directory of t...

(MARKDOWN_NNP)

---

31-32: Refine repository reference.

The final directive could be more specific.

-***PLEASE*** do not add markdown files in this repository. Add them to `talawa-docs`!
+***IMPORTANT:*** Do not add Markdown files to this repository. Add all documentation to the [`talawa-docs`](https://github.com/PalisadoesFoundation/talawa-docs) repository instead.

🧰 Tools

🪛 LanguageTool

[uncategorized] ~32-~32: The preposition “to” seems more likely in this position.
Context: ... PLEASE do not add markdown files in this repository. Add them to `talawa-do...

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)

.github/workflows/README.md (2)

24-24: Fix typo in documentation

There's a duplicate "to" in the sentence.

-      1. Place all actions related to to this in the `pull-request-target.yml` file.
+      1. Place all actions related to this in the `pull-request-target.yml` file.

🧰 Tools

🪛 LanguageTool

[duplication] ~24-~24: Possible typo: you repeated a word
Context: ...ors: 1. Place all actions related to to this in the pull-request-target.yml f...

(ENGLISH_WORD_REPEAT_RULE)

---

35-35: Fix abbreviation format

The abbreviation "eg." should be "e.g." (with periods).

-1. Jobs only work correctly if they have a dedicated file (eg. `CodeQL`)
+1. Jobs only work correctly if they have a dedicated file (e.g., `CodeQL`)

🧰 Tools

🪛 LanguageTool

[uncategorized] ~35-~35: The abbreviation “e.g.” (= for example) requires two periods.
Context: ...orrectly if they have a dedicated file (eg. CodeQL) ## Scripts Follow these gui...

(E_G)

.github/workflows/issue.yml (1)

34-55: Optimize label management logic

The current implementation has redundant object creation and could be simplified.

-            const { owner, repo } = context.repo;
-            const issue_number = context.issue.number;
-            const apiParams = {
-              owner,
-              repo,
-              issue_number
-            };
-            const labels = await github.rest.issues.listLabelsOnIssue(apiParams);
+            const labels = await github.rest.issues.listLabelsOnIssue({
+              ...context.repo,
+              issue_number: context.issue.number
+            });
             if(labels.data.reduce((a, c)=>a||["dependencies"].includes(c.name), false))
               await github.rest.issues.addLabels({
-                owner: context.repo.owner,
-                repo: context.repo.repo,
-                issue_number: context.issue.number,
+                ...context.repo,
+                issue_number: context.issue.number,
                 labels: ["good first issue", "security"]
               });
             else if(labels.data.reduce((a, c)=>a||["security", "ui/ux"].includes(c.name), false))
               await github.rest.issues.addLabels({
-                owner: context.repo.owner,
-                repo: context.repo.repo,
-                issue_number: context.issue.number,
+                ...context.repo,
+                issue_number: context.issue.number,
                 labels: ["good first issue"]
               });

ISSUE_GUIDELINES.md (3)

5-5: Fix grammatical error in the introduction

There's a grammatical error in the sentence structure.

-In order to give everyone a chance to submit a issues reports and contribute to the Talawa project
+In order to give everyone a chance to submit issue reports and contribute to the Talawa project

🧰 Tools

🪛 LanguageTool

[misspelling] ~5-~5: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ...der to give everyone a chance to submit a issues reports and contribute to the Ta...

(EN_A_VS_AN)

---

29-29: Fix typo in the search instructions

The sentence contains a duplicated word and incorrect punctuation.

-Your issue may have already been created. Search for duplicate open issues before submitting yours.for similar deficiencies in the code.duplicate issues are created.
+Your issue may have already been created. Search for duplicate open issues before submitting yours for similar deficiencies in the code.

---

44-44: Capitalize "Slack" in channel references

"Slack" is a proper noun and should be capitalized.

-Ask our contributors to assign it to you in `#talawa` slack channel.
+Ask our contributors to assign it to you in `#talawa` Slack channel.
-Join our `#talawa-github` slack channel for automatic issue and pull request updates.
+Join our `#talawa-github` Slack channel for automatic issue and pull request updates.
-Discuss issues in our various slack channels when necessary
+Discuss issues in our various Slack channels when necessary

Also applies to: 53-53, 57-57

🧰 Tools

🪛 LanguageTool

[grammar] ~44-~44: Did you mean the communication tool “Slack” (= proper noun, capitalized)?
Context: ...butors to assign it to you in #talawa slack channel. Working on these types of exi...

(ON_SKYPE)

README.md (1)

53-53: Fix markdown heading formatting

Remove extra space after the hash symbol in the heading.

-#  Videos
+# Videos

🧰 Tools

🪛 Markdownlint (0.37.0)

53-53: null
Multiple spaces after hash on atx style heading

(MD019, no-multiple-space-atx)

.eslintrc.json (1)

14-16: Simplify ESLint configuration extends

The configuration can be simplified by removing redundant extends:

• eslint-config-prettier and prettier serve the same purpose
• Having both might cause conflicts

  "extends": [
    "plugin:react/recommended",
    "eslint:recommended",
    "plugin:jest/recommended",
    "plugin:prettier/recommended",
    "plugin:@typescript-eslint/recommended",
-   "eslint-config-prettier",
-   "prettier"
  ],

PR_GUIDELINES.md (1)

31-34: Add language specifiers to code blocks

Code blocks should specify the language for proper syntax highlighting.

Update the code blocks to include language specifiers:

-```
+```bash
npm run lint:fix
npm run format:fix

- +bash
npm run lint:check
npm run format:check

Also applies to: 39-42

🧰 Tools

🪛 Markdownlint (0.37.0)

31-31: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

CODE_STYLE.md (2)

58-62: Add language specifiers to code blocks

Code blocks should specify the language for proper syntax highlighting.

Update the code blocks to include language specifiers:

-```
+```jsx
<div className="myCustomClass">...</div>

- +jsx

...

```

- +jsx

Dropdown button

...

-```
+```tsx
import Dropdown from 'react-bootstrap/Dropdown';
...

Also applies to: 64-69, 78-89, 95-115

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 Markdownlint (0.37.0)</summary>

58-58: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

</details>

</details>

---

`239-241`: **Add language specifiers to Sass compilation commands**

The Sass compilation command blocks should specify the shell language.

Update the code blocks:

```diff
-```
+```bash
npx sass src/assets/scss/app.scss src/assets/css/app.css

- +bash
npx sass src/assets/scss/app.scss src/assets/css/app.css --watch

-```
+```bash
npx sass --no-source-map src/assets/scss/app.scss src/assets/css/app.css

Also applies to: 245-247, 251-253

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 Markdownlint (0.37.0)</summary>

239-239: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

</details>

</details>

</blockquote></details>
<details>
<summary>.github/workflows/pull-request.yml (1)</summary><blockquote>

`253-254`: **Consider using a more specific glob pattern**

While the GraphQL validation is good, the glob pattern could be more specific to target only files with GraphQL operations.

Consider this change:

```diff
- graphql-inspector validate './src/GraphQl/**/*.ts' './talawa-api/schema.graphql'
+ graphql-inspector validate './src/GraphQl/**/*{Query,Mutation,Fragment,Subscription}.ts' './talawa-api/schema.graphql'

.github/ISSUE_TEMPLATE/bug-report.md (1)

33-36: Improve markdown formatting

The internship section needs formatting improvements:

1. Use proper heading syntax instead of bold text
2. Format URL as a markdown link

Apply these changes:

-**Potential internship candidates**
+## Potential internship candidates
 
 Please read this if you are planning to apply for a Palisadoes Foundation internship 
-https://github.com/PalisadoesFoundation/talawa/issues/359
+[Internship Information](https://github.com/PalisadoesFoundation/talawa/issues/359)

🧰 Tools

🪛 Markdownlint (0.37.0)

36-36: null
Bare URL used

(MD034, no-bare-urls)

---

33-33: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1453368 and 3d1f1f0.

⛔ Files ignored due to path filters (75)

• package-lock.json is excluded by !**/package-lock.json
• public/favicon.ico is excluded by !**/*.ico
• public/favicon_palisadoes.ico is excluded by !**/*.ico
• public/images/logo512.png is excluded by !**/*.png
• public/images/svg/angleDown.svg is excluded by !**/*.svg
• public/images/svg/arrow-left.svg is excluded by !**/*.svg
• public/images/svg/arrow-right.svg is excluded by !**/*.svg
• public/images/svg/attendees.svg is excluded by !**/*.svg
• public/images/svg/feedback.svg is excluded by !**/*.svg
• public/images/svg/profiledefault.svg is excluded by !**/*.svg
• public/images/svg/up-down.svg is excluded by !**/*.svg
• public/logo192.png is excluded by !**/*.png
• public/markdown/images/install1.png is excluded by !**/*.png
• public/markdown/images/install2.png is excluded by !**/*.png
• src/assets/css/app.css.map is excluded by !**/*.map
• src/assets/images/blank.png is excluded by !**/*.png
• src/assets/images/bronze.png is excluded by !**/*.png
• src/assets/images/defaultImg.png is excluded by !**/*.png
• src/assets/images/gold.png is excluded by !**/*.png
• src/assets/images/palisadoes_logo.png is excluded by !**/*.png
• src/assets/images/silver.png is excluded by !**/*.png
• src/assets/images/talawa-logo-600x600.png is excluded by !**/*.png
• src/assets/images/talawa-logo-dark-200x200.png is excluded by !**/*.png
• src/assets/images/talawa-logo-lite-200x200.png is excluded by !**/*.png
• src/assets/svgs/Attendance.svg is excluded by !**/*.svg
• src/assets/svgs/actionItem.svg is excluded by !**/*.svg
• src/assets/svgs/admin.svg is excluded by !**/*.svg
• src/assets/svgs/agenda-category-icon.svg is excluded by !**/*.svg
• src/assets/svgs/agenda-items.svg is excluded by !**/*.svg
• src/assets/svgs/angleRight.svg is excluded by !**/*.svg
• src/assets/svgs/article.svg is excluded by !**/*.svg
• src/assets/svgs/blockUser.svg is excluded by !**/*.svg
• src/assets/svgs/blockedUser.svg is excluded by !**/*.svg
• src/assets/svgs/cardItemDate.svg is excluded by !**/*.svg
• src/assets/svgs/cardItemEvent.svg is excluded by !**/*.svg
• src/assets/svgs/cardItemLocation.svg is excluded by !**/*.svg
• src/assets/svgs/chat.svg is excluded by !**/*.svg
• src/assets/svgs/checkInRegistrants.svg is excluded by !**/*.svg
• src/assets/svgs/dashboard.svg is excluded by !**/*.svg
• src/assets/svgs/date.svg is excluded by !**/*.svg
• src/assets/svgs/event.svg is excluded by !**/*.svg
• src/assets/svgs/events.svg is excluded by !**/*.svg
• src/assets/svgs/flask.svg is excluded by !**/*.svg
• src/assets/svgs/funds.svg is excluded by !**/*.svg
• src/assets/svgs/key.svg is excluded by !**/*.svg
• src/assets/svgs/listEventRegistrants.svg is excluded by !**/*.svg
• src/assets/svgs/location.svg is excluded by !**/*.svg
• src/assets/svgs/logout.svg is excluded by !**/*.svg
• src/assets/svgs/media.svg is excluded by !**/*.svg
• src/assets/svgs/newChat.svg is excluded by !**/*.svg
• src/assets/svgs/organizations.svg is excluded by !**/*.svg
• src/assets/svgs/palisadoes.svg is excluded by !**/*.svg
• src/assets/svgs/people.svg is excluded by !**/*.svg
• src/assets/svgs/plugins.svg is excluded by !**/*.svg
• src/assets/svgs/post.svg is excluded by !**/*.svg
• src/assets/svgs/posts.svg is excluded by !**/*.svg
• src/assets/svgs/requests.svg is excluded by !**/*.svg
• src/assets/svgs/roles.svg is excluded by !**/*.svg
• src/assets/svgs/settings.svg is excluded by !**/*.svg
• src/assets/svgs/social-icons/Facebook-Logo.svg is excluded by !**/*.svg
• src/assets/svgs/social-icons/Github-Logo.svg is excluded by !**/*.svg
• src/assets/svgs/social-icons/Instagram-Logo.svg is excluded by !**/*.svg
• src/assets/svgs/social-icons/Linkedin-Logo.svg is excluded by !**/*.svg
• src/assets/svgs/social-icons/Reddit-Logo.svg is excluded by !**/*.svg
• src/assets/svgs/social-icons/Slack-Logo.svg is excluded by !**/*.svg
• src/assets/svgs/social-icons/X-Logo.svg is excluded by !**/*.svg
• src/assets/svgs/social-icons/Youtube-Logo.svg is excluded by !**/*.svg
• src/assets/svgs/tag.svg is excluded by !**/*.svg
• src/assets/svgs/tags.svg is excluded by !**/*.svg
• src/assets/svgs/talawa.svg is excluded by !**/*.svg
• src/assets/svgs/user.svg is excluded by !**/*.svg
• src/assets/svgs/userEvent.svg is excluded by !**/*.svg
• src/assets/svgs/users.svg is excluded by !**/*.svg
• src/assets/svgs/venues.svg is excluded by !**/*.svg
• src/assets/talawa-logo-lite-200x200.png is excluded by !**/*.png

📒 Files selected for processing (82)

• .coderabbit.yaml (1 hunks)
• .env.example (1 hunks)
• .eslintignore (1 hunks)
• .eslintrc.json (4 hunks)
• .github/ISSUE_TEMPLATE/bug-report.md (2 hunks)
• .github/ISSUE_TEMPLATE/feature-request.md (2 hunks)
• .github/dependabot.yaml (1 hunks)
• .github/pull_request_template.md (2 hunks)
• .github/workflows/README.md (1 hunks)
• .github/workflows/auto-label.json5 (1 hunks)
• .github/workflows/check-tsdoc.js (1 hunks)
• .github/workflows/ci.yml (0 hunks)
• .github/workflows/codeql-analysis.yml (0 hunks)
• .github/workflows/codeql-codescan.yml (1 hunks)
• .github/workflows/compare_translations.py (1 hunks)
• .github/workflows/countline.py (1 hunks)
• .github/workflows/eslint_disable_check.py (1 hunks)
• .github/workflows/issue.yml (1 hunks)
• .github/workflows/linter.yml (0 hunks)
• .github/workflows/npm-publish.yml (0 hunks)
• .github/workflows/pull-request-target.yml (1 hunks)
• .github/workflows/pull-request.yml (1 hunks)
• .github/workflows/push.yml (1 hunks)
• .github/workflows/stale.yml (1 hunks)
• .github/workflows/talawa_admin_md_mdx_format_adjuster.py (1 hunks)
• .gitignore (2 hunks)
• .husky/post-merge (1 hunks)
• .husky/pre-commit (1 hunks)
• .lintstagedrc.json (1 hunks)
• .node-version (1 hunks)
• .prettierignore (1 hunks)
• .prettierrc (1 hunks)
• CODEOWNERS (1 hunks)
• CODE_OF_CONDUCT.md (1 hunks)
• CODE_STYLE.md (1 hunks)
• CONTRIBUTING.md (2 hunks)
• DOCUMENTATION.md (1 hunks)
• Docker_Container/.dockerignore (0 hunks)
• Docker_Container/README.md (0 hunks)
• Docker_Container/docker-compose.yml (0 hunks)
• Docker_Container/dockerfile (0 hunks)
• INSTALLATION.md (1 hunks)
• ISSUE_GUIDELINES.md (1 hunks)
• ISSUE_TEMPLATE.md (0 hunks)
• PR-guidelines.md (0 hunks)
• PR_GUIDELINES.md (1 hunks)
• PULL_REQUEST_TEMPLATE.md (0 hunks)
• README.md (3 hunks)
• config/babel.config.cjs (1 hunks)
• config/vite.config.ts (1 hunks)
• index.html (1 hunks)
• issue-guidelines.md (0 hunks)
• jest-preview.config.ts (1 hunks)
• jest.config.js (1 hunks)
• package.json (2 hunks)
• public/index.html (0 hunks)
• public/locales/en/common.json (1 hunks)
• public/locales/en/errors.json (1 hunks)
• public/locales/en/translation.json (1 hunks)
• public/locales/fr/common.json (1 hunks)
• public/locales/fr/errors.json (1 hunks)
• public/locales/fr/translation.json (1 hunks)
• public/locales/hi/common.json (1 hunks)
• public/locales/hi/errors.json (1 hunks)
• public/locales/hi/translation.json (1 hunks)
• public/locales/sp/common.json (1 hunks)
• public/locales/sp/errors.json (1 hunks)
• public/locales/sp/translation.json (1 hunks)
• public/locales/zh/common.json (1 hunks)
• public/locales/zh/errors.json (1 hunks)
• public/locales/zh/translation.json (1 hunks)
• public/manifest.json (1 hunks)
• schema.graphql (1 hunks)
• scripts/__mocks__/@dicebear/collection.ts (1 hunks)
• scripts/__mocks__/@dicebear/core.ts (1 hunks)
• scripts/__mocks__/@pdfme/generator.test.ts (1 hunks)
• scripts/__mocks__/@pdfme/generator.ts (1 hunks)
• scripts/__mocks__/fileMock.js (1 hunks)
• scripts/custom-test-env.js (1 hunks)
• scripts/githooks/check-localstorage-usage.js (1 hunks)
• scripts/githooks/update-toc.js (1 hunks)
• setup.ts (1 hunks)

⛔ Files not processed due to max files limit (28)

• src/App.test.tsx
• src/App.tsx
• src/Constant/constant.spec.ts
• src/Constant/constant.ts
• src/GraphQl/Mutations/ActionItemCategoryMutations.ts
• src/GraphQl/Mutations/ActionItemMutations.ts
• src/GraphQl/Mutations/AgendaCategoryMutations.ts
• src/GraphQl/Mutations/AgendaItemMutations.ts
• src/GraphQl/Mutations/CampaignMutation.ts
• src/GraphQl/Mutations/CommentMutations.ts
• src/GraphQl/Mutations/EventAttendeeMutations.ts
• src/GraphQl/Mutations/EventVolunteerMutation.ts
• src/GraphQl/Mutations/FundMutation.ts
• src/GraphQl/Mutations/OrganizationMutations.ts
• src/GraphQl/Mutations/PledgeMutation.ts
• src/GraphQl/Mutations/TagMutations.ts
• src/GraphQl/Mutations/VenueMutations.ts
• src/GraphQl/Mutations/mutations.ts
• src/GraphQl/Queries/ActionItemCategoryQueries.ts
• src/GraphQl/Queries/ActionItemQueries.ts
• src/GraphQl/Queries/AgendaCategoryQueries.ts
• src/GraphQl/Queries/AgendaItemQueries.ts
• src/GraphQl/Queries/EventVolunteerQueries.ts
• src/GraphQl/Queries/OrganizationQueries.ts
• src/GraphQl/Queries/PlugInQueries.ts
• src/GraphQl/Queries/Queries.ts
• src/GraphQl/Queries/fundQueries.ts
• src/GraphQl/Queries/userTagQueries.ts

💤 Files with no reviewable changes (13)

• .github/workflows/ci.yml
• public/index.html
• ISSUE_TEMPLATE.md
• PR-guidelines.md
• PULL_REQUEST_TEMPLATE.md
• Docker_Container/dockerfile
• issue-guidelines.md
• .github/workflows/linter.yml
• Docker_Container/.dockerignore
• Docker_Container/docker-compose.yml
• Docker_Container/README.md
• .github/workflows/npm-publish.yml
• .github/workflows/codeql-analysis.yml

✅ Files skipped from review due to trivial changes (26)

• .eslintignore
• .node-version
• .github/dependabot.yaml
• public/locales/zh/errors.json
• scripts/mocks/fileMock.js
• .github/workflows/auto-label.json5
• scripts/mocks/@dicebear/core.ts
• public/locales/fr/errors.json
• scripts/mocks/@dicebear/collection.ts
• config/babel.config.cjs
• .prettierrc
• CODEOWNERS
• .coderabbit.yaml
• jest-preview.config.ts
• .prettierignore
• .lintstagedrc.json
• public/locales/sp/translation.json
• .env.example
• public/locales/fr/translation.json
• index.html
• public/locales/hi/translation.json
• public/locales/hi/errors.json
• public/locales/zh/common.json
• public/locales/fr/common.json
• public/locales/en/common.json
• public/locales/sp/common.json

🧰 Additional context used

📓 Learnings (1)

scripts/githooks/check-localstorage-usage.js (1)

Learnt from: MayankJha014
PR: PalisadoesFoundation/talawa-admin#2612
File: scripts/githooks/check-localstorage-usage.js:10-18
Timestamp: 2024-12-07T14:25:09.928Z
Learning: TypeScript type annotations should not be added to JavaScript (`.js`) files in this project. Type annotations can only be used in TypeScript (`.ts` or `.tsx`) files.

🪛 eslint

scripts/custom-test-env.js

[error] 5-5: tsdoc-undefined-tag: The TSDoc tag "@pdfme" is not defined in this configuration

(tsdoc/syntax)

---

[error] 9-9: Missing return type on function.

(@typescript-eslint/explicit-function-return-type)

---

[error] 9-9: Missing return type on function.

(@typescript-eslint/explicit-module-boundary-types)

scripts/githooks/update-toc.js

[error] 11-12: Delete ··⏎

(prettier/prettier)

jest.config.js

[error] 33-33: Delete ·

(prettier/prettier)

---

[error] 34-34: Insert ,

(prettier/prettier)

scripts/githooks/check-localstorage-usage.js

[error] 10-10: Missing return type on function.

(@typescript-eslint/explicit-function-return-type)

---

[error] 20-20: Missing return type on function.

(@typescript-eslint/explicit-function-return-type)

---

[error] 43-43: Missing return type on function.

(@typescript-eslint/explicit-function-return-type)

---

[error] 89-89: Insert ,

(prettier/prettier)

---

[error] 92-92: Insert ,

(prettier/prettier)

🪛 actionlint (1.7.4)

.github/workflows/codeql-codescan.yml

35-35: the runner of "github/codeql-action/init@v2" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

---

41-41: the runner of "github/codeql-action/autobuild@v2" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

---

44-44: the runner of "github/codeql-action/analyze@v2" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

.github/workflows/stale.yml

28-28: the runner of "actions/stale@v8" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

.github/workflows/pull-request.yml

61-61: property "changed_files" is not defined in object type {changed-files: {conclusion: string; outcome: string; outputs: {string => string}}}

(expression)

---

62-62: shellcheck reported issue in this script: SC2086:info:1:12: Double quote to prevent globbing and word splitting

(shellcheck)

---

79-79: "github.event.pull_request.head.ref" is potentially untrusted. avoid using it directly in inline scripts. instead, pass it through an environment variable. see https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions for more details

(expression)

.github/workflows/issue.yml

29-29: the runner of "actions/github-script@v6" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

🪛 yamllint (1.35.1)

.github/workflows/codeql-codescan.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 17-17: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

---

[warning] 31-31: wrong indentation: expected 6 but found 7

(indentation)

---

[warning] 37-37: wrong indentation: expected 11 but found 10

(indentation)

.github/workflows/stale.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 20-20: trailing spaces

(trailing-spaces)

---

[error] 21-21: trailing spaces

(trailing-spaces)

.github/workflows/pull-request-target.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 13-13: trailing spaces

(trailing-spaces)

---

[error] 15-15: trailing spaces

(trailing-spaces)

---

[error] 27-27: trailing spaces

(trailing-spaces)

---

[error] 28-28: trailing spaces

(trailing-spaces)

---

[error] 29-29: trailing spaces

(trailing-spaces)

---

[error] 31-31: trailing spaces

(trailing-spaces)

---

[error] 33-33: trailing spaces

(trailing-spaces)

---

[error] 34-34: trailing spaces

(trailing-spaces)

---

[error] 36-36: trailing spaces

(trailing-spaces)

---

[error] 41-41: trailing spaces

(trailing-spaces)

---

[error] 46-46: trailing spaces

(trailing-spaces)

---

[error] 71-71: trailing spaces

(trailing-spaces)

.github/workflows/push.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[error] 17-17: trailing spaces

(trailing-spaces)

---

[error] 18-18: trailing spaces

(trailing-spaces)

---

[warning] 20-20: wrong indentation: expected 2 but found 4

(indentation)

---

[error] 21-21: trailing spaces

(trailing-spaces)

---

[error] 50-50: trailing spaces

(trailing-spaces)

---

[warning] 62-62: too many blank lines

(1 > 0) (empty-lines)

.github/workflows/pull-request.yml

[error] 49-49: trailing spaces

(trailing-spaces)

---

[error] 60-60: trailing spaces

(trailing-spaces)

---

[error] 63-63: trailing spaces

(trailing-spaces)

---

[error] 92-92: trailing spaces

(trailing-spaces)

---

[error] 126-126: trailing spaces

(trailing-spaces)

---

[error] 129-129: trailing spaces

(trailing-spaces)

---

[error] 150-150: trailing spaces

(trailing-spaces)

---

[error] 157-157: trailing spaces

(trailing-spaces)

---

[error] 197-197: trailing spaces

(trailing-spaces)

---

[error] 201-201: trailing spaces

(trailing-spaces)

---

[error] 204-204: trailing spaces

(trailing-spaces)

---

[error] 205-205: trailing spaces

(trailing-spaces)

---

[error] 213-213: trailing spaces

(trailing-spaces)

---

[error] 243-243: trailing spaces

(trailing-spaces)

---

[error] 249-249: trailing spaces

(trailing-spaces)

---

[error] 251-251: trailing spaces

(trailing-spaces)

.github/workflows/issue.yml

[error] 6-6: trailing spaces

(trailing-spaces)

---

[warning] 15-15: wrong indentation: expected 4 but found 6

(indentation)

---

[warning] 66-66: too many blank lines

(1 > 0) (empty-lines)

🪛 Markdownlint (0.37.0)

.github/ISSUE_TEMPLATE/feature-request.md

28-28: null
Bare URL used

(MD034, no-bare-urls)

---

25-25: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

DOCUMENTATION.md

25-25: null
Bare URL used

(MD034, no-bare-urls)

CONTRIBUTING.md

104-104: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

113-113: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

128-128: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

139-139: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

143-143: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

158-158: null
No empty links

(MD042, no-empty-links)

---

159-159: null
No empty links

(MD042, no-empty-links)

---

161-161: null
No empty links

(MD042, no-empty-links)

CODE_STYLE.md

128-128: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)

---

129-129: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)

---

130-130: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)

---

131-131: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)

---

132-132: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)

---

133-133: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)

---

134-134: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)

---

135-135: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)

---

136-136: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)

---

137-137: Expected: 2; Actual: 4
Unordered list indentation

(MD007, ul-indent)

---

164-164: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)

---

165-165: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)

---

166-166: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)

---

57-57: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

73-73: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

75-75: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

92-92: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

190-190: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

230-230: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

---

58-58: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

65-65: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

78-78: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

95-95: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

158-158: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

173-173: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

181-181: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

239-239: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

245-245: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

251-251: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

PR_GUIDELINES.md

31-31: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

39-39: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

README.md

53-53: null
Multiple spaces after hash on atx style heading

(MD019, no-multiple-space-atx)

INSTALLATION.md

321-321: Expected: h3; Actual: h4
Heading levels should only increment by one level at a time

(MD001, heading-increment)

---

33-33: Expected: 4; Actual: 6
Unordered list indentation

(MD007, ul-indent)

---

34-34: Expected: 4; Actual: 6
Unordered list indentation

(MD007, ul-indent)

---

95-95: null
Dollar signs used before commands without showing output

(MD014, commands-show-output)

---

105-105: null
Bare URL used

(MD034, no-bare-urls)

---

142-142: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

154-154: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

164-164: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

188-188: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

194-194: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

200-200: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

208-208: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

214-214: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

220-220: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

240-240: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

256-256: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

264-264: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

270-270: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

292-292: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

300-300: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

313-313: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

327-327: Expected: fenced; Actual: indented
Code block style

(MD046, code-block-style)

---

335-335: Expected: fenced; Actual: indented
Code block style

(MD046, code-block-style)

---

178-178: Expected: #setting-up-react_app_talawa_url-in-env-file; Actual: #setting-up-REACT_APP_TALAWA_URL-in-env-file
Link fragments should be valid

(MD051, link-fragments)

---

178-178: Expected: #setting-up-react_app_recaptcha_site_key-in-env-file; Actual: #setting-up-REACT_APP_RECAPTCHA_SITE_KEY-in-env-file
Link fragments should be valid

(MD051, link-fragments)

.github/ISSUE_TEMPLATE/bug-report.md

36-36: null
Bare URL used

(MD034, no-bare-urls)

---

33-33: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

🪛 LanguageTool

DOCUMENTATION.md

[grammar] ~25-~25: The modal verb ‘should’ requires the verb’s base form.
Context: ...f docs.talawa.io should automatically launched in your browser at http://localhost:300...

(MD_BASEFORM)

---

[grammar] ~26-~26: Did you mean the formatting language “Markdown” (= proper noun)?
Context: ...ttp://localhost:3000/ 1. Add/modify the markdown documents to the docs/ directory of t...

(MARKDOWN_NNP)

---

[uncategorized] ~32-~32: The preposition “to” seems more likely in this position.
Context: ... PLEASE do not add markdown files in this repository. Add them to `talawa-do...

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)

CONTRIBUTING.md

[style] ~27-~27: This expression usually appears with a “please” in front of it.
Context: ...DUCT.md) to understand what this means. Let us know immediately if you have unacceptable ex...

(INSERT_PLEASE)

---

[uncategorized] ~34-~34: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...)" videos are extremely helpful for new open source contributors. ## Ways to Contribute I...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[grammar] ~62-~62: A determiner may be missing.
Context: ...l Request guidelines](PR_GUIDELINES.md) is best resource to follow to start working on ...

(THE_SUPERLATIVE)

---

[uncategorized] ~68-~68: Loose punctuation mark.
Context: ...ushed to the main branch: - develop: For unstable code and bug fixing - `mai...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~69-~69: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...d bug fixing - main: Where the stable production ready code lies. This is our default branch. ...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[typographical] ~73-~73: Consider adding a comma.
Context: ...ultiple developers are working on issues there is bound to be a conflict of interest (...

(IF_THERE_COMMA)

---

[typographical] ~73-~73: Consider adding a comma after ‘Usually’ for more clarity.
Context: ...licts) among issues, PRs or even ideas. Usually these conflicts are resolved in a **Fir...

(RB_LY_COMMA)

---

[grammar] ~73-~73: Did you mean “served” (as in the idiom ‘first come, first served’)?
Context: ...ts are resolved in a First Come First Serve basis however there are certain excep...

(FIRST_SERVED)

---

[uncategorized] ~75-~75: Possible missing comma found.
Context: ... an extension or in conflict with other PRs it is important to ask the author of th...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[grammar] ~75-~75: Did you mean the communication tool “Slack” (= proper noun, capitalized)?
Context: ...tant to ask the author of the PR in the slack channel or in their PRs or issues thems...

(ON_SKYPE)

---

[style] ~77-~77: ‘Last but not the least’ might be wordy. Consider a shorter alternative.
Context: ...y and test that function when needed. - Last but not the least, communication is important make sure t...

(EN_WORDINESS_PREMIUM_LAST_BUT_NOT_THE_LEAST)

---

[grammar] ~77-~77: It seems that “to” is missing before the verb.
Context: ...t the least, communication is important make sure to talk to other contributors, in ...

(MISSING_TO_BETWEEN_BE_AND_VB)

---

[grammar] ~77-~77: Did you mean the communication tool “Slack” (= proper noun, capitalized)?
Context: ... other contributors, in these cases, in slack channel or in a issue/PR thread. - As a...

(ON_SKYPE)

---

[misspelling] ~77-~77: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ... in these cases, in slack channel or in a issue/PR thread. - As a last resort the...

(EN_A_VS_AN)

---

[typographical] ~78-~78: It appears that a comma is missing.
Context: ...el or in a issue/PR thread. - As a last resort the Admins would be responsible for dec...

(DURING_THAT_TIME_COMMA)

---

[grammar] ~135-~135: The operating system from Apple is written “macOS”.
Context: ...r packages can be found for Windows and MacOS. 6. The currently acceptable c...

(MAC_OS)

---

[uncategorized] ~163-~163: Possible missing comma found.
Context: ...odecov/results.jpg)]() 1. After making changes you can add them to git locally using `...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[uncategorized] ~164-~164: Possible missing comma found.
Context: ...o add all changes). 1. After adding the changes you need to commit them using `git comm...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[uncategorized] ~165-~165: Possible missing comma found.
Context: ...using: git push origin <branch_name>.(Here branch name must be name of the branch ...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[uncategorized] ~165-~165: Possible missing article found.
Context: ...: git push origin <branch_name>.(Here branch name must be name of the branch you wan...

(AI_HYDRA_LEO_MISSING_THE)

---

[uncategorized] ~165-~165: Possible missing article found.
Context: ...branch_name>`.(Here branch name must be name of the branch you want to push the chan...

(AI_HYDRA_LEO_MISSING_THE)

---

[uncategorized] ~167-~167: Possible missing comma found.
Context: ...test suite passes, either locally or on CI once a PR has been created. 1. Review a...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[grammar] ~178-~178: Did you mean the communication tool “Slack” (= proper noun, capitalized)?
Context: ...dation/talawa) for the link to join our slack channel. 1. We also have a technical em...

(ON_SKYPE)

CODE_STYLE.md

[style] ~127-~127: Consider removing “of” to be more concise
Context: ...tories of src assets - This houses all of the static assets used in the project - `...

(ALL_OF_THE)

---

[style] ~128-~128: Consider removing “of” to be more concise
Context: ... in the project - css - This houses all of the css files used in the project - `imag...

(ALL_OF_THE)

---

[style] ~129-~129: Consider removing “of” to be more concise
Context: ... the project - images - This houses all of the images used in the project - scss -...

(ALL_OF_THE)

---

[style] ~130-~130: Consider removing “of” to be more concise
Context: ...in the project - scss - This houses all of the scss files used in the project - `c...

(ALL_OF_THE)

---

[grammar] ~134-~134: The singular proper name ‘Sass’ must be used with a third-person or a past tense verb.
Context: ...rms - _talawa.scss - Partial Sass file for Talawa - _utilities.scss - Pa...

(HE_VERB_AGR)

---

[grammar] ~135-~135: The singular proper name ‘Sass’ must be used with a third-person or a past tense verb.
Context: ... - _utilities.scss - Partial Sass file for utilities - _variables.scss -...

(HE_VERB_AGR)

---

[grammar] ~136-~136: The singular proper name ‘Sass’ must be used with a third-person or a past tense verb.
Context: ... - _variables.scss - Partial Sass file for variables - app.scss - Main S...

(HE_VERB_AGR)

---

[style] ~141-~141: Consider removing “of” to be more concise
Context: ...views/screens Constant - This houses all of the constants used in the project `GraphQl...

(ALL_OF_THE)

---

[style] ~143-~143: Consider removing “of” to be more concise
Context: ...in the project GraphQl - This houses all of the GraphQL queries and mutations used in t...

(ALL_OF_THE)

---

[style] ~145-~145: Consider removing “of” to be more concise
Context: ...in the project screens - This houses all of the views/screens to be navigated through i...

(ALL_OF_THE)

---

[style] ~147-~147: Consider removing “of” to be more concise
Context: ... in Talawa-Admin state - This houses all of the state management code for the project ...

(ALL_OF_THE)

---

[uncategorized] ~165-~165: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...following order: - React imports - Third party imports - Local imports If there is...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

PR_GUIDELINES.md

[uncategorized] ~2-~2: Loose punctuation mark.
Context: # Pull Request Guidelines 👍🎉 First off, thanks for taking t...

(UNLIKELY_OPENING_PUNCTUATION)

---

[style] ~4-~4: Consider a shorter alternative to avoid wordiness.
Context: ...ing the time to contribute! 🎉👍 In order to give everyone a chance to submit a pull...

(IN_ORDER_TO_PREMIUM)

---

[style] ~46-~46: Style-wise, it’s not ideal to insert an adverb (‘manually’) in the middle of an infinitive construction (‘to test’). Try moving the adverb to avoid split infinitives.
Context: ..., you'll need to tell us what steps you followed to manually test your changes. 1. Please read our [CONTRIBUTING.md](C...

(SPLIT_INFINITIVE)

---

[style] ~56-~56: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...o be closed. The quality of our code is very important to us. Therefore we make experienced ma...

(EN_WEAK_ADJECTIVE)

---

[uncategorized] ~56-~56: A comma may be missing after the conjunctive/linking adverb ‘Therefore’.
Context: ...ty of our code is very important to us. Therefore we make experienced maintainers of our ...

(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)

---

[style] ~59-~59: Consider using a different verb for a more formal wording.
Context: ...check if all tests are passing; if not, fix the issues and then create a pull reque...

(FIX_RESOLVE)

---

[style] ~64-~64: This expression is wordy and overused. Consider replacing it with a more concise and formal alternative.
Context: ...wer your questions, but we'll get to it sooner or later. @mentioning someone just adds to the p...

(SOONER_OR_LATER)

---

[uncategorized] ~64-~64: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...adds to the pile of notifications we get and it won't make us look at your issue fas...

(COMMA_COMPOUND_SENTENCE)

---

[style] ~65-~65: Consider shortening or rephrasing this to strengthen your wording.
Context: ...ue faster. 1. Do not force push. If you make changes to your pull request, please simply add a ...

(MAKE_CHANGES)

.github/workflows/README.md

[duplication] ~24-~24: Possible typo: you repeated a word
Context: ...ors: 1. Place all actions related to to this in the pull-request-target.yml f...

(ENGLISH_WORD_REPEAT_RULE)

---

[uncategorized] ~35-~35: The abbreviation “e.g.” (= for example) requires two periods.
Context: ...orrectly if they have a dedicated file (eg. CodeQL) ## Scripts Follow these gui...

(E_G)

ISSUE_GUIDELINES.md

[uncategorized] ~2-~2: Loose punctuation mark.
Context: # Issue Report Guidelines 👍🎉 First off, thanks for taking t...

(UNLIKELY_OPENING_PUNCTUATION)

---

[style] ~4-~4: Consider a shorter alternative to avoid wordiness.
Context: ...ing the time to contribute! 🎉👍 In order to give everyone a chance to submit a issu...

(IN_ORDER_TO_PREMIUM)

---

[misspelling] ~5-~5: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ...der to give everyone a chance to submit a issues reports and contribute to the Ta...

(EN_A_VS_AN)

---

[typographical] ~24-~24: Consider adding a comma here.
Context: ...> ___ ## Issue Management In all cases please use the [GitHub open issue search](http...

(PLEASE_COMMA)

---

[style] ~30-~30: Consider using a different verb for a more formal wording.
Context: .... 1. Verify whether the issue has been fixed by trying to reproduce it using the lat...

(FIX_RESOLVE)

---

[style] ~35-~35: The wording of this phrase can be improved.
Context: ...lcome contributors who find new ways to make the code better. ### Existing Issues You can also be ...

(MAKE_STYLE_BETTER)

---

[grammar] ~44-~44: Did you mean the communication tool “Slack” (= proper noun, capitalized)?
Context: ...butors to assign it to you in #talawa slack channel. Working on these types of exi...

(ON_SKYPE)

---

[grammar] ~53-~53: Did you mean the communication tool “Slack” (= proper noun, capitalized)?
Context: ...ew Issues 1. Join our #talawa-github slack channel for automatic issue and pull re...

(ON_SKYPE)

---

[grammar] ~57-~57: Did you mean the communication tool “Slack” (= proper noun, capitalized)?
Context: ...lines 1. Discuss issues in our various slack channels when necessary 2. Please do no...

(ON_SKYPE)

---

[typographical] ~57-~57: Consider adding a comma here.
Context: ...ur various slack channels when necessary 2. Please do not derail or troll issues. 3. Keep...

(PLEASE_COMMA)

README.md

[uncategorized] ~56-~56: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...)" videos are extremely helpful for new open source contributors.

(EN_COMPOUND_ADJECTIVE_INTERNAL)

INSTALLATION.md

[duplication] ~25-~25: Possible typo: you repeated a word
Context: ...](#running-talawa-admin) - Accessing Talawa-Admin - [Talawa-Admin Registration](#talawa-admin-registratio...

(ENGLISH_WORD_REPEAT_RULE)

---

[typographical] ~55-~55: It appears that a comma is missing.
Context: ... that follow. # Prerequisites In this section we'll explain how to set up all the pre...

(DURING_THAT_TIME_COMMA)

---

[uncategorized] ~61-~61: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: .... Basic git knowledge is required for open source contribution so make sure you're comfor...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[grammar] ~67-~67: The word “setup” is a noun. The verb is spelled with a space.
Context: ...avigate to the folder where you want to setup the repository. 2. Open a cmd (Window...

(NOUN_VERB_CONFUSION)

---

[grammar] ~68-~68: The operating system from Apple is written “macOS”.
Context: ...cmd (Windows) or terminal (Linux or MacOS) session in this folder. 1. An easy ...

(MAC_OS)

---

[uncategorized] ~70-~70: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...e option based on your OS. 3. For Our Open Source Contributor Software Developers: ...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[grammar] ~102-~102: The operating system from Apple is written “macOS”.
Context: ...node.jspackages in Windows, Linux and MacOS. 1. For Windows: 1. first install...

(MAC_OS)

---

[duplication] ~116-~116: Possible typo: you repeated a word
Context: ... 5. Save the document. 6. Exit notepad 7. Exit PowerShell 8. This will ensure...

(ENGLISH_WORD_REPEAT_RULE)

---

[grammar] ~119-~119: The operating system from Apple is written “macOS”.
Context: ...t version of node.js 2. For Linux and MacOS, use the terminal window. 1. install...

(MAC_OS)

---

[grammar] ~123-~123: The word “setup” is a noun. The verb is spelled with a white space.
Context: ... the respective recommended commands to setup your node environment 3. This wil...

(NOUN_VERB_CONFUSION)

---

[uncategorized] ~162-~162: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...at runtime. It is not a part of the repo and you will have to create it. For a sampl...

(COMMA_COMPOUND_SENTENCE)

---

[grammar] ~228-~228: The word “setup” is a noun. The verb is spelled with a space.
Context: ...E_KEY in .env file You may not want to setup reCAPTCHA since the project will still ...

(NOUN_VERB_CONFUSION)

---

[grammar] ~232-~232: The word “setup” is a noun. The verb is spelled with a space.
Context: ...ad the following steps. If you want to setup Google reCAPTCHA now, you may refer to ...

(NOUN_VERB_CONFUSION)

---

[typographical] ~246-~246: Except for inverted sentences, ‘need them’ requires a question mark at the end of the sentence.
Context: ...t need them or want to keep the console clean # Post Configuration Steps It's now t...

(MD_PRP_QUESTION_MARK)

---

[uncategorized] ~261-~261: Did you mean: “By default,”?
Context: ...n serve ``` ## Accessing Talawa-Admin By default talawa-admin runs on port `4321` on y...

(BY_DEFAULT_COMMA)

---

[grammar] ~311-~311: The word ‘lint’ is a noun or an adjective. A verb or adverb is missing or misspelled here, or maybe a comma is missing.
Context: ...w.webp) ## Linting code files You can lint your code files using this command: ``...

(PRP_MD_NN)

CODE_OF_CONDUCT.md

[duplication] ~11-~11: Possible typo: you repeated a word
Context: ...-responsibilities) - Scope - Enforcement - Enforcement Guidelines ...

(ENGLISH_WORD_REPEAT_RULE)

🪛 Ruff (0.8.2)

.github/workflows/compare_translations.py

135-135: Within an except clause, raise exceptions with raise ... from err or raise ... from None to distinguish them from errors in exception handling

(B904)

.github/workflows/eslint_disable_check.py

61-61: Loop control variable dirs not used within loop body

Rename unused dirs to _dirs

(B007)

🔇 Additional comments (36)

CODE_OF_CONDUCT.md (2)

3-20: Well-structured table of contents implementation!

The table of contents is properly implemented with:

• Clear hierarchical structure
• Correct markdown link syntax
• Proper section mapping

🧰 Tools

🪛 LanguageTool

[duplication] ~11-~11: Possible typo: you repeated a word
Context: ...-responsibilities) - Scope - Enforcement - Enforcement Guidelines ...

(ENGLISH_WORD_REPEAT_RULE)

---

11-12: Ignore the word repetition warning.

The repetition of "Enforcement" in the table of contents is correct as these are distinct sections with different purposes.

🧰 Tools

🪛 LanguageTool

[duplication] ~11-~11: Possible typo: you repeated a word
Context: ...-responsibilities) - Scope - Enforcement - Enforcement Guidelines ...

(ENGLISH_WORD_REPEAT_RULE)

public/manifest.json (1)

16-16: Verify the new image path exists

The logo path has been moved to the "images" subdirectory. Let's verify this path exists and contains the required image.

✅ Verification successful

Logo path verification successful

The image file exists at the new location public/images/logo512.png, confirming that the manifest.json correctly references the moved image path.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the existence of the 512x512 logo in the new path

# Check if the image exists in the new location
if [ -f "public/images/logo512.png" ]; then
    echo "✓ Image exists at public/images/logo512.png"
else
    echo "✗ Image not found at public/images/logo512.png"
    
    # Check if it exists in the old location
    if [ -f "public/logo512.png" ]; then
        echo "! Image found at old location: public/logo512.png"
        echo "! Please move the image to public/images/ directory"
    else
        echo "! Image not found in old location either"
    fi
fi

Length of output: 135

.github/workflows/stale.yml (3)

12-17: LGTM! Well-configured workflow trigger

The workflow name is descriptive and the daily schedule is appropriate for managing stale items.

---

22-26: LGTM! Appropriate job configuration

The job configuration is correctly set up with the latest Ubuntu runner.

---

27-43: Verify stale action version compatibility

The stale action configuration is well-structured with appropriate timeframes and exemptions. However, there's a potential compatibility issue with the action version.

Let's verify the latest stable version and compatibility:

Consider updating to a newer version if available, but otherwise, the configuration is solid with:

• Appropriate stale/close timeframes (10/180 days)
• Clear notification messages
• Good exemptions for WIP items and milestones
• Reasonable rate limiting (30 operations per run)

🧰 Tools

🪛 actionlint (1.7.4)

28-28: the runner of "actions/stale@v8" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

public/locales/en/translation.json (1)

1-1483: Well-structured JSON file with proper organization!

The file follows proper JSON formatting with consistent nesting and organization.

scripts/githooks/check-localstorage-usage.js (4)

3-5: Avoid potential ESM/CJS compatibility issues in JavaScript files.

You're using ES module imports (e.g., import path from 'path') in a .js file, which might not be supported in older Node.js environments without additional configuration. If your Node.js version and environment are modern enough, this is fine. Otherwise, consider using CommonJS-style require statements.

---

10-18: Ignore static-analysis requests for return-type annotations in .js files.

The static analysis hint suggests adding function return types, but your retrieved learnings mention that type annotations are not used in .js files. You can safely ignore the ESLint or TypeScript-linter-suggested “return type” addition.

🧰 Tools

🪛 eslint

[error] 10-10: Missing return type on function.

(@typescript-eslint/explicit-function-return-type)

---

20-37: Ignore static-analysis requests for return-type annotations in .js files.

Same reasoning as above for getModifiedFiles. This is plain JavaScript, so no type annotations are needed.

🧰 Tools

🪛 eslint

[error] 20-20: Missing return type on function.

(@typescript-eslint/explicit-function-return-type)

---

43-78: Ignore static-analysis requests for return-type annotations in .js files.

Again, for checkLocalStorageUsage, no need for type annotations in .js.

🧰 Tools

🪛 eslint

[error] 43-43: Missing return type on function.

(@typescript-eslint/explicit-function-return-type)

public/locales/hi/common.json (3)

14-20: Authentication and navigation translations look good!

The translations use commonly understood Hindi terms that are widely recognized in the context of web applications.

---

1-98: JSON structure and formatting look good!

The file follows proper JSON formatting with:

• Valid JSON structure
• Consistent indentation
• No trailing commas

---

1-98: Verify translation key consistency across language files

Let's ensure all translation keys are consistent across different language files.

✅ Verification successful

Let me generate another script to better analyze the translation keys since the previous output didn't show the actual differences.

---

Let me try one more script with a different approach since comm is not available:

---

Let me try one final approach with a simpler script:

---

Translation keys are consistent across all language files

Based on the analysis results, all language files (en, fr, hi, sp, zh) contain exactly 96 keys each, and the sample keys shown are identical across all files. The key structure is perfectly maintained across all translation files, ensuring consistency in the internationalization system.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Compare translation keys across language files to ensure consistency

# Find all language files
echo "Checking for language files..."
fd -e json . public/locales

# Extract and compare keys
for lang in public/locales/*/common.json; do
  echo "Analyzing keys in $lang..."
  jq -r 'keys[]' "$lang" | sort > "/tmp/$(basename $(dirname $lang))_keys.txt"
done

# Compare keys between files
if [ -f "/tmp/en_keys.txt" ]; then
  echo "Comparing with English translations..."
  for lang in /tmp/*_keys.txt; do
    if [ "$lang" != "/tmp/en_keys.txt" ]; then
      echo "Differences with $(basename $lang _keys.txt):"
      diff "/tmp/en_keys.txt" "$lang"
    fi
  done
fi

Length of output: 3011

---

Script:

#!/bin/bash
# Get a better view of the keys in each language file
for lang in public/locales/*/common.json; do
  lang_code=$(basename $(dirname $lang))
  echo "=== Keys in $lang_code translation ==="
  jq 'keys | length' "$lang" | xargs echo "Total keys:"
  # Show keys unique to this language file compared to English
  if [ "$lang_code" != "en" ]; then
    echo "Keys in $lang_code but not in English:"
    comm -13 <(jq -r 'keys[]' public/locales/en/common.json | sort) <(jq -r 'keys[]' "$lang" | sort)
    echo "Keys in English but not in $lang_code:"
    comm -23 <(jq -r 'keys[]' public/locales/en/common.json | sort) <(jq -r 'keys[]' "$lang" | sort)
  fi
  echo
done

Length of output: 4110

---

Script:

#!/bin/bash
# Compare keys between English and other language files using basic tools
for lang in public/locales/*/common.json; do
  lang_code=$(basename $(dirname $lang))
  echo "=== Comparing $lang_code with English ==="
  echo "Total keys in $lang_code: $(jq 'keys | length' "$lang")"
  
  if [ "$lang_code" != "en" ]; then
    # Find missing or extra keys
    echo "Checking for differences..."
    
    # Keys in this language but not in English
    echo "Keys in $lang_code but not in English:"
    diff <(jq -r 'keys[]' public/locales/en/common.json | sort) <(jq -r 'keys[]' "$lang" | sort) | grep '^>' || echo "None"
    
    # Keys in English but not in this language
    echo "Keys in English but not in $lang_code:"
    diff <(jq -r 'keys[]' public/locales/en/common.json | sort) <(jq -r 'keys[]' "$lang" | sort) | grep '^<' || echo "None"
    echo
  fi
done

Length of output: 4578

---

Script:

#!/bin/bash
# Simple key count and comparison
echo "=== Translation Key Analysis ==="

# First get English keys as reference
en_keys=$(jq -r 'keys[]' public/locales/en/common.json | sort)
en_count=$(echo "$en_keys" | wc -l)
echo "English keys count: $en_count"

# Compare with other languages
for lang in public/locales/*/common.json; do
  lang_code=$(basename $(dirname $lang))
  if [ "$lang_code" != "en" ]; then
    echo -e "\nAnalyzing $lang_code:"
    lang_keys=$(jq -r 'keys[]' "$lang" | sort)
    lang_count=$(echo "$lang_keys" | wc -l)
    echo "Keys count: $lang_count"
    
    # Show a few sample keys from each file for verification
    echo "Sample keys from $lang_code:"
    jq -r 'keys[0:3][]' "$lang"
  fi
done

Length of output: 11779

config/vite.config.ts (1)

7-11: Consider verifying environment settings.
It's often helpful to validate that the PORT and other environment variables match what's defined in your .env or .env.example files, ensuring that the server port is dynamically derived rather than hard-coded.

scripts/__mocks__/@pdfme/generator.test.ts (1)

5-11: These tests correctly check for a Promise return type.
Everything looks good here. Good job ensuring async correctness.

jest.config.js (1)

1-71: Double-check Jest vs Vitest configurations alignment.

This PR is intended to migrate tests from Jest to Vitest. Keeping or introducing jest.config.js might be redundant if the project fully switches to Vitest. Ensure that if you're fully transitioning, any references to Jest are phased out.

🧰 Tools

🪛 eslint

[error] 33-33: Delete ·

(prettier/prettier)

---

[error] 34-34: Insert ,

(prettier/prettier)

.github/workflows/talawa_admin_md_mdx_format_adjuster.py (1)

1-96: LGTM for the overall approach of escaping MDX characters.

The logic used to escape <, >, {, and } is clear and well-structured. This approach is sufficient for typical MDX usage.

.github/workflows/eslint_disable_check.py (1)

1-122: ESLint-disable logic and messaging.

Overall, the script effectively identifies eslint-disable statements and issues the correct message. This ensures your code remains linted without developer bypass. Very thorough approach.

🧰 Tools

🪛 Ruff (0.8.2)

61-61: Loop control variable dirs not used within loop body

Rename unused dirs to _dirs

(B007)

setup.ts (2)

13-19: Enhance error handling when creating and populating .env.

The script implicitly assumes .env.example exists and is valid. Consider adding a try/catch or appropriate checks (e.g., verifying fs.existsSync('.env.example')) before reading it, to provide a more descriptive error if the file is missing or corrupted.

---

180-183: Successful user feedback.

Ending the setup with a celebratory message is a nice user-experience touch. Good job providing clear guidance on next steps.

.github/workflows/compare_translations.py (1)

1-49: Great introductory module docstring and structure
The purpose, methodology, and usage details are clearly explained. Good job keeping it consistent with Python documentation standards.

.github/workflows/countline.py (1)

1-26: Informative docstring and approach
Your scripting methodology is clearly described. The code commentary effectively guides contributors to maintain concise files, promoting clarity and reusability.

.gitignore (2)

3-6: Lock files properly ignored
Ignoring yarn.lock and pnpm-lock.yaml is standard practice to avoid introducing potential dependency resolution conflicts across different package managers.

---

13-13: Security-conscious environment and coverage ignore
Excluding .env* files, coverage/ output, and debug logs from version control is good practice. This prevents accidental exposure of sensitive info and keeps the repository clean.

Also applies to: 21-28

.github/ISSUE_TEMPLATE/feature-request.md (1)

2-6: Consistent naming and labeling
Renaming the title to “Feature Request” and adjusting the associated labels clarifies the issue type for contributors and maintainers.

.github/workflows/push.yml (2)

36-49: LGTM! Well-structured cache configuration

The cache configuration is well-implemented with:

• Proper cache key based on package-lock.json
• Fallback restore-keys for partial matches
• Caching both ~/.npm and node_modules directories

---

29-29: 🛠️ Refactor suggestion

Consider using LTS version of Node.js

The workflow currently uses Node.js 22.x which is the latest development version. For better stability in CI/CD pipelines, consider using the current LTS version (20.x).

-        node-version: [22.x]
+        node-version: [20.x]

.github/workflows/README.md (1)

1-47: LGTM! Well-structured workflow documentation

The documentation provides clear guidelines for:

• Workflow file organization
• Job sequencing
• Script requirements
• Coding standards

🧰 Tools

🪛 LanguageTool

[duplication] ~24-~24: Possible typo: you repeated a word
Context: ...ors: 1. Place all actions related to to this in the pull-request-target.yml f...

(ENGLISH_WORD_REPEAT_RULE)

---

[uncategorized] ~35-~35: The abbreviation “e.g.” (= for example) requires two periods.
Context: ...orrectly if they have a dedicated file (eg. CodeQL) ## Scripts Follow these gui...

(E_G)

.github/workflows/issue.yml (1)

62-65: LGTM! Well-structured greeting message

The greeting message is informative and includes helpful links to contribution guidelines.

.eslintrc.json (2)

133-134: Review Jest configuration removal

Since the project is transitioning from Jest to Vitest, consider removing Jest-related configurations.

---

63-64: Verify TypeScript rule compatibility

These TypeScript rules appear to be invalid or might not exist in the current version:

• @typescript-eslint/no-unsafe-function-type
• @typescript-eslint/no-wrapper-object-types
• @typescript-eslint/no-empty-object-type

Also applies to: 65-65

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

214-227: Well-structured test coverage configuration!

Good practices observed:

1. High test coverage requirement (95%) ensures code quality
2. Unique naming for Codecov reports prevents collisions

CONTRIBUTING.md (1)

Line range hint 1-179: Documentation is well-structured and comprehensive

The changes provide clear guidelines for contributors, especially regarding testing which aligns with the PR objective.

🧰 Tools

🪛 LanguageTool

[grammar] ~135-~135: The operating system from Apple is written “macOS”.
Context: ...r packages can be found for Windows and MacOS. 6. The currently acceptable c...

(MAC_OS)

---

[uncategorized] ~163-~163: Possible missing comma found.
Context: ...odecov/results.jpg)]() 1. After making changes you can add them to git locally using `...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[uncategorized] ~164-~164: Possible missing comma found.
Context: ...o add all changes). 1. After adding the changes you need to commit them using `git comm...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[uncategorized] ~165-~165: Possible missing comma found.
Context: ...using: git push origin <branch_name>.(Here branch name must be name of the branch ...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[uncategorized] ~165-~165: Possible missing article found.
Context: ...: git push origin <branch_name>.(Here branch name must be name of the branch you wan...

(AI_HYDRA_LEO_MISSING_THE)

---

[uncategorized] ~165-~165: Possible missing article found.
Context: ...branch_name>`.(Here branch name must be name of the branch you want to push the chan...

(AI_HYDRA_LEO_MISSING_THE)

---

[uncategorized] ~167-~167: Possible missing comma found.
Context: ...test suite passes, either locally or on CI once a PR has been created. 1. Review a...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[grammar] ~178-~178: Did you mean the communication tool “Slack” (= proper noun, capitalized)?
Context: ...dation/talawa) for the link to join our slack channel. 1. We also have a technical em...

(ON_SKYPE)

🪛 Markdownlint (0.37.0)

104-104: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

113-113: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

128-128: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

139-139: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

143-143: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

158-158: null
No empty links

(MD042, no-empty-links)

---

159-159: null
No empty links

(MD042, no-empty-links)

---

161-161: null
No empty links

(MD042, no-empty-links)

INSTALLATION.md (1)

288-308: Excellent test documentation!

The test documentation is particularly relevant to the PR objective of refactoring tests:

1. Clear instructions for running tests
2. Debugging guidance with Jest Preview
3. Visual aids for understanding test output

🧰 Tools

🪛 Markdownlint (0.37.0)

292-292: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

300-300: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)

.github/ISSUE_TEMPLATE/bug-report.md (1)

2-7: LGTM! Metadata changes follow GitHub conventions

The changes to the template metadata are consistent with GitHub's best practices:

• Proper capitalization in template name
• Lowercase label format
• Valid YAML syntax for assignees

[coderabbitai]

⚠️ Potential issue

Critical: Incorrect icon size specification for logo192.png

The size "16x16" is inconsistent with the image filename logo192.png which suggests a 192x192 pixel image. This mismatch could break PWA requirements and cause display issues.

Apply this diff to fix the icon size:

-      "sizes": "16x16"
+      "sizes": "192x192"

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	"sizes": "16x16"
	"sizes": "192x192"

[coderabbitai]

⚠️ Potential issue

Missing Spanish translations

Most error messages are still in English instead of Spanish. Only "errorOccurredCouldntCreate" and "errorLoading" are translated to Spanish.

Please translate all error messages to Spanish. For example:

-  "talawaApiUnavailable": "Talawa-API service is unavailable!. Is it running? Check your network connectivity too.",
+  "talawaApiUnavailable": "¡El servicio Talawa-API no está disponible! ¿Está funcionando? Verifique también su conectividad de red.",
-  "notFound": "Not found",
+  "notFound": "No encontrado",

Committable suggestion skipped: line range outside the PR's diff.

[coderabbitai]

🛠️ Refactor suggestion

Standardize naming conventions

There are inconsistencies in the naming conventions:

1. Mixed use of snake_case and camelCase for keys
2. Inconsistent capitalization in values

Consider adopting a consistent naming convention:

-  "atleast_8_char_long": "Atleast 8 Character long",
-  "atleast_6_char_long": "Atleast 6 Character long",
+  "minCharLength8": "At least 8 characters long",
+  "minCharLength6": "At least 6 characters long"

Also applies to: 32-35, 231-232, 233-234

[coderabbitai]

🛠️ Refactor suggestion

Enhance internationalization support

Several areas could benefit from better i18n practices:

1. Add pluralization support for numeric content
2. Use interpolation for dynamic content consistently

Example improvements:

-  "removeUserFrom": "Remove User from {{org}}",
-  "removeConfirmation": "Are you sure you want to remove '{{name}}' from organization '{{org}}'?",
+  "removeUserFrom": "Remove {{userName}} from {{orgName}}",
+  "removeConfirmation": "Are you sure you want to remove '{{userName}}' from '{{orgName}}'?",

Also applies to: 432-433, 1436-1437

[coderabbitai]

⚠️ Potential issue

Replace placeholder translations with proper content

Several keys have values that appear to be placeholders:

• "searchByName": "searchByName"
• "name": "name"
• "email": "email"
• "endOfResults": "endOfResults"

These should be replaced with proper user-facing messages.

Also applies to: 246-248

[coderabbitai]

⚠️ Potential issue

Update testing library versions for React 18 compatibility

The current versions of testing libraries are outdated and incompatible with React 18:

• @testing-library/react v16.0.1 is very old
• @testing-library/user-event v12.1.10 is outdated

Apply this diff to update the versions:

-    "@testing-library/react": "^16.0.1",
-    "@testing-library/user-event": "^12.1.10",
+    "@testing-library/react": "^14.2.1",
+    "@testing-library/user-event": "^14.5.2",

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	"@testing-library/jest-dom": "^6.5.0",
	"@testing-library/react": "^16.0.1",
	"@testing-library/user-event": "^12.1.10",
	"@testing-library/jest-dom": "^6.5.0",
	"@testing-library/react": "^14.2.1",
	"@testing-library/user-event": "^14.5.2",

[coderabbitai]

⚠️ Potential issue

Test configuration doesn't match PR objective

The PR aims to migrate tests to Vitest, but the test script still uses Jest. Consider updating the test configuration to use Vitest.

Apply this diff to update the test script:

-    "test": "cross-env NODE_ENV=test jest --env=./scripts/custom-test-env.js --watchAll --coverage",
+    "test": "vitest --coverage",

Committable suggestion skipped: line range outside the PR's diff.

[coderabbitai]

⚠️ Potential issue

Use stable LTS version of Node.js

The workflow is configured to use Node.js v22.x which is not yet released. This could cause stability issues.

Use a stable LTS version instead:

- node-version: '22.x'
+ node-version: '20.x'

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	- name: Set up Node.js
	uses: actions/setup-node@v4
	with:
	node-version: '22.x'
	- name: Set up Node.js
	uses: actions/setup-node@v4
	with:
	node-version: '20.x'

[coderabbitai]

⚠️ Potential issue

Fix shell script safety issues

The script has potential issues with:

1. Unquoted variables that could break with filenames containing spaces
2. Unchecked environment variable usage

Apply these fixes:

- CHANGED_FILES: ${{ steps.changed_files.outputs.all_changed_files }}
+ CHANGED_FILES: ${{ steps.changed-files.outputs.all_changed_files }}
- npx eslint ${CHANGED_FILES} && python .github/workflows/eslint_disable_check.py
+ npx eslint "${CHANGED_FILES}" && python .github/workflows/eslint_disable_check.py

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	- name: Check for linting errors in modified files
	if: steps.changed-files.outputs.only_changed != 'true'
	env:
	CHANGED_FILES: ${{ steps.changed_files.outputs.all_changed_files }}
	run: npx eslint ${CHANGED_FILES} && python .github/workflows/eslint_disable_check.py
	- name: Check for linting errors in modified files
	if: steps.changed-files.outputs.only_changed != 'true'
	env:
	CHANGED_FILES: ${{ steps.changed-files.outputs.all_changed_files }}
	run: npx eslint "${CHANGED_FILES}" && python .github/workflows/eslint_disable_check.py

🧰 Tools

🪛 actionlint (1.7.4)

61-61: property "changed_files" is not defined in object type {changed-files: {conclusion: string; outcome: string; outputs: {string => string}}}

(expression)

---

62-62: shellcheck reported issue in this script: SC2086:info:1:12: Double quote to prevent globbing and word splitting

(shellcheck)

🪛 yamllint (1.35.1)

[error] 60-60: trailing spaces

(trailing-spaces)

[coderabbitai]

⚠️ Potential issue

Fix incorrect template reference

The additional details section appears to be copied from a feature request template.

Apply this change:

-Add any other context or screenshots about the feature request here.
+Add any other context or screenshots about the bug report here.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	Add any other context or screenshots about the feature request here.
	Add any other context or screenshots about the bug report here.