@raunaqgupta ,

I think you have some misunderstandings about Push event, Push event will be triggered when you directly push commits to a repository branch or push tags to the repository.
If you wants a workflow runs for pull request, in the YAML file of this workflow, you should set it runs on the events that are related to pull request (such as Pull request event and Pull request review event), not Push event.

For example:

on:
  pull_request:
    types: [assigned, opened, synchronize, reopened]
on:

pull_request_review:

types: [edited, dismissed]

In an opening PR, if you want the subsequent commits pushed to this PR can trigger the workflow, you can set the workflow runs on the activity type  pull_request.synchronize.

on:
  pull_request:
    types: [opened, synchronize]

By default, a workflow only runs when a pull_request’s activity type is opened , synchronize , or reopened. So you can just set it like this:

on: pull_request

It equals the below configuration:

on:
  pull_request:
    types: [opened, synchronize, reopened]

About the path filters on Pull request event, you need to know:

Every time you push a new commit to the opening PR, the Actions app will read all the modified files in this PR from the first to last. Once at least one modified file matches the path filters to trigger the workflow, the workflow will be triggered.

That means, if in the previous commits have modified files match the path filters, although in a subsequent commit you only modify the files that do not match the path filters, the workflow still will be triggered by the activity type  pull_request.synchronize.

In addition, the activity type  pull_request.edited  will trigger the workflow when the users edit somethings on the PR, such as changes the PR’s title, changes the PR’s description, or some other information displayed on the web page of the PR.