Skip to content

GitHub-only issue host: remove Forgejo, GitLab and git-bug write support #422

Closed

Description

@tannerpolley

Plan step 6 of #416. Owner decision (2026-11-16): GitHub only.

  • Remove active write support from the Forgejo, GitLab and git-bug issue adapters.
  • Keep historical issue records readable.
  • Don't delete migrations or stored data.
  • Update the Forgejo/GitLab sections of docs/operations/fork.md.

Activity

  1. tannerpolley commented on Nov 17, 2026

    @tannerpolley
    OwnerAuthor

    T3 Code status: Done

    Issue: #422 GitHub-only issue host: remove Forgejo, GitLab and git-bug write support

    Thread: thread:delegated-task:command%3Amcp%3Abb4592fc-a5b1-434a-94e6-fdbd212a677b%3Adelegate-task%3Aissue-422-github-only-2026-11-16

    Model: gpt-6.1-sol

    Branch: issue-422-github-only-issue-host-remove-forgejo

    Updated: 2026-11-17T00:19:07.034Z

  2. tannerpolley commented on Nov 17, 2026

    @tannerpolley
    OwnerAuthor

    T3 Code closeout: done

    Issue: #422 GitHub-only issue host: remove Forgejo, GitLab and git-bug write support
    Thread: thread:delegated-task:command%3Amcp%3Abb4592fc-a5b1-434a-94e6-fdbd212a677b%3Adelegate-task%3Aissue-422-github-only-2026-11-16
    Model: gpt-6.1-sol
    Branch: issue-422-github-only-issue-host-remove-forgejo
    Completed: 2026-11-17T00:19:07.971Z

    Implemented #422 and opened draft PR #431 from the synced main.

    • Removed Forgejo, GitLab, and git-bug issue adapters, login discovery, routing, and git-bug opt-in probing.
    • Preserved historical record contracts and all migrations. Stored summaries and links remain readable; retired hosts no longer support live issue fetching or writes.
    • Updated the fork guide to state GitHub-only active support and retain one line about the Forgejo archive.
    • Removed 4,266 lines, added 58: net −4,208. Upstream-owned files shrank by 26 net lines.

    Verification: 320 tests passed across 23 files, including GitHub issue flows, issue work, core toolkits, historical decoding, and migrations. Server, web, and contracts typechecks passed. check:changed passed everything except the three known mobile type errors.

    Live userdata was untouched. Tool text did not change, so agentContextBudget.json needed no update. No browser verification was run; review and merge remain open.

    PR #431, head fdf21c5, checks and reviews: local checks as above; no hosted checks or reviews yet.

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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions