# Github code links not correct format for forks

**URL:** <https://forum.buildkite.community/t/github-code-links-not-correct-format-for-forks/4440>\
**Category:** Test Analytics\
**Created:** [July 24, 2025, 8:06pm UTC](https://forum.buildkite.community/t/github-code-links-not-correct-format-for-forks/4440 "2025-07-24T20:06:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![IanButterworth](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/ianbutterworth/32/1599_2.png) [@IanButterworth](https://forum.buildkite.community/u/IanButterworth)\
**Post date:** [July 24, 2025, 8:06pm UTC](https://forum.buildkite.community/t/github-code-links-not-correct-format-for-forks/4440/1 "2025-07-24T20:06:49Z")

</div>

The github backlink for tests doesn’t have the correct format for forks.

For branch `ib/bk_path_fix` on my fork `https://github.com/IanButterworth/julia`

On Julia’s Base test suite I get back links like  
`https://github.com/JuliaLang/julia/tree/IanButterworth:ib/bk_path_fix/test/iterators.jl#L651`

for what should be  
`https://github.com/IanButterworth/julia/tree/ib/bk_path_fix/test/iterators.jl#L651`

 ![Screenshot 2025-07-24 at 4.05.55 PM](https://us1.discourse-cdn.com/flex016/uploads/buildkite1/original/2X/0/02727157928d380f84cb2e38bebe568e183db5c3.png)

---

<div class="post-metadata">

**Author:** ![Ola](https://avatars.discourse-cdn.com/v4/letter/o/dbc845/32.png) [@Ola](https://forum.buildkite.community/u/Ola)\
**Post date:** [July 24, 2025, 9:40pm UTC](https://forum.buildkite.community/t/github-code-links-not-correct-format-for-forks/4440/2 "2025-07-24T21:40:52Z")

</div>

Hi Ian,

Thank you for bringing this to our attention. I will pass it across to the internal team.

---

<div class="post-metadata">

**Author:** ![Ola](https://avatars.discourse-cdn.com/v4/letter/o/dbc845/32.png) [@Ola](https://forum.buildkite.community/u/Ola)\
**Post date:** [July 25, 2025, 4:20pm UTC](https://forum.buildkite.community/t/github-code-links-not-correct-format-for-forks/4440/3 "2025-07-25T16:20:10Z")

</div>

Hi again Ian,

I’ve heard back from the team.

After investigating, they have identified what’s happening: Test Engine constructs GitHub links using the pattern `repository_url + branch + file_location`. When tests run from a fork, access to the fork’s repository information is not available within Test Engine - only the branch name and file location are available. This leads to the malformed URLs you’re seeing where the upstream repository URL is combined with a fork-prefixed branch name.

This is a current limitation of how Test Engine processes test execution metadata from forked repositories. The system doesn’t have visibility into whether a branch originates from a fork versus the main repository at the point where these links are generated.

Once tests from your forked branch are merged into the main repository, subsequent test executions will generate correct GitHub links. However, test executions that occurred while the code was still in the fork will retain the incorrect links.

Please let me know if you have any questions or if there’s anything else I can help clarify!