Skip to content

Add clipboard file paste to post composer - #595

Open
lopugit wants to merge 1 commit into
mainfrom
codex/post-composer-paste-attachments
Open

Add clipboard file paste to post composer#595
lopugit wants to merge 1 commit into
mainfrom
codex/post-composer-paste-attachments

Conversation

@lopugit

@lopugit lopugit commented Sep 3, 2026

Copy link
Copy Markdown
Owner

Summary

  • attach clipboard files from the focused post/comment editor and automatically open the existing Photos panel
  • accept file-bearing paste anywhere in the open attachment panel through the same bounded upload queue as file selection and drag/drop
  • preserve normal text paste and keep portal-based Thing editor pastes out of the post
  • document and test the clipboard workflow

Validation

  • targeted ESLint
  • focused clipboard tests: 17 passed
  • feed tests: 35 passed
  • attachment tests: 143 passed
  • production build and Vercel output verification
  • live desktop and 390 px mobile browser checks, including editor/panel file paste, normal text paste, overflow, and browser console
  • Graphify update/ensure and CAS tests: 15 passed

Manual QA note

The isolated local environment intentionally lacked usable object-storage upload credentials, so pasted files reached the shared attachment queue and rendered their rows/previews, while final storage preparation returned the fixed authored error. No test post was published.

@github-actions github-actions Bot added lopu: out-of-date The PR branch is behind its target branch lopu: overlapping files This PR changes files also changed by another open PR lopu: queued The current PR snapshot is waiting in Lopu's PR-management queue labels Sep 3, 2026
@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

🤖 Lopu detected an out-of-date PR branch

Status: Work detected — Lopu is taking ownership.

Current phase: Entering Lopu's serialized PR-resolution queue.

Estimated completion: around 10:16 UTC (~20 minutes; this adjusts as the queue moves).

Next automatic check-in: within 10 minutes while work remains active. You can stay on this PR; there is no need to find the Actions run.

Time conversion (UTC source)

Moment UTC Los Angeles Melbourne
Updated 2026-09-03 09:56 UTC (UTC+00:00) 2026-09-03 02:56 PDT (UTC-07:00) 2026-09-03 19:56 AEST (UTC+10:00)
Estimated finish 2026-09-03 10:16 UTC (UTC+00:00) 2026-09-03 03:16 PDT (UTC-07:00) 2026-09-03 20:16 AEST (UTC+10:00)

Los Angeles and Melbourne use their real IANA time zones, so PDT/PST and AEST/AEDT offsets change automatically.

Lopu queue and PR pulse

Scope Metric Count
Repository Open PRs 13
Repository Conflicting 1
Repository Out-of-date with target 4
Repository GitHub state unknown 1
Repository Part of an open stack 0
Repository Touch files changed by another open PR 9
Repository Target a non-root branch without an open parent PR 0
This resolver batch Admitted snapshots 1
This resolver batch Currently resolving 0
This resolver batch Waiting 1
This resolver batch Finished 0

Related PR context

  • Stack: No open parent or child PR currently links to this branch.
  • Target: main is a repository root/integration branch.
  • Changed-file overlap: 1 changed file is also touched by #10, #295, #554, #564, #578, #592.

Exact branch pair: maincodex/post-composer-paste-attachments.

Timeline

  • 09:56 UTC — Detected that main needs to be merged into codex/post-composer-paste-attachments; assigning the exact snapshot to the resolver queue.

@github-actions github-actions Bot added lopu: queued The current PR snapshot is waiting in Lopu's PR-management queue and removed lopu: queued The current PR snapshot is waiting in Lopu's PR-management queue labels Sep 3, 2026
@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

🤖 Lopu detected an out-of-date PR branch

Status: Work detected — Lopu is taking ownership.

Current phase: Entering Lopu's serialized PR-resolution queue.

Estimated completion: around 10:36 UTC (~20 minutes; this adjusts as the queue moves).

Next automatic check-in: within 10 minutes while work remains active. You can stay on this PR; there is no need to find the Actions run.

Time conversion (UTC source)

Moment UTC Los Angeles Melbourne
Updated 2026-09-03 10:16 UTC (UTC+00:00) 2026-09-03 03:16 PDT (UTC-07:00) 2026-09-03 20:16 AEST (UTC+10:00)
Estimated finish 2026-09-03 10:36 UTC (UTC+00:00) 2026-09-03 03:36 PDT (UTC-07:00) 2026-09-03 20:36 AEST (UTC+10:00)

Los Angeles and Melbourne use their real IANA time zones, so PDT/PST and AEST/AEDT offsets change automatically.

Lopu queue and PR pulse

Scope Metric Count
Repository Open PRs 17
Repository Conflicting 1
Repository Out-of-date with target 6
Repository GitHub state unknown 1
Repository Part of an open stack 0
Repository Touch files changed by another open PR 10
Repository Target a non-root branch without an open parent PR 0
This resolver batch Admitted snapshots 6
This resolver batch Currently resolving 0
This resolver batch Waiting 6
This resolver batch Finished 0

Related PR context

  • Stack: No open parent or child PR currently links to this branch.
  • Target: main is a repository root/integration branch.
  • Changed-file overlap: 1 changed file is also touched by #10, #295, #554, #564, #578, #592, #598.

Exact branch pair: maincodex/post-composer-paste-attachments.

Timeline

  • 10:16 UTC — Detected that main needs to be merged into codex/post-composer-paste-attachments; assigning the exact snapshot to the resolver queue.

@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

✅ Develop S3 preview ready

The alias passed the develop bucket CORS preflight and a final live PR/SHA fence.

Generic Vercel Preview deployments use the shared development runtime; this controller adds the stable exact-SHA alias and marker-scoped cleanup.

@github-actions github-actions Bot removed the lopu: queued The current PR snapshot is waiting in Lopu's PR-management queue label Sep 4, 2026
@github-actions github-actions Bot added the lopu: queued The current PR snapshot is waiting in Lopu's PR-management queue label Sep 4, 2026
@github-actions

github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

⚠️ Could not auto-resolve every conflict with main — manual resolution is needed for the residual paths below. See the workflow run.

Residual conflicted files:

  • TESTING.md

@github-actions github-actions Bot removed the lopu: queued The current PR snapshot is waiting in Lopu's PR-management queue label Sep 4, 2026
@github-actions github-actions Bot added lopu: queued The current PR snapshot is waiting in Lopu's PR-management queue and removed lopu: queued The current PR snapshot is waiting in Lopu's PR-management queue labels Sep 4, 2026
@github-actions github-actions Bot added the lopu: queued The current PR snapshot is waiting in Lopu's PR-management queue label Sep 4, 2026
@github-actions

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

🤝 Merged main into codex/post-composer-paste-attachments — conflicts auto-resolved by Lopu's PR manager.

Conflicted files:

  • TESTING.md

Rebuilt and committed the merged code graph with graphify update .. LLM semantic extraction was attempted afterward but failed; the valid structural result was preserved (see the workflow log).

Please review the merge commit before relying on it.

@github-actions github-actions Bot added lopu: resolving Lopu is actively managing this PR branch lopu: unknown state GitHub is still computing the PR branch state and removed lopu: queued The current PR snapshot is waiting in Lopu's PR-management queue lopu: conflicting GitHub reports merge conflicts for the current PR snapshot labels Sep 5, 2026
@github-actions

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

🤖 Branch status still computing. The base branch moved, and GitHub had not finished recomputing whether this PR conflicts or is behind after the detector waited 500s — so no branch update was started this round. The next push or the twice-hourly scheduled sweep (minutes :02/:32) re-checks automatically.

Posted by the conflict detector at 03:33 UTC, 2026-09-05; this notice is edited in place on re-checks.

@github-actions github-actions Bot removed the lopu: resolving Lopu is actively managing this PR branch label Sep 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lopu: overlapping files This PR changes files also changed by another open PR lopu: unknown state GitHub is still computing the PR branch state

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant