Repository navigation
ci: trigger dtq-dev-767-base daily UI tests, drop stale skip entries - #1728
Merged
Merged
Conversation
dtq-dev-9-base's CI workflow files were deleted on that branch (cleanup commit b4f55e3), so dispatching playwright-tests.yml against it has been failing with "Workflow does not have workflow_dispatch trigger" since 2026-10-31. Replace it with dtq-dev-767-base, which carries the ported workflow. Also drop customer/palo-docker, customer/palo-docker-rebase and customer/palo-docker-typo-fix from SKIP_BRANCHES since those branches no longer exist. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
dtq-dev-9-basewithdtq-dev-767-basein the dailytrigger-ui-tests.ymlbranch list.customer/palo-docker,customer/palo-docker-rebaseandcustomer/palo-docker-typo-fixfromSKIP_BRANCHES— those branches no longer exist on origin.Why
The daily scheduled run of this workflow has been failing every night since 2026-10-31 (visible in Actions history). Root cause: commit
b4f55e36bc("cleanup") deleted.github/workflows/playwright-tests.yml(anddeploy.yml,trigger-ui-tests.yml, etc.) from thedtq-dev-9-basebranch on 2026-10-30. Sincegh workflow run --ref <branch>requires theworkflow_dispatchtrigger to exist in the workflow file on that ref, dispatching againstdtq-dev-9-basenow fails withHTTP 422: Workflow does not have 'workflow_dispatch' trigger.dtq-dev-767-basecarries the ported-over workflow files and is becoming the replacement fordtq-dev-9-basedeploys, so it's swapped in instead.Test plan
Trigger UI Tests for All Customer Branchesworkflow (workflow_dispatch) and confirm it dispatchesplaywright-tests.ymlsuccessfully againstdtq-dev-767-base.🤖 Generated with Claude Code