Reviewing files that changed from the base of the PR and between d01a614 and 02cc6c8.

• .github/workflows/generate-website.yml (1 hunks)

.github/workflows/generate-website.yml (1)

28-29: LGTM! Path filters are correctly configured.

The added path filters are well-structured and consistent with the existing patterns:

• packages/html/**/* will trigger the workflow for any changes in the HTML package
• !packages/html/README.md properly excludes the README file to avoid unnecessary builds

Let's verify that the HTML package is indeed used in the Storybook build:

✅ Verification successful

HTML package contains Storybook stories, confirming the path filters are correctly configured

The verification results show that the packages/html/ directory contains numerous Storybook story files (*.stories.js/ts), confirming that the HTML package is indeed used in the Storybook build. Let's verify the website package's build configuration to ensure completeness:

---

HTML package is integral to Storybook with 70+ story files, path filters are correct

Based on the initial verification results, we found extensive evidence that the HTML package is a crucial part of the Storybook build:

• The packages/html/stories/ directory contains over 70 Storybook story files (*.stories.js/ts)
• These stories cover various features like Anchors, Animation, AutoLayout, etc.

The path filters in the workflow:

      - 'packages/html/**/*'
      - '!packages/html/README.md'

are correctly configured to trigger the website generation when any of these story files change, while properly excluding the README to avoid unnecessary builds.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the relationship between HTML package and Storybook build
# Expected: Find references to HTML package in Storybook configuration or package dependencies

# Check for Storybook configuration files that might reference the HTML package
echo "Searching for Storybook configuration files..."
fd -e js -e ts "\.stories\.|\.storybook" packages/html/

# Check package.json files for dependencies between packages
echo "Checking package dependencies..."
for pkg in packages/*/package.json; do
  echo "Checking $pkg..."
  cat "$pkg" | jq -r '.dependencies."@maxgraph/html" // .devDependencies."@maxgraph/html" // empty'
done

Length of output: 5705

---

Script:

#!/bin/bash
# Check website's build configuration
echo "Checking website's build configuration..."
fd -g "*.js" -g "*.ts" -g "*.json" .storybook/ packages/website/.storybook/

# Check if there are any references to HTML package stories in the website's storybook config
echo "Checking for HTML package references in website's storybook config..."
rg -l "packages/html" .storybook/ packages/website/.storybook/

Length of output: 787

---

Script:

#!/bin/bash
# Let's try a different approach to find Storybook configuration
echo "Searching for Storybook configuration files..."
fd -g "*storybook*" -g "*.stories.*"

# Check main.js/ts which typically contains story loading configuration
echo "Checking story loading configuration..."
rg -l "packages/html" --type js --type ts

Length of output: 371