Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

deploy error solved, push-deploy-website.yml updated #3364

Merged

Conversation

gautam-divyanshu
Copy link
Member

@gautam-divyanshu gautam-divyanshu commented Jan 20, 2025

What kind of change does this PR introduce?

Issue Number:

Fixes #

Snapshots/Videos:
image

If relevant, did you update the documentation?

Summary

Does this PR introduce a breaking change?

Checklist

CodeRabbit AI Review

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

Test Coverage

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

Other information

Have you read the contributing guide?

Summary by CodeRabbit

Release Notes

  • Documentation

    • Added documentation files for mock variables in the Organization Tags component.
    • Introduced new mock variables for testing different scenarios:
      • MOCKS_EMPTY
      • MOCKS_ERROR
      • MOCKS_ERROR_ERROR_TAG
      • MOCKS_NO_MORE_PAGES
      • MOCKS_NULL_END_CURSOR
      • MOCKS_UNDEFINED_USER_TAGS
  • Chores

    • Updated GitHub Actions workflow to use Node.js 20.x.
    • Switched from Yarn to npm for package management and deployment.

Copy link
Contributor

coderabbitai bot commented Jan 20, 2025

Walkthrough

This pull request involves updates to the GitHub Actions workflow for website deployment and the addition of several documentation files for mock variables in the OrganizationTags component. The workflow file has been modified to use Node.js version 20.x and switch from Yarn to npm for package management. Multiple new documentation files have been created to describe mock variables used in testing, providing detailed type and structure information for various scenarios in the OrganizationTags module.

Changes

File Change Summary
.github/workflows/push-deploy-website.yml - Changed Node.js version from 20 to 20.x
- Replaced yarn install --frozen-lockfile with npm ci
- Replaced yarn deploy with npm run deploy
docs/docs/auto-docs/screens/OrganizationTags/OrganizationTagsMocks/variables/ Added documentation files for mock variables:
- MOCKS_EMPTY.md
- MOCKS_ERROR.md
- MOCKS_ERROR_ERROR_TAG.md
- MOCKS_NO_MORE_PAGES.md
- MOCKS_NULL_END_CURSOR.md
- MOCKS_UNDEFINED_USER_TAGS.md

Possibly related PRs

Suggested labels

ignore-sensitive-files-pr

Suggested reviewers

  • palisadoes

Poem

🐰 Deployment's dance, a workflow's new beat,
npm steps in, making deployment sweet.
Mock variables bloom like spring's first light,
Documentation shines, everything's right!
Rabbit hops through code with glee 🚀


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c91155c and 90f5417.

📒 Files selected for processing (1)
  • .github/workflows/push-deploy-website.yml (2 hunks)
🧰 Additional context used
🪛 yamllint (1.35.1)
.github/workflows/push-deploy-website.yml

[error] 41-41: trailing spaces

(trailing-spaces)


[error] 56-56: no new line character at the end of file

(new-line-at-end-of-file)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Test Application
  • GitHub Check: Check Python Code Style
  • GitHub Check: Analyse Code With CodeQL (javascript)
🔇 Additional comments (1)
.github/workflows/push-deploy-website.yml (1)

41-41: LGTM! Good practice using semantic versioning.

Using 20.x allows for automatic minor version updates while maintaining major version compatibility.

🧰 Tools
🪛 yamllint (1.35.1)

[error] 41-41: trailing spaces

(trailing-spaces)


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

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

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

Our policies make our code better.

Reviewers

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

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

Reviewing Your Code

Your reviewer(s) will have the following roles:

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

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

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

Other

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🧹 Nitpick comments (2)
docs/docs/auto-docs/screens/OrganizationTags/OrganizationTagsMocks/variables/MOCKS_NO_MORE_PAGES.md (1)

7-7: Improve type signature readability.

The type signature is complex and hard to read due to excessive escaping of underscores and nested type information. Consider using a code block with proper TypeScript syntax highlighting for better readability.

-`const` **MOCKS\_NO\_MORE\_PAGES**: (\{ `request`: \{ `query`: `DocumentNode`; `variables`: \{ `after`: `undefined`; `first`: `number`; `id`: `string`; `sortedBy`: \{ `id`: `string`; \}; `where`: \{ `name`: \{ `starts_with`: `string`; \}; \}; \}; \}; `result`: \{ `data`: \{ `organizations`: `object`[]; \}; \}; \} \| \{ `request`: \{ `query`: `DocumentNode`; `variables`: \{ `after`: `string`; `first`: `number`; `id`: `string`; `sortedBy`: \{ `id`: `string`; \}; `where`: \{ `name`: \{ `starts_with`: `string`; \}; \}; \}; \}; `result`: \{ `data`: `any`; \}; \})[]
+```typescript
+const MOCKS_NO_MORE_PAGES: Array<{
+  request: {
+    query: DocumentNode;
+    variables: {
+      after: undefined | string;
+      first: number;
+      id: string;
+      sortedBy: {
+        id: string;
+      };
+      where: {
+        name: {
+          starts_with: string;
+        };
+      };
+    };
+  };
+  result: {
+    data: {
+      organizations: object[];
+    } | any;
+  };
+}>
+```
.github/workflows/push-deploy-website.yml (1)

41-41: Good choice switching to Node.js 20.x LTS!

Using Node.js 20.x (LTS) instead of version 22 is a more stable choice for production deployments. However, there's a trailing space at the end of this line that should be removed.

-          node-version: '20.x' 
+          node-version: '20.x'
🧰 Tools
🪛 yamllint (1.35.1)

[error] 41-41: trailing spaces

(trailing-spaces)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0c0fc8e and c91155c.

📒 Files selected for processing (7)
  • .github/workflows/push-deploy-website.yml (2 hunks)
  • docs/docs/auto-docs/screens/OrganizationTags/OrganizationTagsMocks/variables/MOCKS_EMPTY.md (1 hunks)
  • docs/docs/auto-docs/screens/OrganizationTags/OrganizationTagsMocks/variables/MOCKS_ERROR.md (2 hunks)
  • docs/docs/auto-docs/screens/OrganizationTags/OrganizationTagsMocks/variables/MOCKS_ERROR_ERROR_TAG.md (1 hunks)
  • docs/docs/auto-docs/screens/OrganizationTags/OrganizationTagsMocks/variables/MOCKS_NO_MORE_PAGES.md (1 hunks)
  • docs/docs/auto-docs/screens/OrganizationTags/OrganizationTagsMocks/variables/MOCKS_NULL_END_CURSOR.md (1 hunks)
  • docs/docs/auto-docs/screens/OrganizationTags/OrganizationTagsMocks/variables/MOCKS_UNDEFINED_USER_TAGS.md (1 hunks)
✅ Files skipped from review due to trivial changes (4)
  • docs/docs/auto-docs/screens/OrganizationTags/OrganizationTagsMocks/variables/MOCKS_ERROR_ERROR_TAG.md
  • docs/docs/auto-docs/screens/OrganizationTags/OrganizationTagsMocks/variables/MOCKS_NULL_END_CURSOR.md
  • docs/docs/auto-docs/screens/OrganizationTags/OrganizationTagsMocks/variables/MOCKS_UNDEFINED_USER_TAGS.md
  • docs/docs/auto-docs/screens/OrganizationTags/OrganizationTagsMocks/variables/MOCKS_EMPTY.md
🧰 Additional context used
📓 Learnings (2)
docs/docs/auto-docs/screens/OrganizationTags/OrganizationTagsMocks/variables/MOCKS_NO_MORE_PAGES.md (1)
Learnt from: arpit-chakraborty
PR: PalisadoesFoundation/talawa-admin#3158
File: src/screens/OrganizationTags/OrganizationTagsMocks.ts:384-524
Timestamp: 2025-01-15T05:39:30.480Z
Learning: In OrganizationTagsMocks.ts, MOCKS_NULL_END_CURSOR and MOCKS_NO_MORE_PAGES are designed to test UI handling of edge cases where pagination data is inconsistent (e.g., hasNextPage is true but endCursor is null, or next page returns undefined data).
docs/docs/auto-docs/screens/OrganizationTags/OrganizationTagsMocks/variables/MOCKS_ERROR.md (2)
Learnt from: arpit-chakraborty
PR: PalisadoesFoundation/talawa-admin#3158
File: src/screens/OrganizationTags/OrganizationTagsMocks.ts:384-524
Timestamp: 2025-01-15T05:39:30.480Z
Learning: In OrganizationTagsMocks.ts, MOCKS_NULL_END_CURSOR and MOCKS_NO_MORE_PAGES are designed to test UI handling of edge cases where pagination data is inconsistent (e.g., hasNextPage is true but endCursor is null, or next page returns undefined data).
Learnt from: meetulr
PR: PalisadoesFoundation/talawa-admin#2355
File: src/screens/ManageTag/ManageTagMocks.ts:187-269
Timestamp: 2024-11-12T10:40:58.654Z
Learning: In `src/screens/ManageTag/ManageTagMocks.ts`, when mocking data for `USER_TAGS_ASSIGNED_MEMBERS` and `USER_TAGS_MEMBERS_TO_ASSIGN_TO`, it's acceptable for user IDs to overlap because the queries serve different purposes and the overlapping IDs can represent realistic scenarios in tests.
🪛 yamllint (1.35.1)
.github/workflows/push-deploy-website.yml

[error] 41-41: trailing spaces

(trailing-spaces)


[error] 55-55: no new line character at the end of file

(new-line-at-end-of-file)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Analyse Code With CodeQL (javascript)
🔇 Additional comments (2)
docs/docs/auto-docs/screens/OrganizationTags/OrganizationTagsMocks/variables/MOCKS_ERROR.md (2)

9-9: LGTM! Source file line number updated correctly.

The documentation accurately reflects the new location of the MOCKS_ERROR variable definition in the source file.


35-35: Verify the error scenario coverage.

The change from 'orgId' to 'orgIdError' makes the mock's purpose clearer by indicating it's specifically for error testing. This aligns with best practices for mock naming.

Let's verify this is used consistently in error test cases:

✅ Verification successful

The error scenario is properly covered and well-structured. The mock's ID change to 'orgIdError' improves clarity by explicitly indicating its purpose for error testing, and it's properly integrated into the test suite with appropriate error handling setup.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for consistent usage of 'orgIdError' in test files
# Expected: Find test cases that verify error handling using this mock

# Search for test files using this mock
rg -l "MOCKS_ERROR" --glob "**/*.test.{ts,tsx}"

# Search for the specific error scenario usage
rg "orgIdError" --glob "**/*.{ts,tsx}" -C 3

Length of output: 746


Script:

#!/bin/bash
# Check the test file content and error scenario testing
rg -A 10 "MOCKS_ERROR" src/components/TagActions/TagActions.test.tsx

# Look for test descriptions related to error scenarios
rg "describe|it.*error" src/components/TagActions/TagActions.test.tsx

# Check the mock's definition
cat src/screens/OrganizationTags/OrganizationTagsMocks.ts

Length of output: 15217

@tasneemkoushar tasneemkoushar merged commit ca806cc into PalisadoesFoundation:develop-postgres Jan 20, 2025
11 of 13 checks passed
gautam-divyanshu added a commit that referenced this pull request Jan 20, 2025
tasneemkoushar pushed a commit that referenced this pull request Jan 20, 2025
* Revert "push-deploy-website.yml updated (#3364)"

This reverts commit ca806cc.

* Update push-deploy-website.yml
Copy link

codecov bot commented Jan 20, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.75%. Comparing base (f026c00) to head (90f5417).
Report is 2 commits behind head on develop-postgres.

Additional details and impacted files
@@                  Coverage Diff                  @@
##           develop-postgres    #3364       +/-   ##
=====================================================
+ Coverage              8.40%   89.75%   +81.35%     
=====================================================
  Files                   312      335       +23     
  Lines                  8105     8612      +507     
  Branches               1801     1898       +97     
=====================================================
+ Hits                    681     7730     +7049     
+ Misses                 7347      627     -6720     
- Partials                 77      255      +178     
Flag Coverage Δ
combined 89.75% <ø> (?)
vitest 89.75% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

@gautam-divyanshu gautam-divyanshu deleted the deploy branch January 21, 2025 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants