cypress-io / github-action

GitHub Action for running Cypress end-to-end & component tests

Home Page:https://on.cypress.io/guides/continuous-integration/github-actions

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

pnpm workspaces workflow shows "no status"

MikeMcC399 opened this issue ยท comments

The badge for the new workflow https://github.com/cypress-io/github-action/blob/master/.github/workflows/example-start-and-pnpm-workspaces.yml in the README > pnpm workspaces is currently showing "no status" when it should be showing "passing":

image

The markdown code for the badge is formulated in the same way as other badges which work.

[![pnpm workspaces example](https://github.com/cypress-io/github-action/workflows/example-start-and-pnpm-workspaces/badge.svg?branch=master)](.github/workflows/example-start-and-pnpm-workspaces.yml)

pnpm workspaces example

[![Yarn workspaces example](https://github.com/cypress-io/github-action/workflows/example-start-and-yarn-workspaces/badge.svg?branch=master)](.github/workflows/example-start-and-yarn-workspaces.yml)

Yarn workspaces example

If the branch name query parameter ?branch=master is removed, then the status shows correctly. This should be equivalent because master is the repo's default branch and with no branch specified the status badge is supposed to show the default branch.

[![pnpm workspaces example](https://github.com/cypress-io/github-action/workflows/example-start-and-pnpm-workspaces/badge.svg?branch=master)](.github/workflows/example-start-and-pnpm-workspaces.yml)

pnpm workspaces example

At the moment I don't understand the reason for the issue. I'm going to wait to see if it sorts itself out.

The status badges do not conform to the documentation Adding a workflow status badge.

actions and .yml are missing. When corrected the badge works:

pnpm workspaces example

It's not clear why other badges appear to be working although they don't use the correct syntax. Possibly they are showing an out-of-date cached status.

Plan

Modify all badges to conform to the current documentation.

๐ŸŽ‰ This issue has been resolved in version 6.7.0 ๐ŸŽ‰

The release is available on:

Your semantic-release bot ๐Ÿ“ฆ๐Ÿš€