docs(e2e): describe the trigger set the workflow actually has - #483
Merged
Conversation
The CI section still described stage 1 — nightly, e2e/** and manual — and said the nightly could not start until the suite landed on develop. Both are now out of date: pushes to develop, release/** and rc/** trigger a run, and the suite has been on develop since #476. Also records why there are no path filters, and why the set stops short of feature branches, so the next person to consider changing either has the reasoning rather than having to rediscover it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
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
1 participant
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.
Docs only, and doubling as a live check that a normal merge to
developstarts the suite — the last one that proved it was #482, which changed the workflow file itself and so was arguably a special case.The CI section still described stage 1 (nightly,
e2e/**, manual) and claimed the nightly could not start until the suite landed ondevelop. Both are now out of date.Also records two decisions so the next person has the reasoning rather than rediscovering it: why there are no path filters, and why the push set stops short of feature branches.
🤖 Generated with Claude Code