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

feat: Removed Requests Screen from Superadmin Panel #1399

Conversation

KshitijTodkar48
Copy link

What kind of change does this PR introduce?
Feature.

Issue Number:

Fixes #1375

Did you add tests for your changes?
No.

Snapshots/Videos:
Screenshot (98)

Summary
This PR solves the issue #1375 by removing the request screen from Super-admin Panel along with its specific corresponding assets.

Does this PR introduce a breaking change?
No.

Have you read the contributing guide?
Yes.

Copy link

github-actions bot commented Jan 7, 2024

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

When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

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

Reviewing Your Code

Your reviewer(s) will have the following roles:

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

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

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

Other

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

Copy link

codecov bot commented Jan 7, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (e04e50a) 97.44% compared to head (66e4137) 97.35%.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1399      +/-   ##
===========================================
- Coverage    97.44%   97.35%   -0.10%     
===========================================
  Files          138      136       -2     
  Lines         3683     3553     -130     
  Branches      1076     1033      -43     
===========================================
- Hits          3589     3459     -130     
  Misses          89       89              
  Partials         5        5              

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

@KshitijTodkar48
Copy link
Author

@palisadoes @rishav-jha-mech @aashimawadhwa, please review the PR and let me know if any changes are required.

@rishav-jha-mech
Copy link
Contributor

LGTM

@palisadoes palisadoes merged commit e6a9c14 into PalisadoesFoundation:develop Jan 10, 2024
9 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