Repository navigation
ci: report required checks on push, pull request, and merge queue - #75
Closed
jonbeckman wants to merge 2 commits into
Closed
jonbeckman wants to merge 2 commits into
jonbeckman wants to merge 2 commits into
Conversation
Add merge_group triggers for the checks that gate pull requests, and move CodeQL to a workflow that keeps the existing Analyze check names. Release preview reports success outside pull requests. release.yml stays unchanged. Co-authored-by: Jonathan Beckman <jonathantbeckman@gmail.com>
Contributor
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: 56b238b4-097c-4310-821f-dc086b100622) |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Approved. Cursor Bugbot was skipped (usage limit), so that signal was omitted, and no approval policy requires human review. This automation had no prior approval on the current head.
Sent by Cursor Approval Agent: Pull Request Router and Approver
Contributor
TegamiThis repository uses Tegami to manage releases. When your changes affect published packages, add a changelog file under Create a changelog → · Changelog format Release preview
This PR does not add changelog files. Pending changelogs from other branches are included in the preview above. Run Managed by Tegami. |
Contributor
🟢 e2e solzero-core: 33 passed10 agent steps · 33 model calls · 64.8k tokens · $0.0155 All 33 tests in 13 files
e2e 0.17.0 · 4m 18s · local-cloudflare · run artifacts |
Keep master's Nub 0.9.6 setup and current action references. Keep merge_group triggers for the required checks and the CodeQL advanced setup. Reference CodeQL actions by major tag. Co-authored-by: Jonathan Beckman <jonathantbeckman@gmail.com>
Contributor
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: 6bd84006-9190-415c-9f23-66c1b4e85729) |
This was referenced Nov 1, 2026
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
Required pull request checks now run on
pushtomaster, onpull_request, and onmerge_group(checks_requested). Check context strings are unchanged.DeployandDeploy Previewstay disabled. This pull request does not add a deploy trigger, aprodenvironment, or a secret-scope change.release.ymlis untouched, so it does not conflict with #74.This change has no product behavior. It uses
release:none. Operators still publish with Tegami asvX.Y.Ztags. No.tegami/entry.Required check contexts
These are the strings GitHub shows. No context was renamed.
Analyze (javascript-typescript)andAnalyze (actions)are literal job names. They match the previous default-setup contexts and do not come from a matrix value.Repository validation.github/workflows/validate.yml)validateCloudflare end-to-end flows.github/workflows/validate.yml)e2eBuild release preview.github/workflows/tegami-pr-preview.yml)previewAnalyze (javascript-typescript).github/workflows/codeql.yml)analyze-javascript-typescriptAnalyze (actions).github/workflows/codeql.yml)analyze-actionsactionlint.github/workflows/validate.yml)validate(reviewdog check from “Lint GitHub Actions workflows”)CodeQLBuild release previewbuilds the Tegami preview onpull_requestonly. Onpushandmerge_groupthe same job reports success and skips the preview steps, so the required check is not left pending.Cloudflare end-to-end flowsalready runs when the event is notpull_request, so a merge group runs it. The checkout uses the pull request head SHA when that field is present, andgithub.shafor push, merge group, and dispatch. The job does not read a pull request number. Fork pull requests still skip it.Workflows with
merge_groupThese workflows now include
merge_group: types: [checks_requested]for base branchmaster:.github/workflows/validate.yml.github/workflows/tegami-pr-preview.yml.github/workflows/codeql.ymlThese workflows do not get
merge_group. They are not required pull request gates:.github/workflows/deploy.ymland.github/workflows/preview.ymlstay disabled. Invert guards remain..github/workflows/release.ymlstill runs fromworkflow_runafter Validate onmaster..github/workflows/agent-container-images.ymlstaysworkflow_call/workflow_dispatch..github/workflows/tegami-pr-comment.ymlstill posts only after a successful pull request preview.Release tag pattern
Existing tags are
v1.5.0,v1.6.0,v1.7.0, andv1.8.0. Tegami publishes an immutablevX.Y.Ztag (v*).Prod promote is not applicable
SolZeroAI/platform is public OSS. GitHub Actions must never deploy preview or prod.
DeployandDeploy Previewstay disabled. This pull request does not addrelease: publishedor any other deploy trigger, and it does not add aprodenvironment.CodeQL default setup
.github/workflows/codeql.ymlis advanced setup so CodeQL can run onmerge_group. Default setup (dynamic/github-code-scanning/codeql) cannot. Disable default setup when this workflow is onmaster. GitHub rejects an advanced setup upload while default setup stays enabled.This run could not change that repository setting.
actionlint on
release.ymlThe cache-call finding on
masteris already fixed..github/workflows/release.ymlsetscache-mode: readon the agent-container-images call (from #70). actionlint 1.17.0, the version CI runs, reports no findings on that file. This pull request does not editrelease.yml.Validation
nub run typechecknub run lint(existing warnings, 0 errors)nub run formatnub run config:checkandnub run testwere not run. This change is workflow and docs only.Checklist
.tegami/release entry, or explained why this pull request usesrelease:none.nub run config:check,nub run typecheck,nub run lint,nub run format, andnub run test.THIRD_PARTY_NOTICES.mdfor new third-party code or separately licensed assets.nub run typecheck,nub run lint, andnub run formatpassed.nub run config:checkandnub run testwere not run. No third-party code was added.Note
Low Risk
Workflow and documentation only; no application runtime changes. Operators must disable CodeQL default setup when merging to avoid upload conflicts.
Reviewed by Cursor Bugbot for commit 89bfdf7. Bugbot is set up for automated code reviews on this repo. Configure here.