Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Harmonize Component test workflow to E2E example workflows #771

Merged

Conversation

MikeMcC399
Copy link
Collaborator

This PR implements the suggestions from issue #770 "Harmonize Component test workflow" regarding the workflow .github/workflows/example-component-test.yml.

  1. It changes the name to example-component-test so that it appears sorted in the left-hand side of GH Action view together with the E2E tests.
  2. It changes the trigger to be identical to E2E example triggers. This avoids the workflow running on push to branches other than master.
  3. It changes the runner to the explicit Ubuntu version ubuntu-22.04. This makes it clearer exactly which version is being used and it aligns it with the default version used in all E2E tests.

Verification

Manually run workflow and ensure it is successful.

Push to a branch other than master and check that the workflow is not triggered.

@jaffrepaul jaffrepaul merged commit ff51ae7 into cypress-io:master Feb 8, 2023
@MikeMcC399 MikeMcC399 deleted the fix/component-test-workflow branch February 9, 2023 07:37
@github-actions
Copy link

🎉 This PR is included in version 5.0.9 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants