I imagine you’re trying to reproduce the equivalent of:

  <a href="https://github.com/github/docs/commit/8e25c7666ce5b9576d6aa1e982a58285f5f90ef9" target="_blank" rel="noopener nofollow ugc">github.com/github/docs</a>

<div class="github-info">
  <div class="date">
    committed <span class="discourse-local-date" data-format="ll" data-date="2022-01-04" data-time="19:28:53" data-timezone="UTC">07:28PM - 04 Jan 22 UTC</span>
  </div>

  <div class="user">
    <a href="https://github.com/Octomerger" target="_blank" rel="noopener nofollow ugc">
      <img alt="Octomerger" src="https://user-images.githubusercontent.com/2119212/181071368-d9e759d5-20d8-4626-902b-d4cca65b33c0.jpeg" class="onebox-avatar-inline" width="20" height="20">
      Octomerger
    </a>
  </div>

  <div class="lines" title="changed 0 files with 0 additions and 0 deletions">
    <a href="https://github.com/github/docs/commit/8e25c7666ce5b9576d6aa1e982a58285f5f90ef9" target="_blank" rel="noopener nofollow ugc">
      <span class="added">+0</span>
      <span class="removed">-0</span>
    </a>
  </div>
</div>

Screenshot_20220105-1051331080×267 53.5 KB

It’s doable. There are magical APIs for it

Actually i have a use case where we wanted to capture all the PR’s went in a release.
Example :
i have a repo A where i created a PR named PR-1 which is now merged to master branch of repo A and there is a target repo B where release happens , now from master branch of A changes are merged to master of B repo and after some day there is a release in B say after 5 days on that day i need to find all the PR’s went to this release. All the intial PR’s like (PR-1).

can we add custom fields in Pull Request?

Not really. You can use labels to add very limited metadata.

You can also stick stuff into the description in a structured format.

<!--
data:{"key":"value"}
-->

And then retrieve it.

Great can we propagate the data fields if our PR is merged and propagated to another repo.

Normally if you want something to propagate, you’d stick it into a commit, either in git metadata, git commit message, or normal files…