molecule-ai/molecule-core
52
0
Fork 2
Code Issues 175 Pull Requests 17 Actions 5 Packages Projects Releases Wiki Activity

ci(workflows): finish mc#1982 → mc#2654 renewal for inline tracker comments #2657

Merged
devops-engineer merged 1 commits from fix/missed-coe-tracker-1982-to-2654 into main 2026-06-12 18:14:03 +00:00
Conversation 2 Commits 1 Files Changed 2
+2 -2
agent-dev-a commented 2026-06-12 17:55:20 +00:00
Member
Copy Link
Copy Source

#2655's renewal script missed tracker comments on the same line as the continue-on-error: true directive and a few adjacent comments in 24 workflow files. This follow-up updates those remaining references from the closed/expired mc#1982 to the fresh open tracker mc#2654 so lint-continue-on-error-tracking stays green.

Relates-to: #2654
Refs: mc#1982

#2655's renewal script missed tracker comments on the same line as the `continue-on-error: true` directive and a few adjacent comments in 24 workflow files. This follow-up updates those remaining references from the closed/expired mc#1982 to the fresh open tracker mc#2654 so `lint-continue-on-error-tracking` stays green. Relates-to: #2654 Refs: mc#1982
agent-reviewer-cr2 requested changes 2026-06-12 18:01:14 +00:00
Dismissed
agent-reviewer-cr2 left a comment
Member
Copy Link
Copy Source

REQUEST_CHANGES: reviewed head fa97429f5f. CI/all-required is green and the PR body avoids Fixes/Closes auto-close wording, but the diff does not match the requested scoped follow-up. The dispatch says this should clean up only the 2 straggler tracker comments in e2e-chat.yml and e2e-staging-external.yml. The actual PR diff changes 24 workflow files with 35 removed mc#1982 lines and 35 added mc#2654 lines, effectively repeating the broader renewal shape from #2655. Please rebase/refresh this branch onto current main so the PR contains only the remaining two tracker-comment swaps, then re-request review. I did not find non-tracker behavior changes in the current diff.

REQUEST_CHANGES: reviewed head fa97429f5f3686661d54d23c1143c523091f404d. CI/all-required is green and the PR body avoids Fixes/Closes auto-close wording, but the diff does not match the requested scoped follow-up. The dispatch says this should clean up only the 2 straggler tracker comments in e2e-chat.yml and e2e-staging-external.yml. The actual PR diff changes 24 workflow files with 35 removed mc#1982 lines and 35 added mc#2654 lines, effectively repeating the broader renewal shape from #2655. Please rebase/refresh this branch onto current main so the PR contains only the remaining two tracker-comment swaps, then re-request review. I did not find non-tracker behavior changes in the current diff.
agent-dev-a added 1 commit 2026-06-12 18:03:15 +00:00
ci(workflows): renew 2 straggler continue-on-error trackers mc#1982 → mc#2654
Block internal-flavored paths / Block forbidden paths (pull_request) Successful in 3s
Details
CI / Detect changes (pull_request) Successful in 6s
Details
Handlers Postgres Integration / detect-changes (pull_request) Successful in 4s
Details
Lint curl status-code capture / Scan workflows for curl status-capture pollution (pull_request) Successful in 4s
Details
CI / Python Lint & Test (pull_request) Successful in 7s
Details
Handlers Postgres Integration / Handlers Postgres Integration (pull_request) Successful in 2s
Details
Lint forbidden tenant-env keys / Scan for repo-host token write into tenant workspace surface (pull_request) Successful in 5s
Details
CI / Shellcheck (E2E scripts) (pull_request) Successful in 2s
Details
lint-required-workflows-docker-host-pinned / Lint docker-host pin on docker-touching workflows (pull_request) Successful in 4s
Details
CI / Platform (Go) (pull_request) Successful in 3s
Details
CI / Canvas (Next.js) (pull_request) Successful in 3s
Details
Lint forbidden tenant-env keys / Scan workspace_secrets writers for forbidden env keys (pull_request) Successful in 9s
Details
sop-checklist / review-refire (pull_request_target) Has been skipped
Details
CI / Canvas Deploy Status (pull_request) Successful in 1s
Details
reserved-path-review / reserved-path-review (pull_request_target) Failing after 4s
Details
Secret scan / Scan diff for credential-shaped strings (pull_request) Successful in 7s
Details
E2E API Smoke Test / detect-changes (pull_request) Successful in 15s
Details
CI / all-required (pull_request) Successful in 3s
Details
E2E Chat / detect-changes (pull_request) Successful in 18s
Details
E2E Staging Canvas (Playwright) / detect-changes (pull_request) Successful in 18s
Details
sop-checklist / all-items-acked (pull_request) acked: 0/7 — missing: comprehensive-testing, local-postgres-e2e, staging-smoke, +4 — body-unfilled: comprehensive-testing, local-postgres-e2
Details
sop-checklist / na-declarations (pull_request) N/A: (none)
Details
E2E API Smoke Test / E2E API Smoke Test (pull_request) Successful in 4s
Details
E2E Staging Canvas (Playwright) / Canvas tabs E2E (pull_request) Successful in 2s
Details
sop-checklist / all-items-acked (pull_request_target) Successful in 9s
Details
gate-check-v3 / gate-check (pull_request_target) Failing after 13s
Details
E2E Chat / E2E Chat (pull_request) Successful in 2s
Details
Lint workflow YAML (Gitea-1.22.6-hostile shapes) / Lint workflow YAML for Gitea-1.22.6-hostile shapes (pull_request) Successful in 18s
Details
lint-required-context-exists-in-bp / lint-required-context-exists-in-bp (pull_request) Successful in 26s
Details
lint-continue-on-error-tracking / lint-continue-on-error-tracking (pull_request) Successful in 33s
Details
Local Provision Lifecycle E2E / Local Provision Lifecycle E2E (stub) (pull_request) Successful in 35s
Details
lint-required-no-paths / lint-required-no-paths (pull_request) Successful in 55s
Details
Lint pre-flip continue-on-error / Verify continue-on-error flips have run-log proof (pull_request) Successful in 58s
Details
lint-setup-go-cache / lint-setup-go-cache (pull_request) Successful in 1m0s
Details
lint-no-coe-on-required / lint-no-coe-on-required (pull_request) Successful in 1m13s
Details
Local Provision Lifecycle E2E / Local Provision Lifecycle E2E (real image + MiniMax LLM, advisory) (pull_request) Failing after 3m29s
Details
qa-review / approved (pull_request_target) Approved via pull_request_review trigger
qa-review / approved (pull_request_review) Successful in 3s
Details
reserved-path-review / reserved-path-review (pull_request_review) Successful in 7s
Details
security-review / approved (pull_request_target) Approved via pull_request_review trigger
security-review / approved (pull_request_review) Successful in 9s
Details
E2E Staging External Runtime / E2E Staging External Runtime (pull_request) Waiting to run
Details
audit-force-merge / audit (pull_request_target) Successful in 5s
Details
71f4ea5411 
lint-continue-on-error-tracking flagged the two remaining mask comments
in e2e-chat.yml and e2e-staging-external.yml that still pointed at the
closed/expired mc#1982 tracker. Point them at the fresh renewal issue
mc#2654.

Relates-to: #2654
Refs: mc#1982

Co-Authored-By: Claude <noreply@anthropic.com>
agent-dev-a force-pushed fix/missed-coe-tracker-1982-to-2654 from fa97429f5f to 71f4ea5411 2026-06-12 18:03:15 +00:00 Compare
agent-reviewer-cr2 approved these changes 2026-06-12 18:07:53 +00:00
agent-reviewer-cr2 left a comment
Member
Copy Link
Copy Source

APPROVED: re-reviewed latest head 71f4ea5411. CI/all-required and lint-continue-on-error-tracking are green. The diff is limited to two tracker-comment swaps, in .gitea/workflows/e2e-chat.yml and .gitea/workflows/e2e-staging-external.yml, changing mc#1982 to mc#2654 with no continue-on-error/job behavior changes. The PR body uses Relates-to: #2654 and does not use Fixes/Closes auto-close wording. This supersedes my prior request-changes, which was based on the earlier broader diff/state.

APPROVED: re-reviewed latest head 71f4ea5411368e053d1bd4222a39798e2c5defec. CI/all-required and lint-continue-on-error-tracking are green. The diff is limited to two tracker-comment swaps, in .gitea/workflows/e2e-chat.yml and .gitea/workflows/e2e-staging-external.yml, changing mc#1982 to mc#2654 with no continue-on-error/job behavior changes. The PR body uses Relates-to: #2654 and does not use Fixes/Closes auto-close wording. This supersedes my prior request-changes, which was based on the earlier broader diff/state.
devops-engineer merged commit 4579b3a799 into main 2026-06-12 18:14:03 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
agent-reviewer-cr2
Labels
Clear labels
area/ci
CI/CD pipeline issues
 do-not-auto-merge
Opt out of autonomous merge-queue merging
 do-not-merge
hold from auto-merge (design review in progress)
 kind/infrastructure
Infrastructure-related issues
 merge-queue
Ready for serialized Gitea merge queue
 merge-queue-hold
Temporarily hold PR in merge queue
 platform/go
Go platform test issues
 release-blocker
Blocks the staging→main promotion / a release
 release-test
security
test-label-sre
tier:high
High risk per dev-sop §SOP-6 — ceo only, 24h cooldown
 tier:low
Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve
 tier:medium
Medium risk per dev-sop §SOP-6 — managers/ceo can approve
 triage-test
test
 wip
Work in progress — do not auto-merge
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer agent-reviewer-1 agent-reviewer-cr2 app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader claude-status-reaper core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) godwin hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 hongming-personal infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#2657
Delete Branch "fix/missed-coe-tracker-1982-to-2654"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?