chore(KIT-6121): shallow Quantic E2E checkouts - #8375
Conversation
Quantic E2E jobs only need the checked-out revision and do not inspect repository history. Jira: https://coveord.atlassian.net/browse/KIT-6121
|
|
Tip All tests passed and all changes approved!🟢 UI Tests: 438 tests unchanged |
@coveo/atomic
@coveo/atomic-hosted-page
@coveo/atomic-legacy
@coveo/atomic-react
@coveo/auth
@coveo/bueno
@coveo/create-atomic
@coveo/create-atomic-component
@coveo/create-atomic-component-project
@coveo/create-atomic-result-component
@coveo/create-atomic-rollup-plugin
@coveo/create-ui
@coveo/headless
@coveo/headless-react
@coveo/relay
@coveo/shopify
commit: |
There was a problem hiding this comment.
Pull request overview
This PR updates the Quantic E2E GitHub Actions workflow to use shallow checkouts (fetch-depth: 1) for jobs that don’t rely on repository history, reducing checkout time and data transfer while keeping the change isolated to the CI workflow.
Changes:
- Switched multiple
actions/checkoutsteps from full history (fetch-depth: 0) to shallow checkout (fetch-depth: 1) in the Quantic E2E workflow. - Kept all other E2E setup, SFDX setup, deployment, and Playwright execution steps unchanged.
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Jira
https://coveord.atlassian.net/browse/KIT-6121
Motivation
Quantic E2E jobs only need the checked-out revision and do not inspect repository history. Shallow checkouts reduce checkout time and data transfer without changing E2E setup, deployment, or test behavior.
Changes
.github/workflows/e2e-quantic.yml.Validation
Checklist
chore(<scope>): <description>)