Skip to content

Exclude blog directory from documentation unbloater workflow #13296

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pelikhan merged 2 commits into from
Feb 2, 2026
Merged

Exclude blog directory from documentation unbloater workflow #13296

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0c14051
Initial plan
Copilot Feb 2, 2026
efc48bd
feat: exclude blog directory from documentation unbloater workflow
Copilot Feb 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 8 additions & 5 deletions .github/workflows/unbloat-docs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,14 +149,16 @@ This will help you avoid re-cleaning files that were recently processed.

### 2. Find Documentation Files

Scan the `docs/` directory for markdown files, excluding code-generated files:
Scan the `docs/` directory for markdown files, excluding code-generated files and blog posts:
```bash
find docs/src/content/docs -name '*.md' -type f ! -name 'frontmatter-full.md'
find docs/src/content/docs -path 'docs/src/content/docs/blog' -prune -o -name '*.md' -type f ! -name 'frontmatter-full.md' -print
```

**IMPORTANT**: Exclude `frontmatter-full.md` as it is automatically generated from the JSON schema by `scripts/generate-schema-docs.js` and should not be manually edited.
**IMPORTANT**: Exclude these directories and files:
- `docs/src/content/docs/blog/` - Blog posts have a different writing style and purpose
- `frontmatter-full.md` - Automatically generated from the JSON schema by `scripts/generate-schema-docs.js` and should not be manually edited

Focus on files that were recently modified or are in the `docs/src/content/docs/samples/` directory.
Focus on files that were recently modified or are in the `docs/src/content/docs/` directory (excluding blog).

{{#if ${{ github.event.pull_request.number }}}}
**Pull Request Context**: Since this workflow is running in the context of PR #${{ github.event.pull_request.number }}, prioritize reviewing the documentation files that were modified in this pull request. Use the GitHub API to get the list of changed files:
Expand All @@ -172,7 +174,8 @@ Focus on markdown files in the `docs/` directory that appear in the PR's changed

**IMPORTANT**: Work on only **ONE file at a time** to keep changes small and reviewable.

**NEVER select these code-generated files**:
**NEVER select these directories or code-generated files**:
- `docs/src/content/docs/blog/` - Blog posts have a different writing style and should not be unbloated
- `docs/src/content/docs/reference/frontmatter-full.md` - Auto-generated from JSON schema

Choose the file most in need of improvement based on:
Expand Down
Loading