Skip to content

feat(docs): deployment to github pages#25

Merged
AdriaCarrera merged 5 commits intomainfrom
docs/feat/deploy
Jun 16, 2025
Merged

feat(docs): deployment to github pages#25
AdriaCarrera merged 5 commits intomainfrom
docs/feat/deploy

Conversation

@GuillemGarciaDev
Copy link
Collaborator

@GuillemGarciaDev GuillemGarciaDev commented Jun 16, 2025

feat(docs): deployment to github pages

Summary by CodeRabbit

  • New Features
    • Added automated workflows to test and deploy documentation to GitHub Pages.
  • Documentation
    • Updated documentation site configuration for deployment branch and URL formatting.
    • Updated footer navigation links to reflect new documentation structure.
    • Removed a deprecated sidebar entry from the documentation navigation.

@coderabbitai
Copy link

coderabbitai bot commented Jun 16, 2025

📝 Walkthrough

Walkthrough

This update introduces two new GitHub Actions workflows for documentation testing and deployment. Docusaurus configuration is modified to specify the deployment branch and URL formatting, and two footer navigation links are updated. Additionally, a commented-out sidebar entry is removed from the documentation sidebar configuration.

Changes

File(s) Change Summary
.github/workflows/deploy-docs-test.yaml Added workflow for testing documentation deployment on pull requests targeting main.
.github/workflows/deploy-docs.yaml Added workflow for deploying documentation to GitHub Pages on pushes to main, with build and deploy jobs.
docs/docusaurus.config.ts Updated deployment branch to gh-pages, set trailingSlash to false, and changed two footer navigation URLs.
docs/sidebars.ts Removed a commented-out sidebar entry from the conceptsSidebar array.

Sequence Diagram(s)

sequenceDiagram
    participant GitHub
    participant Workflow (deploy-docs.yaml)
    participant Build Job
    participant Deploy Job
    participant GitHub Pages

    GitHub->>Workflow (deploy-docs.yaml): Push to main branch
    Workflow (deploy-docs.yaml)->>Build Job: Start build job
    Build Job->>Build Job: Checkout repo, setup Node.js, install deps, build docs
    Build Job->>Workflow (deploy-docs.yaml): Upload build artifact
    Workflow (deploy-docs.yaml)->>Deploy Job: Start deploy job (after build)
    Deploy Job->>GitHub Pages: Deploy artifact using actions/deploy-pages@v4
Loading
sequenceDiagram
    participant GitHub
    participant Workflow (deploy-docs-test.yaml)
    participant Test-Deploy Job

    GitHub->>Workflow (deploy-docs-test.yaml): Pull request to main branch
    Workflow (deploy-docs-test.yaml)->>Test-Deploy Job: Start test-deploy job
    Test-Deploy Job->>Test-Deploy Job: Checkout repo, setup Node.js, install deps, build docs
Loading
✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

AdriaCarrera
AdriaCarrera previously approved these changes Jun 16, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (1)
.github/workflows/deploy-docs.yaml (1)

3-8: Consider scoping deployment to doc changes.
Triggering on every push to main redeploys your site even when non-docs code changes. You can limit runs to docs-related updates:

on:
  push:
    branches:
      - main
    paths:
      - 'docs/**'
      - '.github/workflows/deploy-docs.yaml'
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 400c548 and 85cac0f.

📒 Files selected for processing (4)
  • .github/workflows/deploy-docs-test.yaml (1 hunks)
  • .github/workflows/deploy-docs.yaml (1 hunks)
  • docs/docusaurus.config.ts (2 hunks)
  • docs/sidebars.ts (0 hunks)
💤 Files with no reviewable changes (1)
  • docs/sidebars.ts
🧰 Additional context used
🪛 actionlint (1.7.7)
.github/workflows/deploy-docs-test.yaml

19-19: "working-directory" is not available with "uses". it is only available with "run"

(syntax-check)

⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: integration-contracts / integration
  • GitHub Check: integration-packages / Build
🔇 Additional comments (3)
docs/docusaurus.config.ts (3)

128-130: Verify the updated ‘Architecture’ doc path exists.
You’ve changed the footer link from /docs/concepts/architecture to /docs/concepts/architecture_overview. Make sure the corresponding file (docs/concepts/architecture_overview.md) exists and is included in your sidebar.


136-138: Validate the “Custom Backend” URL update.
The footer now points to /docs/concepts/architecture_custom_backend. Confirm you’ve created or moved the page to that path and updated any sidebar entries accordingly.


25-26:

Details

✅ Verification successful

Ensure Docusaurus version compatibility with new config keys.
The properties deploymentBranch and trailingSlash require Docusaurus v2.1+ to work as expected. Please confirm your @docusaurus/core version in docs/package.json supports these keys to avoid build errors.

Run:


🏁 Script executed:

jq -r '.dependencies["@docusaurus/core"]' docs/package.json

Length of output: 67


No action needed: Docusaurus v3.7.0 supports deploymentBranch and trailingSlash
Verified that @docusaurus/core is at version 3.7.0, which fully supports both config keys—no changes required.

@AdriaCarrera AdriaCarrera merged commit c70ff4f into main Jun 16, 2025
5 checks passed
@AdriaCarrera AdriaCarrera deleted the docs/feat/deploy branch June 16, 2025 09:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments