a8ebd390fa
* refactor(forge): forge-neutral foundation (GitHub-only) Decouple git-hosting from GitHub behind a neutral abstraction (issue #1616), GitHub-only for now; existing GitHub behaviour is unchanged. - Forge manifest, neutral ForgeService contract, forge registry + resolver, and a client forge-module registry. - GitHub code renamed to the neutral shape; PR/Issue attachment wording preserved. - forge.search.response enums parse tolerantly (unknown kind/auth state degrade instead of breaking the client). - createPullRequest reports typed CLI/auth errors instead of a generic message. - forge-resolver host/remote caches are LRU-bounded. - Forge host trust is explicit: only a known cloud host or a CLI-authenticated host is ever talked to; an unauthenticated GitHub Enterprise host fails resolution instead of routing to github.com. - Docs: forge-providers guide, glossary and i18n forge-copy conventions, architecture and rpc-namespacing terminology. - Vitest React Native mocks (unistyles, svg, linking, lucide) consolidated into shared aliased test-stubs. * feat(forge): GitLab adapter, forge-aware UI, pipelines and approvals GitLab adapter over the glab CLI on the neutral contracts: MR status, forge-aware UI, pipeline tree, and N-of-M approvals. - threadIsResolved is part of the neutral timeline item. - Pipeline load failures show an error instead of an empty section. - Manual pipeline jobs render as pending. - Fork/detached MR head pipelines are fetched by MR iid (glab ci get --merge-request). * feat(forge): Gitea family adapter (Gitea, Forgejo, Codeberg) One adapter over the tea CLI serving Gitea, Forgejo, and Codeberg on the neutral contracts. - CI status aggregates commit statuses and Actions runs together. - Gitea's terminal "warning" state maps to failure on server and client. - Gitea Actions check details are reachable from the PR pane by workflowRunId. * refactor(forge): localize compatibility handling * test(forge): expect normalized GitLab facts --------- Co-authored-by: Mohamed Boudra <boudra.moha@gmail.com>
35 lines
1.2 KiB
TypeScript
35 lines
1.2 KiB
TypeScript
/**
|
|
* Compatibility exports for tests and non-visual derivations. Rich PR-pane
|
|
* contributions now come from client forge modules and validate the open
|
|
* `forgeSpecific` envelope at runtime.
|
|
*/
|
|
import type { CheckoutPrStatusResponse } from "@getpaseo/protocol/messages";
|
|
import type { Forge } from "@/git/forge";
|
|
import { CLIENT_FORGE_LOGIC_MODULES } from "@/git/forges";
|
|
import type { PrPaneCheck } from "./data";
|
|
|
|
type CheckoutPrStatus = NonNullable<CheckoutPrStatusResponse["payload"]["status"]>;
|
|
|
|
const CLIENT_NATIVE_FALLBACK_CONTRIBUTIONS = CLIENT_FORGE_LOGIC_MODULES.flatMap(
|
|
(module) => module.facts?.nativeFallbackChecks ?? [],
|
|
);
|
|
|
|
/**
|
|
* Fallback check rows for a status whose forge reports no individual checks.
|
|
* Returns [] for forges that don't synthesize one.
|
|
*/
|
|
export function getNativeFallbackChecks(status: CheckoutPrStatus, forge: Forge): PrPaneCheck[] {
|
|
const facts = status.forgeSpecific;
|
|
if (!facts) {
|
|
return [];
|
|
}
|
|
const checks: PrPaneCheck[] = [];
|
|
for (const contribute of CLIENT_NATIVE_FALLBACK_CONTRIBUTIONS) {
|
|
const check = contribute.contribute(facts, status, forge);
|
|
if (check) {
|
|
checks.push(check);
|
|
}
|
|
}
|
|
return checks;
|
|
}
|