Decide what information about issue forks to show on issue page on Drupal.org, implement
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3071681. -->
Reported by: [drumm](https://www.drupal.org/user/3064)
>>>
<p>Once <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/drupalorg/-/work_items/3071473" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/drupalorg/-/work_items/3071473</a></span> is done, issues on Drupal.org should have some information about activity in the issue’s fork. Once we are on to <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/drupalorg/-/work_items/2205815" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/drupalorg/-/work_items/2205815</a></span>, merge-request-related activity will be figured out in a followup issue.</p>
<p>At minimum, I imagine this would be a note of which branches exist. At maximum, every commit.</p>
<p>I suspect we should be more minimal here. Until the merge request is open, the analogue of posting a patch, every commit is essentially a draft. The history will be available by clicking over to the repository on git.drupalcode.org.</p>
<p>For implementation, this might be pulled in client-side from GitLab’s API, pulled in server-side from GitLab’s API, or pushed to Drupal.org’s DB by a post-commit hook.</p>
<h3>User interface changes</h3>
<p><strong>Fork information</strong></p>
<ul>
<li>Issue fork name ✅ done</li>
<li>Clone / get push access ✅ done</li>
<li><span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/drupalorg/-/work_items/3071474" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/drupalorg/-/work_items/3071474</a></span></li>
<li>Link to detailed instructions ✅ done</li>
<li><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupalorg/issues/3071746" title="Status: Closed (fixed)">#3071746: Create branch in issue fork button?</a></span></li>
</ul>
<p><strong>For each active branch</strong></p>
<ul>
<li>Branch name ✅ done</li>
<li>Compare link, with nearest branch that exists in the project - As in a core 9.0.x-dev issue will usually be compared with 9.0.x, where it was branched from. The same issue might have other branches made from 9.1.x/8.9.x/etc. ✅ done</li>
<li>Last commit made ✅ done</li>
<li>Link to merge request raw diff, when available
</li><li>Likely, if possible - How many comments have been made on lines of code in the branch’s commits, linking to a listing of those comments.</li>
<li>Maybe - Who has committed on the branch. (The most recent committer is straightforward to pull in.)</li>
<li>Maybe - When the last commit made on the branch.</li>
<li>Maybe, less likely - How many commits were made on the branch.</li>
</ul>
issue