Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Alerting: Linear as a destination type, opening one issue per incident

未关闭
  • 哪里不对？
#1,896 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@Makisuo 已经在做这个了。

开始于 2026年10月28日。

  • #1940 来自 @Makisuo —— 未关闭

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript
领域
backend

调研方向

Start in packages/backend/src/services/alerts/AlertDestinationDelivery.ts, especially composeLinkUrl, then trace how existing destination types such as Slack are configured and delivered through the alerts services. Read the webhook delivery/signature path and the integration configuration used to connect Slack. Done means a connectable linear destination can create an issue for a trigger, comment on renotify/resolve, link the incident, and composeLinkUrl yields an incident-specific URL.

由索引模型根据 Issue 内容生成。

描述

Written by an AI agent (Claude) on behalf of @jasonkuhrt.

A team that tracks its work in Linear can't send Maple alerts there. Linear isn't a destination type, so getting an incident into Linear means writing and hosting your own webhook endpoint.

Here's what that takes today. It's the Worker we're about to build for Heartbeat:

// Behind a `webhook` destination. Check x-maple-signature first.
// Linear accepts a caller-chosen UUID on create, so ids derived from
// incidentId and x-maple-delivery-key make Maple's retries harmless.
switch (body.eventType) {
	case "trigger":
		// Linear issueCreate in the team's Triage, id = uuid(incidentId).
	case "renotify":
	case "resolve":
		// Linear commentCreate on issue uuid(incidentId),
		// id = uuid(x-maple-delivery-key).
	case "test":
		// nothing
}

It also needs a Linear API key in the Worker's secrets, so every issue shows the key's owner as its creator, not Maple.

What we'd like to write instead, after connecting Linear once in Maple's integrations the way Slack is connected:

yield* Maple.AlertDestination("linear", {
	type: "linear",
	name: "Engineering triage",
	team_id: "…", // the Linear team whose Triage receives the issues
})

Maple would then open one issue per incident in that team, comment on it at renotify and resolve, link it back to the incident, and show itself as the issue's creator.

Linear's own Sentry integration is the precedent (https://linear.app/docs/sentry). Sentry alert rules can create Linear issues, a Sentry issue can link to a Linear issue, and completing the Linear issue resolves the Sentry one. Maple's error issues could work the same way: create or link a Linear issue from an error issue, and move the error issue to resolved when its Linear issue completes.

One related gap: the webhook reference describes linkUrl as "the incident in the Maple dashboard", but composeLinkUrl in packages/backend/src/services/alerts/AlertDestinationDelivery.ts builds /services/<name>, the same URL for every incident of a service. That's why the Worker above keys on incidentId, and its issue can only link to the service page.

主要语言
TypeScript
星标
1.8k
派生
120
平均合并
8 小时 11 分钟
30 天内合并 PR
667

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

MapleTechLabs/maple 的其他 Issue

查看 MapleTechLabs/maple 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。