Repository navigation
refactor: Login and register page - #899
aXenDeveloper wants to merge 2 commits into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
React Doctor found no new issues. 🎉 Reviewed by React Doctor for commit |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7346c66f51
ℹ️ 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".
| { | ||
| "schemaVersion": 1, | ||
| "securityUpdates": {} | ||
| } |
There was a problem hiding this comment.
Restore the security-update manifest required by publishing
Deleting this file breaks the existing security-update validation and publication workflow. Checked .github/workflows/publish-security-updates.yml: changes to this path trigger the workflow, whose validation step calls release:update-manifest check. In scripts/update-manifest/publish-update-manifest.ts:276–278, readSecurityUpdates() unconditionally reads this exact file with no missing-file fallback, so validation now throws ENOENT; the publication mode uses the same reader. A repository-wide filename search found no replacement manifest. Keep the empty manifest until its consumers are migrated.
Useful? React with 👍 / 👎.
Improving Documentation
pnpm lint:fixto fix formatting issues before opening the PR.Description
What?
Why?