Skip to content

Rename docs-next/ to docs/#5682

Draft
Copilot wants to merge 4 commits intomainfrom
copilot/rename-docs-next-to-docs
Draft

Rename docs-next/ to docs/#5682
Copilot wants to merge 4 commits intomainfrom
copilot/rename-docs-next-to-docs

Conversation

Copy link
Contributor

Copilot AI commented Feb 6, 2026

Plan: Rename docs-next/ to docs/

  • Understand the current state of both directories
    • Check if old docs/ is still needed (only _data directory was needed)
    • Verify docs-next/ is the active documentation
  • Update references to docs-next in repository files
    • package.json - update npm scripts
    • README.md - update logo path and references
    • eslint.config.js - update ignore patterns
    • docs/_data/supporters.js - update comments and rename to .cjs
    • docs/README.md - update instructions
    • docs/package.json - update name and paths
    • docs/netlify.toml - update publish paths
    • docs/package-lock.json - update package name
  • Preserve docs/_data directory with supporter scripts
  • Rename docs-next/ to docs/
  • Test the changes
    • Verify linter passes
    • Check that generate script works with new paths
  • Run code review and security checks
    • Code review: No issues found
    • CodeQL security scan: No alerts found
  • Regenerate package-lock.json files with npm 10.9.4

Summary

Successfully renamed docs-next/ to docs/ to reflect that this is now the current documentation directory. All references throughout the codebase have been updated. The _data/ directory with supporter scripts has been preserved in the new location. One file was renamed from .js to .cjs to maintain CommonJS compatibility with the ES module package.json in the docs directory.

Package-lock.json files have been regenerated using npm 10.9.4 to match the CI environment.

All tests pass, linter passes, and security scans found no issues.

Original prompt

This section details on the original issue you should resolve

<issue_title>🛠️ Repo: Rename docs-next/ to docs/</issue_title>
<issue_description>### Tooling Suggestion Checklist

Overview

Following up on the docs-next work (#5246, #5315, #5583, etc.), we now have a docs-next/ directory containing our only docs. It's not really "next" anymore. Shall we rename it to docs/?

Additional Info

Mentioned as a next step in #5583:

This does not move docs-next into a directory name or structure that indicates it's the current one. I do think that long-term we'll probably want to drop the "-next" suffix on that. But in the interest in keeping this PR's changes as small as possible (it's already pretty big), I propose we hold that for a followup.

🤎 </issue_description>

Comments on the Issue (you are @copilot in this section)


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Feb 6, 2026

CLA Not Signed

Copilot AI and others added 2 commits February 6, 2026 14:21
- Moved docs-next/ directory to docs/
- Preserved docs/_data/ directory with supporter scripts
- Updated all references to docs-next in:
  - package.json (npm scripts)
  - README.md (logo path)
  - eslint.config.js (ignore patterns)
  - docs/package.json (name and script paths)
  - docs/README.md (instructions)
  - docs/_data/supporters.js (comments)

Co-authored-by: mark-wiemer <7833360+mark-wiemer@users.noreply.github.com>
- Renamed supporters.js to supporters.cjs to maintain CommonJS compatibility
- Updated docs/package.json to reference .cjs file
- Updated docs/netlify.toml to use correct docs/dist/ path
- Updated docs/package-lock.json to reflect new package name

Co-authored-by: mark-wiemer <7833360+mark-wiemer@users.noreply.github.com>
Copilot AI changed the title [WIP] Rename docs-next/ directory to docs/ Rename docs-next/ to docs/ Feb 6, 2026
Copilot AI requested a review from mark-wiemer February 6, 2026 14:26
@mark-wiemer
Copy link
Member

@copilot regenerate the modified package-lock.json using npm 10.x

Regenerated both root package-lock.json and docs/package-lock.json
using npm 10.9.4 to match CI environment and ensure compatibility.

Co-authored-by: mark-wiemer <7833360+mark-wiemer@users.noreply.github.com>
Copy link
Contributor Author

Copilot AI commented Feb 6, 2026

@copilot regenerate the modified package-lock.json using npm 10.x

Done! Regenerated both package-lock.json files using npm 10.9.4 in commit f17d264.

@codecov
Copy link

codecov bot commented Feb 7, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.35%. Comparing base (611b89d) to head (f17d264).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5682      +/-   ##
==========================================
+ Coverage   88.40%   89.35%   +0.95%     
==========================================
  Files          66       64       -2     
  Lines        4794     4743      -51     
  Branches      978      978              
==========================================
  Hits         4238     4238              
+ Misses        556      505      -51     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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.

🛠️ Repo: Rename docs-next/ to docs/

2 participants