CopilotKit / CopilotKit/outpost
Linear sync go-live: deploy the service and verify a ticket round-trips
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7
- Forks
- 3
- Avg merge
- 7d 16h
- Merged PRs (30d)
- 15
Description
apps/linear-sync is built with a Dockerfile and health port 3004, but is not deployed. It requires three secrets and will not start unless all three are present.
Checklist
- Create the Railway service pointed at
apps/linear-sync - Set all three required secrets (the service exits at boot if any is missing)
- Verify
/healthon3004returns green - Confirm the worker reports the Linear adapter as registered (see #161)
- Verify one ticket round-trips Outpost → Linear → Outpost
Depends on the open decisions in the sync-decisions issue — specifically which Linear team receives issues, and whether all tickets or only escalated ones are pushed. Deploying before those are settled risks flooding a real Linear team.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with apps/linear-sync/Dockerfile and the /health endpoint on port 3004, then read #161 and the sync-decisions issue before creating anything. Done means the Railway service has all three secrets, reports the Linear adapter as registered, returns a healthy response, and completes one approved ticket round-trip without flooding a real team.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- backend, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100