Skip to content

Fix GitHub synchronization after Planfile ticket archival #8

Open

Description

@tom-sapletta-com

Reproduction: complete a Planfile ticket with an existing GitHub sync mapping. Planfile moves it from current.yaml to a history sprint; planfile sync github --direction to then reports no local tickets and leaves the GitHub issue open.\n\nAcceptance criteria:\n1. Sync discovers mapped tickets in active and archived/history sprints.\n2. A completed ticket closes its mapped GitHub issue.\n3. A dry run reports the intended close without mutating GitHub.\n4. Add a regression test covering the archival path.

Reproduction: complete a Planfile ticket with an existing GitHub sync mapping. Planfile moves it from current.yaml to a history sprint; planfile sync github --direction to then reports no local tickets and leaves the GitHub issue open.\n\nAcceptance criteria:\n1. Sync discovers mapped tickets in active and archived/history sprints.\n2. A completed ticket closes its mapped GitHub issue.\n3. A dry run reports the intended close without mutating GitHub.\n4. Add a regression test covering the archival path.

Activity

  1. added
    priority-highAuto-created label for priority-high
    planfileAuto-created label for planfile
    managedAuto-created label for managed
    github-syncAuto-created label for github-sync
    regressionAuto-created label for regression
    and removed on Sep 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    github-syncAuto-created label for github-syncmanagedAuto-created label for managedplanfileAuto-created label for planfilepriority-highAuto-created label for priority-highregressionAuto-created label for regression

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions