Skip to content

Update links to readme files and others for mono repo - #8827

Merged
sumerjabri merged 9 commits into
craftersoftware:developfrom
alhambrav:update-links-for-monorepo
Jul 29, 2026
Merged

Update links to readme files and others for mono repo#8827
sumerjabri merged 9 commits into
craftersoftware:developfrom
alhambrav:update-links-for-monorepo

Conversation

@alhambrav

@alhambrav alhambrav commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Ticket reference or the full description of what's in the PR

Update links to readme files and others for mono repo

Summary by CodeRabbit

  • Documentation
    • Updated repository and community links across project documentation to point to the current CrafterCMS repository.
    • Improved README heading structure, formatting, module guidance, build instructions, and development workflow documentation.
    • Added clearer instructions for checking existing issues before submitting bug, enhancement, feature, or quality requests.
    • Updated JavaScript SDK package metadata and documentation links for improved repository navigation.
    • Corrected issue references and clarified select inline documentation without changing application behavior.

@alhambrav

Copy link
Copy Markdown
Contributor Author

@rart @jvega190 Please review the URL changes made for json and tsx files. Thank you!

@coderabbitai

coderabbitai Bot commented Jul 27, 2026

Copy link
Copy Markdown

Review Change Stack

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

Walkthrough

Updates CrafterCMS repository links across issue templates, documentation, package metadata, changelog entries, and inline references. The root README also revises cloning, module forking, upgrade, and build instructions.

Changes

Repository reference updates

Layer / File(s) Summary
Build workflow documentation
README.md
Updates repository clone commands, build and upgrade terminology, module forking guidance, Docker tag examples, and task documentation.
JavaScript package metadata
js-sdk/package.json, js-sdk/packages/*/package.json, studio-ui/ui/uppy/package.json
Updates repository, directory, issue tracker, and homepage metadata for SDK and UI packages.
Community documentation links
cli/README.md, commons/README.md, core/README.md, deployer/README.md, engine/README.md, groovy-sandbox/README.md, profile/README.md, search/README.md, social/README.md, studio/README.md, studio-ui/README.md, studio-ui/ui/app/*
Changes community and resource URLs to the craftersoftware/craftercms repository and adjusts selected Markdown headings and link layouts.
Issue and inline reference updates
.github/ISSUE_TEMPLATE/*, js-sdk/CHANGELOG.md, js-sdk/packages/content/README.md, studio-ui/ui/app/src/*, studio-ui/ui/guest/src/controls/rte.ts
Updates issue-history instructions, issue links, changelog references, and explanatory comments without changing runtime behavior.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

Suggested reviewers: sumerjabri, jmendeza, rart

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 22.22% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title is concise and related to the main change: updating monorepo links across README and related files.
Description check ✅ Passed The description matches the required template and includes the requested ticket/full-description section.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
studio-ui/ui/uppy/package.json (1)

18-23: 🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win

Align the repository metadata with the monorepo.

bugs.url now targets craftersoftware/craftercms, but repository.url and repository.directory still reference the former standalone studio-ui layout. Update both fields so package consumers are directed to the correct monorepo location.

Proposed fix
  "repository": {
    "type": "git",
-   "url": "git+https://github.com/craftercms/studio-ui.git",
-   "directory": "ui/uppy"
+   "url": "git+https://github.com/craftersoftware/craftercms.git",
+   "directory": "studio-ui/ui/uppy"
  },
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@studio-ui/ui/uppy/package.json` around lines 18 - 23, Update the repository
metadata in package.json to point to the Crafter CMS monorepo: replace the
former studio-ui repository URL and adjust repository.directory to the package’s
correct monorepo path, keeping bugs.url unchanged.
🧹 Nitpick comments (1)
studio/README.md (1)

12-12: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Use the configured heading style for the new subsections.

The new headings at Lines 12, 16, and 20 trigger markdownlint MD003 because this repository expects setext headings. Convert them to setext style or update the lint configuration consistently.

Also applies to: 16-16, 20-20

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@studio/README.md` at line 12, Update the new subsection headings in
studio/README.md, including Code of Conduct and the headings at the
corresponding lines, to use the repository’s configured setext heading style;
alternatively, consistently update the markdownlint MD003 configuration if that
is the intended project-wide change.

Source: Linters/SAST tools

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@groovy-sandbox/README.md`:
- Line 54: Align the changed community headings with the configured markdownlint
MD003 style by converting the headings to setext syntax, preserving their
existing text. Apply this to groovy-sandbox/README.md at lines 54, 58, and 62;
profile/README.md at lines 12, 16, and 20; search/README.md at lines 12, 16, and
20; and social/README.md at lines 12, 16, and 20. Do not change the
configuration unless ATX headings are intentionally required.

In `@README.md`:
- Around line 224-242: Update the README section “4.3.1. Forking the Repository”
so the documented selfUpdate command explicitly uses the upstream remote via the
gitRemote Gradle property. Also update the fallback git pull instruction to pull
from upstream, ensuring both update paths retrieve changes from the canonical
repository rather than the contributor’s fork.

---

Outside diff comments:
In `@studio-ui/ui/uppy/package.json`:
- Around line 18-23: Update the repository metadata in package.json to point to
the Crafter CMS monorepo: replace the former studio-ui repository URL and adjust
repository.directory to the package’s correct monorepo path, keeping bugs.url
unchanged.

---

Nitpick comments:
In `@studio/README.md`:
- Line 12: Update the new subsection headings in studio/README.md, including
Code of Conduct and the headings at the corresponding lines, to use the
repository’s configured setext heading style; alternatively, consistently update
the markdownlint MD003 configuration if that is the intended project-wide
change.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 5a855d91-da5b-4a22-ad0d-dd100fdf6aee

📥 Commits

Reviewing files that changed from the base of the PR and between d921262 and a21c4f7.

📒 Files selected for processing (40)
  • .github/ISSUE_TEMPLATE/bug_report.yml
  • .github/ISSUE_TEMPLATE/enhancement_request.yml
  • .github/ISSUE_TEMPLATE/feature_request.yml
  • .github/ISSUE_TEMPLATE/quality_request.yml
  • README.md
  • build.gradle
  • cli/README.md
  • commons/README.md
  • core/README.md
  • deployer/README.md
  • engine/README.md
  • groovy-sandbox/README.md
  • js-sdk/CHANGELOG.md
  • js-sdk/README.md
  • js-sdk/package.json
  • js-sdk/packages/classes/package.json
  • js-sdk/packages/content/README.md
  • js-sdk/packages/content/package.json
  • js-sdk/packages/ice/package.json
  • js-sdk/packages/models/package.json
  • js-sdk/packages/redux/package.json
  • js-sdk/packages/search/package.json
  • js-sdk/packages/utils/package.json
  • profile/README.md
  • search/README.md
  • social/README.md
  • studio-ui/README.md
  • studio-ui/ui/app/README.md
  • studio-ui/ui/app/scripts/README.md
  • studio-ui/ui/app/src/components/DashletCard/dashletCommons.tsx
  • studio-ui/ui/app/src/components/ItemDisplay/ItemDisplay.tsx
  • studio-ui/ui/app/src/components/ItemMegaMenu/ItemMegaMenuUI.tsx
  • studio-ui/ui/app/src/components/PathNavigator/PathNavigator.tsx
  • studio-ui/ui/app/src/components/PathNavigator/PathNavigatorUI.tsx
  • studio-ui/ui/app/src/components/PathNavigatorTree/PathNavigatorTree.tsx
  • studio-ui/ui/app/src/components/PathNavigatorTree/PathNavigatorTreeUI.tsx
  • studio-ui/ui/app/src/utils/contentType.ts
  • studio-ui/ui/guest/src/controls/rte.ts
  • studio-ui/ui/uppy/package.json
  • studio/README.md

Comment thread groovy-sandbox/README.md Outdated
Comment thread README.md Outdated

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
README.md (1)

224-236: 🎯 Functional Correctness | 🟠 Major

Make the documented self-update pull from upstream.

The instructions configure origin as the fork and add the canonical repository as upstream, but Line [235] runs ./gradlew selfUpdate without -PgitRemote=upstream. Since gitRemote defaults to origin and build.gradle passes it to git pull, this can update from the fork instead of the canonical repository.

Suggested documentation change
-    ./gradlew selfUpdate
+    ./gradlew -PgitRemote=upstream selfUpdate
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` around lines 224 - 236, Update the “To update your local clone
with the latest” command in the Forking the Repository section to invoke
selfUpdate with the gitRemote property set to upstream, ensuring it pulls from
the canonical repository rather than origin.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@README.md`:
- Around line 224-236: Update the “To update your local clone with the latest”
command in the Forking the Repository section to invoke selfUpdate with the
gitRemote property set to upstream, ensuring it pulls from the canonical
repository rather than origin.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: ba6580b9-f38c-4646-b3f6-477e38b61309

📥 Commits

Reviewing files that changed from the base of the PR and between e1777da and 96a48a8.

📒 Files selected for processing (2)
  • README.md
  • build.gradle

@alhambrav
alhambrav marked this pull request as ready for review July 29, 2026 10:45
@alhambrav
alhambrav requested a review from sumerjabri as a code owner July 29, 2026 10:45
@sumerjabri
sumerjabri merged commit 620de4e into craftersoftware:develop Jul 29, 2026
1 of 2 checks passed
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.

3 participants