paperclip-github-plugin 0.8.2 → 0.8.4

package/README.md

@@ -35,7 +35,7 @@ The plugin adds a full in-host workflow instead of a one-off import script:
 - saved sync diagnostics that let operators inspect the latest per-issue failures, raw errors, and suggested next steps
 - a project sidebar item that opens a live project-scoped Pull Requests page for the mapped repository and can show the open PR count through a lightweight badge read
 - manual sync actions from global, project, and issue surfaces
-- a GitHub detail tab on synced Paperclip issues that includes GitHub-marked action buttons plus the GitHub issue creator with avatar, and lets operators manually link an unlinked Paperclip issue to a GitHub issue or pull request
+- a GitHub detail tab on synced Paperclip issues that includes GitHub-marked action buttons plus the GitHub issue creator with avatar, and lets operators manually link or unlink a Paperclip issue from a GitHub issue or pull request
 - GitHub link annotations on sync-generated status transition comments when the host supports comment annotations
 
 ## How it works
@@ -88,6 +88,8 @@ If a Paperclip issue was created locally or by an agent workflow before GitHub S
 
 Manual GitHub issue links are added to the same import registry and issue-link entity used by normal sync, so future syncs update the Paperclip issue from the GitHub issue. Manual pull request links are added to the PR-link entity used by the project Pull Requests page, so future syncs monitor PR status even when there is no closing GitHub issue.
 
+Linked Paperclip issues can also be unlinked from the GitHub detail surface. Unlinking removes the active GitHub Sync link metadata and import-registry tracking for that Paperclip issue without deleting either side, so the issue stays local until it is linked again.
+
 ### Agent workflows built in
 
 Paperclip agents can search GitHub for duplicates, read and update issues, assign issues to the saved token owner, post comments, create pull requests, inspect changed files and CI, reply to review threads, resolve or unresolve threads, request reviewers, search org-level GitHub Projects, and associate pull requests with those projects without leaving the Paperclip plugin surface.
@@ -146,6 +148,8 @@ To keep imported issues recognizable without cluttering the visible description,
 
 Repeated syncs keep existing imports current instead of creating duplicates again. If the plugin's import registry is stale, the worker can repair deduplication by reusing existing Paperclip issues when durable GitHub link metadata is already present.
 
+If a linked GitHub issue is transferred to another repository, GitHub Sync follows the canonical GitHub URL. When the destination repository is mapped to another Paperclip project in the same company, the existing Paperclip issue moves to that project and keeps its GitHub link. When the destination repository is not mapped, GitHub Sync unlinks the Paperclip issue and marks it `cancelled` with a Paperclip comment explaining the transfer.
+
 When the local Paperclip API is available, the plugin also syncs labels by name, prefers exact color matches when multiple Paperclip labels share the same name, and creates missing Paperclip labels when needed.
 
 ### Status mapping
@@ -155,17 +159,19 @@ When the local Paperclip API is available, the plugin also syncs labels by name,
 | Open issue with no linked pull request, created by a repository maintainer | `todo` on first import |
 | Open issue with no linked pull request | Configured default status, which defaults to `backlog` |
 | Open issue with a linked pull request and unfinished CI | `in_progress` |
-| Open issue with failing CI, a non-mergeable linked pull request, requested changes, or unresolved review threads | `todo`, or `in_progress` when GitHub Sync can hand the work back to an executor |
-| Open issue with green CI, a merge-ready linked pull request, no requested changes, and all review threads resolved | `in_review` |
+| Open issue with failing CI, a non-mergeable linked pull request, or unresolved review threads | `todo`, or `in_progress` when GitHub Sync can hand the work back to an executor |
+| Open issue with green CI, a merge-ready linked pull request, and all review threads resolved | `in_review` |
 | Closed issue completed as finished work | `done` |
 | Closed issue closed as `not_planned` or `duplicate` | `cancelled` |
 
 Additional behavior:
 
 - Open issues with no linked pull request that are created by a verified repository maintainer/admin bypass the default imported status and start in `todo`.
+- If the Paperclip host initially creates that imported maintainer issue in `backlog`, GitHub Sync promotes it to `todo` without replacing the configured default assignee with the executor handoff assignee, so triage ownership stays intact.
 - When Paperclip board access is connected for a company, the advanced assignee dropdowns list both company agents and `Me` for the connected board user.
 - Newly imported issues that finish sync in `todo` and are assigned to an agent enqueue an assignee wakeup so the agent can pick them up promptly.
-- For linked pull requests, GitHub Sync treats merge-conflict, behind-branch, blocked, draft, unstable merge states, and requested-changes review decisions as executor work, while merge-ready states such as `CLEAN` and `HAS_HOOKS` can move work into `in_review` when CI is green and there are no requested changes or unresolved review threads.
+- For linked pull requests, GitHub Sync treats merge-conflict, behind-branch, blocked, draft, unstable merge states, and unresolved review threads as executor work, while merge-ready states such as `CLEAN` and `HAS_HOOKS` can move work into `in_review` when CI is green and review threads are resolved. A stale aggregate `CHANGES_REQUESTED` review decision alone does not move that maintainer wait back to active execution.
+- Imported issues that are already `blocked` stay `blocked` while any first-class `blockedBy` issue is still non-terminal, even if the linked GitHub pull request is otherwise green and review-ready.
 - When sync moves work into `in_review`, GitHub Sync first follows the Paperclip issue execution policy's current reviewer or approver when that stage is visible on the issue. If Paperclip exposes an internal review or approval stage but not yet the participant, the plugin falls back to the configured reviewer or approver handoff assignee. If the transition is only a healthy linked-PR wait with no visible internal review or approval stage, GitHub Sync leaves the issue unassigned so it can wait on normal maintainer review without waking an internal owner.
 - When sync moves work back into active execution, GitHub Sync first follows the Paperclip issue execution policy `returnAssignee` when it is available. Otherwise it falls back to the configured executor handoff assignee and then to the default imported assignee.
 - Sync-driven handoffs to agent assignees best-effort enqueue an explicit wakeup so the next reviewer, approver, or executor can pick the issue up even when their agent is not running heartbeats.

package/dist/manifest.js

@@ -535,7 +535,7 @@ var COMPANY_METRIC_API_ROUTE_URL_PATH = `/api/plugins/${GITHUB_SYNC_PLUGIN_ID}/a
 var require2 = createRequire(import.meta.url);
 var packageJson = require2("../package.json");
 var SCHEDULE_TICK_CRON = "* * * * *";
-var MANIFEST_VERSION = "0.8.2"?.trim() || typeof packageJson.version === "string" && packageJson.version.trim() || process.env.npm_package_version?.trim() || "0.0.0-dev";
+var MANIFEST_VERSION = "0.8.4"?.trim() || typeof packageJson.version === "string" && packageJson.version.trim() || process.env.npm_package_version?.trim() || "0.0.0-dev";
 var manifest = {
   id: GITHUB_SYNC_PLUGIN_ID,
   apiVersion: 1,
@@ -559,6 +559,7 @@ var manifest = {
     "issues.create",
     "issues.update",
     "issues.wakeup",
+    "issue.relations.read",
     "issue.comments.read",
     "issue.comments.create",
     "agents.read",

package/dist/ui/index.js

@@ -34641,11 +34641,13 @@ function GitHubSyncIssueDetailTabContent(props) {
     forceVisible: true
   });
   const linkGitHubItem = usePluginAction("issue.linkGitHubItem");
+  const unlinkGitHubItem = usePluginAction("issue.unlinkGitHubItem");
   const toast = usePluginToast();
   const [manualLinkOpen, setManualLinkOpen] = useState2(false);
   const [manualLinkKind, setManualLinkKind] = useState2("issue");
   const [manualLinkReference, setManualLinkReference] = useState2("");
   const [manualLinkPending, setManualLinkPending] = useState2(false);
+  const [unlinkPending, setUnlinkPending] = useState2(false);
   useEffect2(() => {
     if (!props.companyId || !props.issueId) {
       return;
@@ -34703,6 +34705,36 @@ function GitHubSyncIssueDetailTabContent(props) {
       setManualLinkPending(false);
     }
   }
+  async function handleUnlinkGitHubItem() {
+    if (!props.companyId || !props.issueId || unlinkPending) {
+      return;
+    }
+    if (typeof window !== "undefined" && !window.confirm("Unlink this Paperclip issue from GitHub? GitHub Sync will stop updating it until it is linked again.")) {
+      return;
+    }
+    setUnlinkPending(true);
+    try {
+      await unlinkGitHubItem({
+        companyId: props.companyId,
+        issueId: props.issueId
+      });
+      await details.refresh();
+      notifyGitHubSyncPullRequestsChanged();
+      toast({
+        title: "GitHub link removed",
+        body: "This Paperclip issue is no longer linked to GitHub.",
+        tone: "success"
+      });
+    } catch (error) {
+      toast({
+        title: "Unable to unlink GitHub item",
+        body: getActionErrorMessage(error, "GitHub Sync could not remove this link."),
+        tone: "error"
+      });
+    } finally {
+      setUnlinkPending(false);
+    }
+  }
   return /* @__PURE__ */ jsxs2("section", { className: "ghsync-issue-detail", style: props.themeVars, children: [
     /* @__PURE__ */ jsx2("style", { children: EXTENSION_SURFACE_STYLES }),
     detailTabState === "loading" ? /* @__PURE__ */ jsx2("p", { className: "ghsync-extension-empty", children: "Loading GitHub sync details\u2026" }) : null,
@@ -34786,7 +34818,24 @@ function GitHubSyncIssueDetailTabContent(props) {
               }),
               children: /* @__PURE__ */ jsx2(GitHubButtonLabel, { label: "Open on GitHub" })
             }
-          ) : null
+          ) : null,
+          /* @__PURE__ */ jsx2(
+            "button",
+            {
+              type: "button",
+              className: getPluginActionClassName({
+                variant: "danger",
+                size: "sm",
+                extraClassName: "ghsync-extension-link"
+              }),
+              disabled: unlinkPending,
+              onClick: () => {
+                void handleUnlinkGitHubItem();
+              },
+              title: "Unlink from GitHub",
+              children: /* @__PURE__ */ jsx2(LoadingButtonContent, { busy: unlinkPending, label: "Unlink", busyLabel: "Unlinking" })
+            }
+          )
         ] })
       ] }),
       /* @__PURE__ */ jsxs2("div", { className: "ghsync-extension-grid", children: [