Define Cypress custom script from the inputs about github-action HOT 2 CLOSED

thanks for your review and advice!
Note: the fix is very easy - just add CYPRESS_INCLUDE_TAGS to the env variables

from github-action.

@valyabogatyrova

According to your workflow, you are not really using the functions of the action.

The action executes npm ci if it finds a package-lock.json, so this means there is probably a duplication of your npm install command.

    - name: Install dependencies
      run: npm install

The command option bypasses most functions of the action. See https://github.com/cypress-io/github-action/blob/master/README.md#custom-test-command. So the action has no influence on how your command is executed:

      with:
        command: CYPRESS_INCLUDE_TAGS=${{ inputs.tags_to_include }} npx cypress run ${{ inputs.spec_or_folder }} --browser chrome

This issue list is for bugs and enhancement requests to the action. Your post does not fall into this category however. Also, it looks like you may be using a plug-in to filter your selection, and again, questions for this usage would not belong here.

If you need community support for "how-to" questions you can reach out to the Cypress technical community on Discord
(click on button) where you can find many experienced users. Good luck!

from github-action.