Pr workflow

[duplixx]

What kind of change does this PR introduce?

Feature added
Added feature to only check the files which have been changed

Issue Number:

Fixes #1117

Did you add tests for your changes?

Snapshots/Videos:

If relevant, did you update the documentation?

Summary

Does this PR introduce a breaking change?

Other information

Have you read the contributing guide?

[github-actions]

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

[noman2002]

Please fix the first comment so that each issue listed automatically closes. The PR_GUIDELINES.md file has details.

Please also fill in the template for the pull request as completely as you can. It greatly helps others searching for code changes in future and helps others understand the summarized rationale for the work you have done

[tasneemkoushar]

@duplixx please resolve the conflicting files.

[duplixx]

@noman2002 @tasneemkoushar fixed the failing issue kindly check !!
thanks!

[palisadoes]

I have to revert this. A line you added is causing these PR tests to fail.

1. https://github.com/PalisadoesFoundation/talawa-admin/actions/runs/7174182075/job/19536488975?pr=1180
2. https://github.com/PalisadoesFoundation/talawa-admin/actions/runs/7170940986/job/19524818348?pr=1178
3. https://github.com/PalisadoesFoundation/talawa-admin/actions/runs/7170548121/job/19523527658?pr=1170

Please resubmit