Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

クローズ
  • 何か問題がありますか？
#1,896 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@Makisuo がすでに取り組んでいます。

2026年10月28日 から。

  • #1940 @Makisuo による — オープン

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
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時間 34分
マージ済み PR（30日）
687

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

MapleTechLabs/maple のほかの issue

MapleTechLabs/maple の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。