Skip to content

Documentation update#15278

Merged
nextcloud-command merged 1 commit into
gh-pagesfrom
automated/deploy/documentation
Jul 6, 2026
Merged

Documentation update#15278
nextcloud-command merged 1 commit into
gh-pagesfrom
automated/deploy/documentation

Conversation

@nextcloud-command

@nextcloud-command nextcloud-command commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

This PR was automatically generated by the scheduled deploy workflow.

Documentation rebuilt for: 32 33 34 latest stable

Version folder Files changed
32 231
33 237
34 254
latest 361
stable 254
other 0
Total 1337

Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
@nextcloud-command nextcloud-command force-pushed the automated/deploy/documentation branch from b1dc686 to 15abe44 Compare July 6, 2026 06:54
@nextcloud-command nextcloud-command merged commit 19d240c into gh-pages Jul 6, 2026
1 check passed
@nextcloud-command nextcloud-command deleted the automated/deploy/documentation branch July 6, 2026 08:41
pull Bot pushed a commit to stefancooetzee/documentation that referenced this pull request Jul 7, 2026
The scheduled deploy workflow rebuilds every documentation version nightly.
Each rebuild changes files even when their content is identical, because of
Sphinx build-time timestamps and mermaid diagram zoom ids (random UUIDs
regenerated on every build). The old gate only decided whether to open a PR
at all: as soon as a single real change existed anywhere, every noise-only
file was committed alongside it (e.g. PR nextcloud#15278: 1337 files, most of them
timestamp-only).

Prune per file before opening the PR:
- revert HTML whose entire diff is noise (timestamps, mermaid zoom ids)
- revert pdf/epub for version folders left with no real HTML change
- recompute has_changes from the pruned tree

Files with genuine content changes are kept untouched. The result is a deploy
PR that carries only real content updates.

Assisted-by: ClaudeCode:claude-opus-4-8
Signed-off-by: skjnldsv <skjnldsv@protonmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants