chore(ci): Separate schema generation into dedicated workflow#799
chore(ci): Separate schema generation into dedicated workflow#799
Conversation
Moved generate-schema job from ci.yml to a new schema-update.yml workflow to prevent unnecessary execution during PRs. The new workflow runs only on main branch pushes and includes proper permissions for git operations. This improves CI efficiency by separating concerns between testing and schema maintenance.
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
|
Note Other AI code review bot(s) detectedCodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review. Caution Review failedThe pull request is closed. WalkthroughRemoves the generate-schema job from .github/workflows/ci.yml and introduces a dedicated .github/workflows/schema-update.yml workflow to generate and auto-commit the schema. Adds a new versioned schema at website/client/src/public/schemas/1.4.0/schema.json and updates the latest schema to include git includeLogs and includeLogsCount fields. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
actor Dev as Developer/PR
participant GH as GitHub
participant WF as Update Schema Workflow
participant Node as Node/NPM
participant Repo as Repo
Dev->>GH: Push / PR to main (or manual dispatch)
GH->>WF: Trigger "Update Schema"
WF->>Repo: actions/checkout@<pinned>
WF->>Node: setup-node (.tool-versions, npm cache)
WF->>Node: npm ci
WF->>Node: npm run website-generate-schema
WF->>Repo: git-auto-commit (commit schema changes)
Repo-->>Dev: Commit with "chore(schema): auto generate schema"
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
📜 Recent review detailsConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro 💡 Knowledge Base configuration:
You can enable these sources in your CodeRabbit configuration. 📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
Status, Documentation and Community
|
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
Deploying repomix with
|
| Latest commit: |
5ef2e45
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://b2efa9de.repomix.pages.dev |
| Branch Preview URL: | https://feat-schema.repomix.pages.dev |
There was a problem hiding this comment.
Pull Request Overview
This PR separates schema generation from the main CI pipeline by moving it to a dedicated workflow, improving CI efficiency by only running schema updates when needed.
- Moved
generate-schemajob fromci.ymlto newschema-update.ymlworkflow - Added proper permissions and triggers for the new schema workflow
- Eliminated unnecessary schema generation during PR validation
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| .github/workflows/schema-update.yml | New dedicated workflow for schema generation with proper permissions and triggers |
| .github/workflows/ci.yml | Removed generate-schema job to streamline CI pipeline |
This PR separates the schema generation workflow from the main CI pipeline to improve efficiency and reduce unnecessary executions during PRs.
Summary
The
generate-schemajob has been moved fromci.ymlto a new dedicatedschema-update.ymlworkflow. This change prevents schema generation from running on every PR, as it's only needed when changes are merged to the main branch.Key Changes
generate-schemajob fromci.ymlschema-update.ymlworkflow with:mainbranch pushes and manual dispatchcontents: writepermissions for git operationsBenefits
Path Triggers
The new workflow only runs when these files change:
src/config/configSchema.tspackage.jsonwebsite/client/package.jsonChecklist
npm run testnpm run lint