feat: add scheduled caller for CommonalitiesTest regression sweep - #707
Open
hdamker wants to merge 1 commit into
Open
feat: add scheduled caller for CommonalitiesTest regression sweep#707hdamker wants to merge 1 commit into
hdamker wants to merge 1 commit into
Conversation
Moves the daily schedule from tooling's caller here so it lives with the repository it tests; the reusable pipeline itself stays in tooling.
hdamker
requested review from
PedroDiez,
bigludo7,
eric-murray,
jlurien and
rartych
as code owners
September 3, 2026 06:43
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.
What type of PR is this?
What this PR does / why we need it:
Adds the scheduled trigger for CommonalitiesTest's regression sweep —
a standing validation signal on unreleased Commonalities content,
running daily against real API-repository layouts. See
CommonalitiesTest's README for what it tests and why:
https://github.com/camaraproject/CommonalitiesTest#readme
The sync/cherry-pick/sweep pipeline itself stays in
camaraproject/tooling; this just moves the schedule's home there to
here, alongside a companion PR on tooling that drops it from tooling's
own caller (kept for ad hoc dispatch only).
Which issue(s) this PR fixes:
Part of #706
Does this PR introduce a breaking change?
Special notes for reviewers:
No change to Commonalities' own API content or any other workflow.
Changelog input
Additional documentation
This section can be blank.