Pr workflow updated for changed files

[duplixx]

What kind of change does this PR introduce?

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

[palisadoes]

1. Include the eslint configuration file with the desired changes.
2. How do you plan to get whether this works? I don't want to have the same problems repeated. As you and @tasneemkoushar are in the same timezone I'd suggest that you work together on a Zoom call to make sure subsequent PRs work as expected. For example using test PRs immediately after merging.

[palisadoes]

You should be using a different version of the action. Check the GitHub action's website. They are not using V1 anymore

[duplixx]

fixed the changed file issue also added checked file condition

[palisadoes]

@duplixx

1. Is this ready for review?
2. Is the failed test part of the testing of this PR? If so, please restore the files correctly.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (9ff2924) 92.77% compared to head (92c7753) 92.77%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1207   +/-   ##
=======================================
  Coverage   92.77%   92.77%           
=======================================
  Files         134      134           
  Lines        3238     3238           
  Branches      904      904           
=======================================
  Hits         3004     3004           
  Misses        225      225           
  Partials        9        9           

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

[duplixx]

@palisadoes
yeah I have fixed the failing test,and the PR is ready to be reviewed
Thanks!!

[palisadoes]

@anwersayeed please take a look

[anwersayeed]

Looks fine to me.

[palisadoes]

@duplixx

1. This needs to be merged against develop
2. Please resubmit
3. Closing