Skip to content

fix(#298): add go install instructions to notion-cli plugin - #366

Closed
javimosch wants to merge 1 commit into
masterfrom
am/am-f17c27-dkdpk19l4133-1ade27f5
Closed

fix(#298): add go install instructions to notion-cli plugin#366
javimosch wants to merge 1 commit into
masterfrom
am/am-f17c27-dkdpk19l4133-1ade27f5

Conversation

@javimosch

Copy link
Copy Markdown
Owner

Automated maintenance run by automaintainer.

Focus: ISSUE FIX OBJECTIVE (GitHub Issue #298: "Add 4ier/notion-cli as bundled plugin")

ISSUE DESCRIPTION:

Feature Request: Add Notion CLI Plugin

Plugin: 4ier/notion-cli

Why this plugin?

  • Full-featured Notion CLI with 39 commands
  • Complete Notion API coverage (pages, databases, blocks, comments, users, files)
  • Single binary (Go), cross-platform (Linux, macOS, Windows)
  • MIT licensed, actively maintained (222 stars, 8 releases)
  • "Like gh for GitHub, but for Notion" - familiar CLI pattern
  • AI-friendly with JSON output and schema-aware operations

Key Features

  • Auth: Internal integration token support
  • Pages: view, list, create, delete, restore, move, open, set properties, edit
  • Databases: list, view, query, create, update, add, export
  • Blocks: full block lifecycle management
  • Search: workspace-wide search
  • Users: workspace member management
  • Files: upload and manage files
  • Templates: apply consistent page structures

Installation

go install github.com/4ier/notion-cli@latest

Use Cases

  • Developer workflow automation
  • AI agent integration for knowledge base operations
  • Scripted Notion workspace management
  • Bulk data operations on databases
  • Content management and publishing workflows

Comparison

Provides more comprehensive API coverage than alternatives like the official ntn CLI, with better cross-platform support (including Windows).

Generated with Devin

APPROACH: Minimal fix — implement the described change with the smallest safe diff. Stay as close to the issue description as possible.

PROCEDURE (follow in order, do not deviate):

  1. Read the issue and orient to the affected code (at most ~4 commands, then stop).
  2. Implement the fix described above — stay close to the issue description.
  3. If a test suite exists, verify the fix passes it.
  4. COMMIT referencing the issue: fix(Add 4ier/notion-cli as bundled plugin #298):
  5. The PR body MUST include 'Fixes Add 4ier/notion-cli as bundled plugin #298' so GitHub auto-closes the issue on merge.
  6. One focused fix is a complete win. Do not scope-creep.

Branch: am/am-f17c27-dkdpk19l4133-1ade27f5

Diff:

plugins/notion-cli/install-guidance.json      |  6 ++++--
 plugins/notion-cli/plugin.json                |  4 +++-
 plugins/notion-cli/skills/quickstart/SKILL.md | 12 +++++++++++-
 3 files changed, 18 insertions(+), 4 deletions(-)

Ensure the bundled notion-cli plugin lists the primary go install
method from the issue, alongside Homebrew and npm alternatives.

Fixes #298
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@coderabbitai

coderabbitai Bot commented Aug 1, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 20 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: 712aec2f-e778-46db-9394-2fdef7c225ca

📥 Commits

Reviewing files that changed from the base of the PR and between 6df5369 and 5d6645f.

📒 Files selected for processing (3)
  • plugins/notion-cli/install-guidance.json
  • plugins/notion-cli/plugin.json
  • plugins/notion-cli/skills/quickstart/SKILL.md

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

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

@javimosch

Copy link
Copy Markdown
Owner Author

Closing as duplicate of #369 (most recent attempt for issue #298). Reducing PR cap pressure.

@javimosch javimosch closed this Aug 4, 2026
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.

Add 4ier/notion-cli as bundled plugin

1 participant