Bundled tracker services move to core - #230
Merged
Merged
Conversation
czpython
force-pushed
the
bundled-services-in-core
branch
from
August 10, 2026 09:06
e96bbb3 to
b432690
Compare
czpython
enabled auto-merge (squash)
August 10, 2026 09:06
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Linear and Jira relocate from ship's
services.pyintocore/services.py, beside the GitHub App. Behavior is unchanged — same service keys, same rows, same cards, same verify; ship still reads the rows and keeps every piece of policy (the tracker selector, statuses,get_tracker, its webhooks, the tracker check).The rule this settles: core declares the appliance's bundled integrations — its own offering; an extension declares a service only when it brings a new integration to the appliance. Consumers read rows by key regardless of who declared them. This also structurally removes the shared-provider collision for first-party services: core declares once, any extension reads.
Mechanics: the Linear GraphQL URL constant hoists into core and ship's ticketing client now imports it from there — the dependency flips to the legal direction (ship → core). No wire, frontend, or row changes; no migration; nothing to redo on live boxes (connected rows are keyed by service string, not by declarer).
🤖 Generated with Claude Code