You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue was created from a legacy filesystem backlog card. GitHub Issues are now the live work tracker; repository docs remain Method evidence.
Source backlog: docs/method/backlog/cool-ideas/PROCESS_remote-issue-deletion-sync.md
Original lane: cool-ideas
Original legend: PROCESS
Original backlog card
Remote Issue Deletion Sync
Support an explicit policy for what METHOD should do when a synced remote
issue is deleted or otherwise disappears. Today that case is mostly a
silent edge, but a real sync layer should decide whether to archive the
local item, warn loudly, or preserve it with a remote-tombstone marker.
#18 - Land 0030-0033 repo-truth and MCP debt fixes [merged]
📝 Issue Planner
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
GitHub Issues are now the canonical Method work tracker, so Method no longer needs a two-way remote-deletion sync policy for filesystem backlog mirrors. If a future problem appears around deleted GitHub Issues, renamed issues, or imported external trackers, it should be filed as a concrete GitHub-canonical lifecycle issue rather than resurrecting local mirror sync as the authority model.
Activity
coderabbitai commentedon Jun 1, 2026
🔗 Related PRs
#18 - Land 0030-0033 repo-truth and MCP debt fixes [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
flyingrobots commentedon Jun 1, 2026
Closing as obsolete after #27.
GitHub Issues are now the canonical Method work tracker, so Method no longer needs a two-way remote-deletion sync policy for filesystem backlog mirrors. If a future problem appears around deleted GitHub Issues, renamed issues, or imported external trackers, it should be filed as a concrete GitHub-canonical lifecycle issue rather than resurrecting local mirror sync as the authority model.