-
Notifications
You must be signed in to change notification settings - Fork 33
Checks "more details" link should link to Rally #202
Comments
This issue has been automatically marked as stale because it has not had recent activity. If you think this issue should stay open, please remove the |
This should stay open. |
This is not something that can be achieved. The link that is generated at the bottom is part of the |
@primetheus The link is settable in the API call: It's just not being set currently. |
Just needs to be added to the GitHub Checks API call you make here: Line 536 in 668b9c1
See reference at https://docs.github.com/en/free-pro-team@latest/rest/reference/checks |
Ah, right. @ineffyble in the event that you have multiple Rally artifacts in the check, what would be the desired endpoint? For example, if a pull request addresses |
This issue has been automatically marked as stale because it has not had recent activity. If you think this issue should stay open, please remove the |
@primetheus If there's a way to redirect to the a page showing a list of those artifacts (possibly by searching for "US8 OR DE22" or such), that would be ideal. Otherwise the first artifact would be fine I think. |
This issue has been automatically marked as stale because it has not had recent activity. If you think this issue should stay open, please remove the |
Commenting. |
This issue has been automatically marked as stale because it has not had recent activity. If you think this issue should stay open, please remove the |
There is a case that we need to consider If |
Is your feature request related to a problem? Please describe.
As a user, when I see a link at the bottom of my Checks summary, which says "View more details on Rally App", I expect that link to take me to Rally, instead of the source code of the GitHub app.
Describe the solution you'd like
Setting
details_url
on the Checks Run object to point to the most specific location in Rally possible (e.g. Artifact, Project, etc, falling back to the Rally dashboard).The text was updated successfully, but these errors were encountered: