docs(ci): correct the include-hidden-files rationale in docs.yml

[EtienneLescot]

Problem

The comment I added in #316 (7c4827b9) states:

v4 stopped bundling dotfiles, and Docusaurus writes a .nojekyll into website/build

That is wrong. Docusaurus writes .nojekyll from its own deploy command, not from a plain build. This site runs npm run build and deploys the artifact, so no .nojekyll is ever produced.

Verified rather than assumed — the Pages artifact published by that very commit (id 9028339047) was downloaded and unpacked:

$ tar -tf artifact.tar | wc -l
59
$ tar -tf artifact.tar | grep -E '(^|/)\.[^/]'
(no dot-entries at all)

So include-hidden-files: true is currently a no-op, and the risk I used to justify splitting docs.yml out of #97 did not actually exist.

Fix

Keep the flag, correct the reason.

The value is forward-looking, not current: a .well-known/ directory added later for domain verification or security.txt would be dropped from the deploy silently under the v4+ default. That is the failure worth guarding — it is invisible until someone wonders why a verification never completes.

No behavior change; this touches a comment only.

Note

The Pages deploy on main after #316 succeeded end to end — Build site and Deploy to GitHub Pages both green, https://getopenscreen.com/ serving 200, and zero Node 20 deprecation lines in the run. The bump itself is fine; only its stated rationale was off.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@EtienneLescot, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 11 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 40adac5e-3553-4e79-823a-727299522597

📥 Commits

Reviewing files that changed from the base of the PR and between 7c4827b and f83d72a.

📒 Files selected for processing (1)

• .github/workflows/docs.yml

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}