Skip to content

fix(lastcode): run daily Intel dispatch on GitHub - #115

Merged
lastobelus merged 1 commit into
lastcode/mainfrom
lastcode/daily-intel-hosted-lock
Aug 27, 2026
Merged

lastobelus merged 1 commit into
lastcode/mainfrom
lastcode/daily-intel-hosted-lock

Conversation

@lastobelus

Copy link
Copy Markdown
Owner

The new daily Intel dispatcher runs on GitHub Ubuntu, but it reused the local Project Action’s Darwin-only request-file lock and therefore failed before dispatching its first build.

This keeps the local action unchanged and lets only the hosted daily job rely on its existing GitHub Actions concurrency group. Exact tag/commit selection, unique dispatch correlation, internal waiting, and release verification are unchanged. Focused coverage proves both hosted selection and execution use the no-op local lock while the workflow remains serialized.

Part of #103.

Built with GPT-5.6 in the Codex harness.

@lastobelus

ghost commented Aug 27, 2026 •

Copy link
Copy Markdown
Owner Author

@codex review

@chatgpt-codex-connector

ghost commented Aug 27, 2026

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Can't wait for the next one!

Reviewed commit: 849cdc740a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@lastobelus
lastobelus merged commit 4dc0c61 into lastcode/main Aug 27, 2026
@lastobelus
lastobelus deleted the lastcode/daily-intel-hosted-lock branch August 27, 2026 23:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant