Skip to content

Conversation

@andyjakubowski
Copy link
Contributor

@andyjakubowski andyjakubowski commented Oct 16, 2025

Closes:

GRN-4812: Update README.md
GRN-4817: Create a contributing guide
GRN-4921: Add instructions on applying extension template updates

Signed-off-by: Andy Jakubowski hello@andyjakubowski.com

Summary by CodeRabbit

  • Documentation
    • Simplified README: clearer install, usage (including read-only viewer behavior), troubleshooting, and maintenance; replaced development instructions with a pointer to CONTRIBUTING.
    • Updated system requirements to Python 3.9+ and JupyterLab 4.5.0+.
    • Added CONTRIBUTING with step-by-step development, auth, build/watch, testing, and packaging guidance.
    • Clarified release notes: only the Python package is published; frontend isn’t published separately and requires backend components.

@linear
Copy link

linear bot commented Oct 16, 2025

GRN-4956 Update OSS docs

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 16, 2025

📝 Walkthrough

Walkthrough

Adds a new CONTRIBUTING.md with step-by-step developer guidance: environment setup (Python/Node, uv tooling), editable installs, authentication for @deepnote/blocks, linking the frontend with JupyterLab, enabling the server extension, watch/build/debug workflows, test commands (pytest/Jest), uninstall steps, release guidance, and instructions for applying extension template updates. README.md was refocused to user-facing install/usage/troubleshooting content and now links to CONTRIBUTING.md for development. RELEASE.md was updated to state only the Python package is published to PyPI and the frontend is not published separately.

Sequence Diagram(s)

The changes are documentation-only and do not introduce or modify runtime control flow, so no sequence diagram is provided.

Possibly related PRs

Pre-merge checks

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Linked Issues Check ❓ Inconclusive The PR addresses GRN-4812 and GRN-4817 effectively: README.md was updated with usage-focused content and the contributing section was removed, while a new CONTRIBUTING.md was created with development setup and testing guidance. However, for GRN-4921, the provided summary of CONTRIBUTING.md changes does not explicitly indicate that step-by-step instructions for applying extension template updates were added. The summary mentions development installation, testing, and packaging but lacks evidence that the specific template update guidance requirement was implemented. Verify that CONTRIBUTING.md includes explicit step-by-step instructions explaining how to apply updates from the extension template into the jupyterlab-deepnote repository, as specified in GRN-4921. If this content is present but omitted from the summary, the check passes; if absent, add it before merging.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The title "docs: update OSS docs" clearly and concisely describes the primary change in the pull request. It uses conventional commit format and accurately reflects that multiple documentation files are being updated (CONTRIBUTING.md, README.md, and RELEASE.md). While "OSS docs" is somewhat broad, it's sufficiently specific in context and effectively communicates the documentation focus to someone scanning the commit history.
Out of Scope Changes Check ✅ Passed The changes to CONTRIBUTING.md and README.md align with the three linked issues (GRN-4812, GRN-4817, and GRN-4921). However, modifications to RELEASE.md were not explicitly mentioned in the requirements. While these changes clarify publishing procedures and appear reasonable as ancillary documentation updates, they fall outside the stated objectives of the linked issues. The scope is mostly in-scope with a minor undisclosed addition.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ae02719 and d270a96.

📒 Files selected for processing (2)
  • CONTRIBUTING.md (1 hunks)
  • README.md (0 hunks)
💤 Files with no reviewable changes (1)
  • README.md
🧰 Additional context used
🪛 markdownlint-cli2 (0.18.1)
CONTRIBUTING.md

31-31: Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)


36-36: Bare URL used

(MD034, no-bare-urls)


42-42: Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


44-44: Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)

Signed-off-by: Andy Jakubowski <hello@andyjakubowski.com>
Signed-off-by: Andy Jakubowski <hello@andyjakubowski.com>
@andyjakubowski andyjakubowski force-pushed the andy/grn-4956-update-oss-docs branch from d270a96 to e34145a Compare October 16, 2025 15:05
Signed-off-by: Andy Jakubowski <hello@andyjakubowski.com>
@andyjakubowski andyjakubowski marked this pull request as ready for review October 16, 2025 15:06
coderabbitai[bot]
coderabbitai bot previously approved these changes Oct 16, 2025
@andyjakubowski andyjakubowski changed the base branch from andy/grn-4810-default-to-python3-kernel to main October 16, 2025 15:10
@andyjakubowski andyjakubowski dismissed coderabbitai[bot]’s stale review October 16, 2025 15:10

The base branch was changed.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

♻️ Duplicate comments (1)
CONTRIBUTING.md (1)

39-47: Fix the lingering lint hits.

Convert the bare URL in the list item to a proper Markdown link so markdownlint stops flagging MD034.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d270a96 and f1210d2.

📒 Files selected for processing (3)
  • CONTRIBUTING.md (1 hunks)
  • README.md (1 hunks)
  • RELEASE.md (2 hunks)

Signed-off-by: Andy Jakubowski <hello@andyjakubowski.com>
@codecov
Copy link

codecov bot commented Oct 17, 2025

The author of this PR, andyjakubowski, is not an activated member of this organization on Codecov.
Please activate this user on Codecov to display this PR comment.
Coverage data is still being uploaded to Codecov.io for purposes of overall coverage calculations.
Please don't hesitate to email us at support@codecov.io with any questions.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f1210d2 and cce9f56.

📒 Files selected for processing (1)
  • README.md (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: build
  • GitHub Check: check_release
🔇 Additional comments (3)
README.md (3)

6-6: User-focused content structure is clear and well-organized.

The reorganization successfully shifts README toward end-user guidance: simplified install, clear usage examples, and straightforward uninstall steps. Good alignment with PR objectives.

Also applies to: 15-19, 21-27, 49-55


57-59: Contributing reference appropriately delegates to external file.

Clean pointer to CONTRIBUTING.md aligns with separation of concerns (user README vs. contributor guide).


10-11: Confirm if Python 3.9+ is intentional or should align with JupyterLab 4.0.0's 3.8+ baseline.

JupyterLab 4.0.0 requires Python 3.8 or newer, but the README specifies 3.9+. If this stricter requirement reflects extension-specific dependencies, keep it; otherwise, consider relaxing to 3.8+ to match the JupyterLab baseline.

Signed-off-by: Andy Jakubowski <hello@andyjakubowski.com>
coderabbitai[bot]
coderabbitai bot previously approved these changes Oct 17, 2025
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

♻️ Duplicate comments (1)
README.md (1)

29-43: Expand Troubleshooting with diagnostic steps and support link.

The section verifies extension presence but omits common diagnostic actions (browser cache, console errors, logs) and a link to open issues—improvements suggested in prior review.

Consider this more complete guidance:

  ## Troubleshooting
  
  If you encounter issues with the extension, verify that both the server and frontend extensions are properly installed and enabled.
  
  Check server extensions:
  
  ```bash
  jupyter server extension list

Check frontend extensions:

jupyter labextension list
  • If issues persist:
    1. Clear your browser cache and reload JupyterLab.
    1. Open the browser console (F12 or Ctrl+Shift+I) and check for errors.
    1. Check Jupyter server logs for backend errors.
  • For further assistance, please open an issue on GitHub.

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used**: CodeRabbit UI

**Review profile**: ASSERTIVE

**Plan**: Pro

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between cce9f5647f9e0ae7982d4e8c7360b6731f2bd3d5 and fd857e123b9fd661b1edb3888b03a8c84a85c3b9.

</details>

<details>
<summary>📒 Files selected for processing (1)</summary>

* `README.md` (1 hunks)

</details>

<details>
<summary>⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)</summary>

* GitHub Check: build
* GitHub Check: check_release

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->

coderabbitai[bot]
coderabbitai bot previously approved these changes Oct 17, 2025
Conda should not be a recommended package registry target

Signed-off-by: Andy Jakubowski <hello@andyjakubowski.com>
coderabbitai[bot]
coderabbitai bot previously approved these changes Oct 17, 2025
We need that version because it adds support for custom content providers, something our extension depends on:
https://jupyterlab.readthedocs.io/en/stable/extension/extension_points.html#content-provisioning

Signed-off-by: Andy Jakubowski <hello@andyjakubowski.com>
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between deefc67 and c700cdc.

📒 Files selected for processing (1)
  • README.md (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: Spell Check
  • GitHub Check: build
  • GitHub Check: check_release
🔇 Additional comments (2)
README.md (2)

10-11: Clarify the 4.5.0 baseline and add support/maintenance policy.

The Requirements bump JupyterLab from 4.0.0 to 4.5.0 without explanation. Past feedback flagged vague maintenance guidance; the README now lacks explicit support scope (which 4.x releases are supported, what happens if users stay on older versions, breaking-change expectations).

Consider adding a brief maintenance note:

 ## Requirements

 - Python 3.9 or higher
- - JupyterLab 4.5.0 or higher
+ - JupyterLab 4.5.0 or higher (tested minimum; all 4.x releases supported)
+
+ **Maintenance:** We recommend keeping JupyterLab updated to the latest 4.x for bug fixes and security patches. Breaking changes will be called out in release notes and may require upgrading to 5.x.

53-55: Clean separation of user and developer docs.

The Contributing section now appropriately directs users to CONTRIBUTING.md for development guidance, keeping README focused on usage. This aligns well with the PR objectives.

Copy link
Contributor

@jamesbhobbs jamesbhobbs left a comment

Choose a reason for hiding this comment

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

Not final but a vast improvement on what we have @Yggdrasill501 should be updating it soon so merging as is for the improvement.

@jamesbhobbs jamesbhobbs merged commit 125f95d into main Oct 23, 2025
13 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