Understand any codebase instantly. System intelligence for codebases, built for humans and AI.
TypeScript aiai-memoryclaude-codeclicode-analysiscode-mappingcode-memorycodebase-understandingcodexdeveloper-toolsllmopenclawpersistent-memoryprogram-analysissoftware-architecturesystem-intelligencesystem-mapping
ci: accept a leading [jarvis] tag in the conventional title check (#857)
Ian Hockbf412c1ec36a
diff --git a/.github/workflows/pr-title.yml b/.github/workflows/pr-title.ymlindex 44b08b76..62c7b19f 100644--- a/.github/workflows/pr-title.yml+++ b/.github/workflows/pr-title.yml@@ -31,3 +31,13 @@ jobs:perfchorerevert+ # Jarvis (the agent that opens PRs) prefixes its titles with a status tag:+ # "[jarvis] ", "[jarvis][review-blocked] ", "[jarvis][blocked: <reason>] ", ...+ # The pattern below is the action's default conventional header pattern+ # with an optional leading "[jarvis]" tag (plus further [...] groups and+ # whitespace). Everything after the tag is judged exactly as before; other+ # bracket prefixes still fail. The tag only lives on the PR title: when a+ # Jarvis PR is squash-merged it may be dropped from (or carried into) the+ # commit title depending on merge settings, so check the squash title.+ headerPattern: '^(?:\[jarvis\](?:\[[^\]]*\])*\s+)?(\w*)(?:\((.*)\))?!?: (.*)$'+ headerPatternCorrespondence: type, scope, subject