Skip to content

ci: Added a CI workflow the fork can run. - #12

Closed
moetemp wants to merge 1 commit into
devfrom
moe/fork-ci
Closed

moetemp wants to merge 1 commit into
devfrom
moe/fork-ci

Conversation

@moetemp

@moetemp moetemp commented Sep 15, 2026

Copy link
Copy Markdown
Collaborator

This PR adds .github/workflows/test-fork.yml.

Upstream's test workflow asks for Blacksmith runners this fork cannot schedule, so every run of it here is cancelled with no runner, on every branch including dev. Nothing in the fork had a CI signal. The new workflow typechecks every package (concurrency capped, so tsgo is not killed for memory on a hosted runner) and runs the core and temporal unit suites.

First of a stack; each branch above it adds one thing to the Temporal executor.

@github-actions

Copy link
Copy Markdown

This PR doesn't fully meet our contributing guidelines and PR template.

What needs to be fixed:

  • PR description is missing required template sections. Please use the PR template.

Please edit this PR description to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

@github-actions

Copy link
Copy Markdown

Hey! Your PR title ci: Added a CI workflow the fork can run. doesn't follow conventional commit format.

Please update it to start with one of:

  • feat: or feat(scope): new feature
  • fix: or fix(scope): bug fix
  • docs: or docs(scope): documentation changes
  • chore: or chore(scope): maintenance tasks
  • refactor: or refactor(scope): code refactoring
  • test: or test(scope): adding or updating tests

Where scope is the package name (e.g., app, desktop, opencode).

See CONTRIBUTING.md for details.

Upstream's test workflow asks for runners this fork cannot schedule, so every run here was cancelled with no runner and nothing had a signal. This one runs typecheck and the core and temporal suites on the hosted runners.
@github-actions

Copy link
Copy Markdown

This pull request has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

Feel free to open a new pull request that follows our guidelines.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant