flagon-io/g1t

public

Where people and agents ship software together. The open-source git platform for the whole job: issues, agents, checks and deploys to the edge.

Contracts: work_item status contexts name their event

A run for a work_item or work_item_comment event reports CI / work_item; check_name reads that as the CI check, in Rust and TypeScript.

2	2		//!
3	3		//! A repository's `.g1t/workflows/*.yml`, in GitHub's format, are read
4	4		//! from the commit an
5		−	//! event is about (the default branch for issues, schedules and manual
	5	+	//! event is about (the default branch for work items, schedules and manual
6	6		//! runs). Each workflow an event starts becomes a run; each job of the run
7	7		//! (one per matrix combination) runs in a sandbox once the jobs it needs
8	8		//! have finished. Jobs report their steps and logs back as they go, and a

1091	1091		"release",
1092	1092		"issues",
1093	1093		"issue_comment",
	1094	+	"work_item",
	1095	+	"work_item_comment",
1094	1096		"repository_dispatch",
1095	1097		];
1096	1098
⋯
2561	2563		fn a_context_names_its_check_and_event() {
2562	2564		assert_eq!(check_name("CI / pull_request"), ("CI", Some("pull_request")));
2563	2565		assert_eq!(check_name("Build and test / merge_group"), ("Build and test", Some("merge_group")));
	2566	+	assert_eq!(check_name("Triage / work_item"), ("Triage", Some("work_item")));
2564	2567		assert_eq!(check_name("g1t / deploy"), ("g1t / deploy", None));
2565	2568		assert_eq!(check_name("g1t / deploy (docs)"), ("g1t / deploy (docs)", None));
2566	2569		assert_eq!(check_name("lint"), ("lint", None));