improve studio UI polish and CMS workflow clarity#22
Conversation
![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: 337be8cd3b
ℹ️ 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".
| @@ -0,0 +1 @@ | |||
| Subproject commit e791f54723e8a630ae5316dbd6a14e0763924b51 | |||
There was a problem hiding this comment.
This adds .claude/worktrees/project-guidance as a submodule gitlink, but the commit does not add a .gitmodules entry for it. In this state a fresh checkout has no URL to fetch, and even git submodule status --recursive fails with no submodule mapping found in .gitmodules for path '.claude/worktrees/project-guidance'; either remove this local worktree from the index or add a real submodule mapping.
Useful? React with 👍 / 👎.
| pnpm install --frozen-lockfile | ||
| pnpm build | ||
| pnpm test | ||
| pnpm exec playwright install chromium # first time only |
There was a problem hiding this comment.
This checklist is written as repo-root commands, but @playwright/test is only a dependency of apps/studio, not the root package, so pnpm exec playwright install chromium from the repository root fails with Command "playwright" not found. The release checklist will block operators before e2e setup unless this uses the studio workspace command, matching the CI workflow's working-directory: apps/studio step.
Useful? React with 👍 / 👎.
| CI runs build, unit tests, and Playwright smoke tests; GitHub CodeQL analyzes | ||
| JavaScript/TypeScript and Actions workflows on pushes and PRs to `main`. |
There was a problem hiding this comment.
The security policy now tells users that CodeQL analyzes JS/TS and Actions on pushes and PRs, but the repository only contains .github/workflows/ci.yml and has no CodeQL workflow or checked-in configuration. Unless this depends on an untracked repository setting, a fresh fork or checkout will not get the advertised CodeQL coverage, so this overstates the current automated security checks.
Useful? React with 👍 / 👎.
1 participant
ui polish.....editor ux improvements next