<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=27903) </details> <!--IssueSummary end--> ### Problem to solve When using GitLab Merge Requests, [reports](https://docs.gitlab.com/ee//ci/yaml/README.html#artifactsreports) such as tests (e.g., [`artifacts:reports:junit`](https://docs.gitlab.com/ee//ci/yaml/README.html#artifactsreportsjunit)) and performance ([`artifacts:reports:performance`](https://docs.gitlab.com/ee//ci/yaml/README.html#artifactsreportsperformance-premium)) are posted to the Merge Request, but are not visible from the CI page (see, e.g., gitlab-ce#49212). When using [GitLab CI/CD with GitHub](https://about.gitlab.com/solutions/github/), there is no GitLab Merge Request and this information is not posted to the GitHub Pull Request. This severely limits the audience of GitLab CI/CD for projects hosted at GitHub, and since this limitation isn't documented, gives a poor impression of GitLab CI/CD relative to other services. ### Intended users Anyone who uses [GitLab CI/CD with GitHub](https://about.gitlab.com/solutions/github/) or other [CI/CD for external repositories](https://docs.gitlab.com/ee/ci/ci_cd_for_external_repos/). ### Further details This is a standard feature offered by all other CI/CD platforms, including GitLab CI/CD for GitLab repositories. ### Proposal * Make all `artifacts:reports` reachable from the CI interface; see gitlab-ce#49212. * Add reports to external pull requests (GitHub, Bitbucket) to the extent they support doing so. ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)? --> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> ### Testing <!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further guidelines: https://about.gitlab.com/handbook/engineering/quality/guidelines/test-engineering/ --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### Links / references