## Description By changing the workflow trigger and the way to check for correct labels, we are trying to allow the PR integrations tests to run every time the PR is updated. That means, if you push changes, and the PR already has ok-to-test label, it will rerun the tests based on new changes ## Automation /ok-to-test tags="@tag.Sanity" ### 🔍 Cypress test results <!-- This is an auto-generated comment: Cypress test results --> > [!TIP] > 🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉 > Workflow run: <https://github.com/appsmithorg/appsmith/actions/runs/10296910575> > Commit: c59583ba28c8cdff35a12422b8c73838c6efdc85 > <a href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=10296910575&attempt=1" target="_blank">Cypress dashboard</a>. > Tags: `@tag.Sanity` > Spec: > <hr>Thu, 08 Aug 2024 06:32:48 UTC <!-- end of auto-generated comment: Cypress test results --> ## Communication Should the DevRel and Marketing teams inform users about this change? - [ ] Yes - [ ] No <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Introduced a new job, `checkTestLabel`, to verify the presence of the "ok-to-test" label on pull requests. - Added a new job, `mark-stale`, to mark the Cypress status as stale when the label is absent. - **Improvements** - Updated the `parse-tags` job to run only after the `checkTestLabel` job, enhancing workflow control. - Modified the conditions for executing the `parse-tags` job based on the output of the `checkTestLabel` job. - **Style** - Minor formatting adjustments for job dependencies in the workflow. <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|---|---|---|
| .. | ||
| ISSUE_TEMPLATE | ||
| workflows | ||
| config-test.json | ||
| config.json | ||
| config.yml | ||
| labeler.yml | ||
| pull_request_template.md | ||
| release-drafter-template.yml | ||
| reviewers.yml | ||
| semantic.yml | ||