As a developer, I want to have a link automatically generated for verifying a PR on workspaces.openshift.com

[ibuziuk]

Is your task related to a problem? Please describe.

As a developer, I want to have a link automatically generated for verifying a PR on workspaces.openshift.com:

Describe the solution you'd like

• a developer opens a PR to one of the Eclipse Che related repositories
• a link to workspaces.openshift.com is automatically generated in the following format:

https://workspaces.openshift.com#https://github.com/fork/repo/tree/branch e.g.

Describe alternatives you've considered

N/A

Additional context

ideally, the Try it on Eclipse Che hosted by Red Hat link should be generated for every Eclipse Che related repo and every PR

[nickboldt]

Try it on Eclipse Che hosted by Red Hat

Should the link be labelled "Open this PR in Developer Workspace" ? or is "Eclipse Che hosted by Red Hat" the official name?

[ibuziuk]

Eclipse Che hosted by Red Hat is the official name - https://www.eclipse.org/che/docs/che-7/hosted-che/hosted-che/
However, I think we should end up generating just the following badge:

[l0rd]

cc @benoitf

[benoitf]

would be nice to have badge available on shields.io

[l0rd]

would be nice to have badge available on shields.io

There is a simple icon for Che. So we can use something like https://img.shields.io/static/v1?logo=eclipse-che&label=label&message=message. For example:

[ibuziuk]

The action has been created

on: pull_request_target

jobs:
  comment_pr:
    runs-on: ubuntu-20.04
    name: Try the PR on Eclipse Che hosted by Red Hat
    steps:
      - name: Comment PR
        uses: thollander/actions-comment-pull-request@1.0.1
        with:
          message: 'Try the PR on Eclipse Che hosted by Red Hat [![Contribute](https://img.shields.io/badge/Eclipse_Che-Hosted%20by%20Red%20Hat-525C86?logo=eclipse-che&labelColor=FDB940)](https://workspaces.openshift.com#https://github.com/${{ github.event.pull_request.head.repo.full_name }}/tree/${{ github.head_ref }})'
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Each Eclipse Che repo should have it in place. Example eclipse-che/che-docs#2092

NOTE: it is important to use pull_request_target trigger due to the permission issues with forks:

• https://github.blog/2020-08-03-github-actions-improvements-for-fork-and-pull-request-workflows/
• "Resource not accessible by integration" actions/first-interaction#10

[ibuziuk]

Moving to the next sprint. Open questions after the sprint review:

• Custom GitHub action
• GitHub App / marketplace
• Blog post / documentation

[ibuziuk]

The action has been published -
Going to close the issue once redhat-actions/try-in-web-ide#7 is fixed + the docs are published on the https://www.eclipse.org/che/docs/che-7/hosted-che/hosted-che/

[ibuziuk]

Docs PRs have been merged. Closing

• feat: Replacing a customg action with the official 'try-in-web-ide' che-docs#2113
• docs: Add documentation for Try in Web IDE Github action che-docs#2114