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 #1378

Conversation

KshitijTodkar48
Copy link
Contributor

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 5, 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

@@ -5,7 +5,6 @@ import { useHistory } from 'react-router-dom';
import { ReactComponent as AngleRightIcon } from 'assets/svgs/angleRight.svg';
import { ReactComponent as LogoutIcon } from 'assets/svgs/logout.svg';
import { ReactComponent as OrganizationsIcon } from 'assets/svgs/organizations.svg';
import { ReactComponent as RequestsIcon } from 'assets/svgs/requests.svg';
Copy link
Contributor

Choose a reason for hiding this comment

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

Check whether this icon is used somewhere else or not, if not then remove this svg file too

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ok, I'll do that.

@rishav-jha-mech
Copy link
Contributor

rishav-jha-mech commented Jan 5, 2024

@KshitijTodkar48 you need to remove the test for Requests from LeftDrawer.test.ts too

@palisadoes
Copy link
Contributor

Please fix the conflicting files

@KshitijTodkar48
Copy link
Contributor Author

@rishav-jha-mech @palisadoes I am opening a new PR for this issue.

@KshitijTodkar48 KshitijTodkar48 deleted the feat/Remove-Requests-Screen branch January 7, 2024 12:25
@palisadoes
Copy link
Contributor

Please reopen this PR. There is no reason to close it

  1. We have already signed reviewers
  2. It's against the correct branch
  3. The history of activities to help out reviewers is easily visible

Please be considerate of our volunteers time

Do not open another one. Reopen this one.

@KshitijTodkar48
Copy link
Contributor Author

KshitijTodkar48 commented Jan 7, 2024

@palisadoes , Very sorry for the inconvenience, but I have already opened a new PR for this. While solving the conflicts, I messed up some git-workflow. So just to be on safer side, I deleted that branch completely. I'll take care to not repeat such an action in the future. Please let it go this time.

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