Release: develop -> main - #1417
Merged
Merged
Conversation
The outcome form already uses the logged-in staff verified name. Remove the unused clerks-list helper and the e2e seed that only existed to feed that list.
github-actions
Bot
requested review from
TaprootFreak and
davidleomay
as code owners
August 20, 2026 18:49
* Skip PR CI on drafts unless the ci label is set Ready for review dispatches the suite once and adds ci. If ci or ci:full is already present, ready does not start a second run. * Point CodeQL pull-request and push triggers at main The other PR workflows already use main as the release branch; master is leftover and would skip CodeQL on PRs into main. * Convert failed Ready kicks to draft via GraphQL REST has no convert-to-draft endpoint. Use convertPullRequestToDraft so a failed dispatch cannot leave skipped checks on a mergeable PR. * Require GraphQL convert-to-draft to confirm isDraft A parse error or missing payload must not look like a successful revert. * Align e2e docs with draft CI skip and bare dispatch The harness README and test-architecture still said the job always runs and that every workflow_dispatch is a full suite. * Note draft CI skip in the test-architecture layer table * Format the test-architecture table for Prettier * Do not default e2e api_ref on workflow_dispatch A Ready kick only passes pr_number and base_ref. A YAML default of develop would look like an explicit pin and skip the API bootstrap fallback when the guard is not on develop yet. * Skip full-stack E2E on develop unless ci:full A standard develop PR must finish CI in under 10 minutes. The job still runs (mode=none, no checkout, no stack). Full suite is ci:full, main, or a bare workflow_dispatch. * Clarify that the e2e route gate runs only on a full stack A standard develop PR without ci:full does not bring the stack up, so CI cannot fail a missing route claim on that path. * Start full-stack E2E only after Build and test E2E is called from PR CI after unit tests succeed so it cannot start while tests are still queued. Develop without ci:full remains a no-op. * Document that Ready dispatches PR CI, not e2e-stack * Clarify e2e-stack scope comments for workflow_call full input
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.
Automatic Release PR
This PR was automatically created after changes were pushed to develop.
Commits: 1 new commit(s)
Checklist