chore: add CI and a PR template - #4
Conversation
No workflow existed here at all. The template asks for the negative control, the same as in the sibling repositories: a passing test proves nothing until it has been shown it can fail.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ea3d76ee8f
ℹ️ 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".
| node-version: ${{ matrix.node }} | ||
| cache: pnpm | ||
|
|
||
| - run: pnpm install --frozen-lockfile |
There was a problem hiding this comment.
In a fresh GitHub Actions checkout, ../mcp-core does not exist, but package.json and the lockfile resolve @projectsociety/mcp-core from file:../mcp-core. The preceding checkout step fetches only this repository, so both matrix jobs stop here with ERR_PNPM_LINKED_PKG_DIR_NOT_FOUND and never build or test; pnpm install --help confirms that the command installs every project dependency. Check out and build the sibling at the expected location, or depend on an artifact that a standalone checkout can resolve.
Useful? React with 👍 / 👎.
1 participant
This repository is public and had no workflow at all — nothing verified that it builds.
Adds the same CI as the siblings (Node 20 and 22, build, typecheck, test) and the PR template that asks for the negative control: what was sabotaged, and what went red.
130 tests, build and typecheck green.