Skip to content

Save captures to Pinboard by default; keep Readwise optional - #3

Merged
randomradio merged 1 commit into
mainfrom
cursor/clipboard-instead-of-readwise-b20b
Sep 10, 2026
Merged

randomradio merged 1 commit into
mainfrom
cursor/clipboard-instead-of-readwise-b20b

Conversation

@randomradio

@randomradio randomradio commented Sep 10, 2026 •

Copy link
Copy Markdown
Owner

What changed

Readwise Reader stays as an optional destination and stays off unless you turn it on.

New captures save to Pinboard by default when a token is configured. The Options checkbox matches that default.

This is the 0.1.5 release cut: Pinboard-first capture, optional Readwise, plus the unreleased main work since v0.1.4 (Readability, item index, toast retry, tests, CI).

Why

The useful default is a tagged Pinboard bookmark. Readwise can stay for people who want it.

Tests

  • pnpm typecheck
  • pnpm test — 136 passing
  • pnpm build
Open in Web Open in Cursor 

@cursor cursor Bot changed the title Copy tagged captures to the clipboard instead of Readwise Save tagged captures to Pinboard instead of Readwise Sep 10, 2026
Readwise can stay as an optional destination. New captures go to Pinboard unless the user turns that off.

Co-authored-by: i.an <randomradio@users.noreply.github.com>
@cursor
cursor Bot force-pushed the cursor/clipboard-instead-of-readwise-b20b branch from df3ed15 to 606e765 Compare September 10, 2026 16:43
@cursor cursor Bot changed the title Save tagged captures to Pinboard instead of Readwise Save captures to Pinboard by default; keep Readwise optional Sep 10, 2026
@randomradio
randomradio marked this pull request as ready for review September 10, 2026 16:43
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 10, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-10T16:47:03.102353Z 606e765 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@randomradio
randomradio merged commit fe69a20 into main Sep 10, 2026
1 check passed

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 606e765fa8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

- `pnpm build`
- `pnpm package`
- `unzip -l tldr-v0.1.1.zip`
- `unzip -l tldr-v0.1.5.zip`

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Correct the validation record for the 0.1.5 artifact

This now records tldr-v0.1.5.zip as having been inspected on 2026-06-12, but the repository was still at version 0.1.1 on that date and 0.1.5 is introduced by this commit. Since scripts/package.mjs derives the archive name from package.json, that earlier validation could not have covered this artifact; update the date after actually packaging and inspecting 0.1.5, or retain the previously validated filename so release staff do not rely on a false validation record.

Useful? React with 👍 / 👎.

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.

2 participants