Current situation
The .github/workflows/example-component-test.yml example workflow differs arbitrarily from e2e workflows, for example .github/workflows/example-config.yml
| Item |
Component tests |
E2E test example-config |
| name |
Component Tests |
example-config |
| on: |
[push, workflow_dispatch] |
see below |
| runs-on: |
ubuntu-latest |
ubuntu-22.04 |
E2E action trigger:
on:
push:
branches:
- 'master'
pull_request:
workflow_dispatch:
Suggested changes
- Change 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.
- Change the trigger to be identical to E2E example triggers. This avoids the workflow running on
push to branches other than master.
- Change 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.
Current situation
The .github/workflows/example-component-test.yml example workflow differs arbitrarily from e2e workflows, for example .github/workflows/example-config.yml
E2E action trigger:
Suggested changes
example-component-testso that it appears sorted in the left-hand side of GH Action view together with the E2E tests.pushto branches other thanmaster.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.