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

Fixed the UserPortal/Home.tsx for develop-userTypeFix branch #1733

Conversation

kanhaiya04
Copy link
Contributor

What kind of change does this PR introduce?

Refactoring

Issue Number:

Fixes #1686

Did you add tests for your changes?

Yes

Snapshots/Videos:

If relevant, did you update the documentation?

Summary

Fixed the UserPortal/Home.tsx screen to support develop-userTypeFix branch of talawa API

Does this PR introduce a breaking change?

No

Other information

Have you read the contributing guide?

Copy link

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if these conditions occur:

  1. The overall code coverage drops below the target threshold of the repository
  2. Any file in the pull request has code coverage levels below the repository threshold
  3. Merge conflicts

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

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

@Cioppolo14
Copy link
Contributor

@kanhaiya04 Please fix the failing checks.

Copy link

codecov bot commented Mar 16, 2024

Codecov Report

Attention: Patch coverage is 73.33333% with 4 lines in your changes are missing coverage. Please review.

Project coverage is 94.81%. Comparing base (56ae7cb) to head (5f7309d).

Files Patch % Lines
src/screens/UserPortal/Home/Home.tsx 42.85% 4 Missing ⚠️
Additional details and impacted files
@@                   Coverage Diff                   @@
##           develop-userTypeFix    #1733      +/-   ##
=======================================================
- Coverage                95.40%   94.81%   -0.60%     
=======================================================
  Files                      138      138              
  Lines                     3721     3721              
  Branches                  1149     1150       +1     
=======================================================
- Hits                      3550     3528      -22     
- Misses                     165      186      +21     
- Partials                     6        7       +1     

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

@palisadoes palisadoes merged commit 5e774ad into PalisadoesFoundation:develop-userTypeFix Mar 17, 2024
6 of 10 checks passed
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.

3 participants