Chapter 5. Use OpenShift Dev Spaces in team workflow

Procedure

1. Open the feature branch to review in OpenShift Dev Spaces. A clone of the branch opens in a workspace with tools for debugging and testing.
2. Check the pull or merge request changes.

3. Run your desired debugging and testing tools:

   • Run a linter.
   • Run unit tests.
   • Run the build.
   • Run the application to check for problems.
4. Navigate to the UI of your Git provider to leave a comment and pull or merge your assigned request.

Procedure

1. In the GitHub repository, create a .github/workflows directory if it does not exist already.

2. Create an example.yml file in the .github/workflows directory with the following content:

   name: Try in Web IDE example
   
   on:
     pull_request_target:
       types: [opened]
   
   jobs:
     add-link:
       runs-on: ubuntu-20.04
       steps:
         - name: Web IDE Pull Request Check
           id: try-in-web-ide
           uses: redhat-actions/try-in-web-ide@v1
           with:
             # GitHub action inputs
   
             # required
             github_token: ${{ secrets.GITHUB_TOKEN }}
   
             # optional - defaults to true
             add_comment: true
   
             # optional - defaults to true
             add_status: true

   This code snippet creates a workflow named Try in Web IDE example, with a job that runs the v1 version of the redhat-actions/try-in-web-ide community action. The workflow is triggered on the pull_request_target event, on the opened activity type.

3. Optional: Configure the activity types from the on.pull_request_target.types field to customize when the workflow triggers. Activity types such as reopened and synchronize can be useful.

   For example:

   on:
     pull_request_target:
       types: [opened, synchronize]

4. Optional: Configure the add_comment and add_status GitHub action inputs within example.yml. These inputs customize whether comments and status checks are added.