Expand Pull Request status and title from GitHub check

[perseoGI]

Select Topic Area

Question

Body

I would like to know if it is possible to render PR links in a GitHub check as can be done from a Pull Request comment, using
#<pr-num>
or #<issue-num>
or even the links
Example of Pull Request commet with PR links rendered propertly:

Example of a GitHub Check which does not expand the name and the status of the linked PR/Issue:

As it can be seen, it do expands the content on hover. I'll like to be always expanded.

I've tried putting the markdown text inside the checks.output.summary and checks.output.text with the same results.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[perseoGI]

Any update?

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[perseoGI]

Not stale!
Is there any update?

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[perseoGI]

Can anyone help?

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[perseoGI]

Still not addressed

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[perseoGI]

Not stale!

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[brocked200]

Working!

[perseoGI]

Working on it or is it working now?

[Rknilkant]

Hi there @perseoGI ,

Great question — this is something that many CI/CD tool integrations and GitHub App developers run into.

Currently, GitHub Checks API does support Markdown, but it does not fully render PR or issue references (like #123 or full links) the same way as PR comments do.

What works:
Basic Markdown like bold, italics, links, lists, etc., is rendered in checks.output.text and checks.output.summary.

Hover previews do work for issue/PR links, as you’ve noticed.

What doesn’t work:
GitHub does not auto-expand PR or issue links to their full titles or status (as seen in comments).

References like #123 or https://github.com/owner/repo/pull/123 will not be expanded inline in Checks output.

Workaround:
If context is important, you can manually format the Markdown to include PR titles or brief descriptions yourself, like:
Related PR: #123 - Fix login bug

This will render as a clickable link in the check output, though it won’t auto-expand or show PR status.

You’re not alone in wanting this — I’d recommend posting a feature suggestion in GitHub Feedback to request richer link rendering in GitHub Checks.

Hope this helps clarify things!

Best,
Rknilkant

[perseoGI]

Greetings @Rknilkant,
Thank you very much for your response!
I understand your suggestion of adding context manually in the markdown.
The thing is that we would like to have the information dynamically updated. PR titles may vary and the status may also change so having the possibility of rendering them dynamically will be excellent!

I’d recommend posting a feature suggestion in GitHub Feedback to request richer link rendering in GitHub Checks.

Where is this page exactly located?
I thought this GitHub discussion page was the correct place to request features!

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[perseoGI]

Not stale!

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[perseoGI]

Not stale

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[perseoGI]

Not stale

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[dylanjha]

@perseoGI thanks for opening this. I am running into this too, and I'm bummed that GH markdown does not support this feature

[perseoGI]

Let's see if GitHub team could take a look at this feature

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[perseoGI]

Not stale!

[rootNyx404]

I found a temporary workaround for this issue.

Currently GitHub Checks output does not support fully expanded PR references like normal Pull Request comments.
Instead of using only #PR-number, using a Markdown link with the PR title makes the output more readable.

Example:

[PR #10 - Update zlib conanfile.py](https://github.com/OWNER/REPO/pull/10)

It does not create the same expanded preview card, but it works well as a readable alternative until GitHub adds native support for expanded references inside Checks output.

[perseoGI]

Thank you, yes, this is a simple workaround.
But the issue with this is that if for some reason, the PR title changes, the GH check PR title wont be updated.
It is not super important but that is why we want dynamic expansions.

[rootNyx404]

That makes sense.
A static Markdown link is only a partial workaround because it loses the automatic synchronization with the actual PR metadata.

Dynamic expansion would definitely be more useful since it would:

• automatically reflect PR title changes
• show current PR status/state
• keep GitHub Checks output consistent with normal PR comments

Hopefully GitHub eventually exposes the same rendering behavior inside Checks output as well.

[perseoGI]

I hope so too!

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬