gitlab-triage 1.46.0 → 1.47.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 82a56fd407f0bb5dd6be0155a71267d214702b0c811a35b8d559d2fda1ae1b58
-  data.tar.gz: 8efe032a3e69a3ea5537798d0be00f96a976e10dd2d4fbd4c042d8c46fb8637f
+  metadata.gz: c3318627182a7f105d948f9c81f43db29dd3f271db82968a0d80623d42a4c6d8
+  data.tar.gz: c2c4a9208acef6b922382b8ac5e38a9d398fc55ea6d1fcac6d07bb45b7544712
 SHA512:
-  metadata.gz: e3be78f754d51d09ca12902d9414b34d7e342f9aca7a3eb48711a56f25c7669c87e879e52684b1d4bf094eae1e54717258340840f39bafab737f21e4e220ea5e
-  data.tar.gz: e95dcfc0963e88093fecffab883b34b5ceadf065cc73530bcde23ee74b87199e5cb79c0f8a040f866dc4da50c703ec11fb2ab9209b7d4c9283e8395b73be492c
+  metadata.gz: 07c2506ececee5455224d17d52c3fed0ec4be1b1f575bc0edec27dddd8093b824d794cbdc2d084179a881db8eb94e50506a75cebbee558cd66282a25c3a89776
+  data.tar.gz: d4f60985c3e2bb01c952fcadb1ac4669e9c792e5457d57f88f1684e87cafeaa0a6c38718a01e5d04e39a2acaed7da731dc2b59a9aa9d40a062c38fa3fb929ac5

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    gitlab-triage (1.46.0)
+    gitlab-triage (1.47.0)
       activesupport (>= 5.1)
       globalid (~> 1.0, >= 1.0.1)
       graphql (< 2.1.0)

data/README.md

@@ -1186,7 +1186,7 @@ resource_rules:
 
 ##### Delete action
 
-**This action is only applicable for branches.**
+**This action is only applicable for branches, issues and merge requests.**
 
 Delete the resource.
 
@@ -1220,6 +1220,55 @@ sub-policies' summary.
 Note that only the `summarize` keys in the sub-policies' `actions` is used. Any
 other keys (e.g. `mention`, `comment`, `labels` etc.) are ignored.
 
+#### Custom type summaries
+
+By default, summary rules fetch GitLab resources (issues, merge requests, etc.) and use them to generate the summary content. However, you can create summaries that pull data from external sources (like ClickHouse, Prometheus, or custom APIs) without fetching any GitLab resources.
+
+To create a custom summary, add `type: custom` to your rule definition:
+
+```yml
+resource_rules:
+  issues:
+    summaries:
+      - name: Weekly Report
+        rules:
+          - name: Bug Heatmap
+            conditions:
+              labels:
+                - bug
+            actions:
+              summarize:
+                title: "Bugs"
+                item: "- {{title}}"
+                summary: "{{items}}"
+          
+          - name: Quarantined Tests
+            type: custom  # Skip resource fetching
+            actions:
+              summarize:
+                title: "Quarantined Tests"
+                summary: |
+                  #{ fetch_quarantined_tests_from_clickhouse() }
+        actions:
+          summarize:
+            title: "Weekly Report"
+            summary: |
+              {{items}}
+```
+
+When `type: custom` is specified:
+- No GitLab resources are fetched
+- The `conditions` field is optional and ignored
+- The `item` field in `actions.summarize` is not needed
+- The summary is always included in the report (as long as it has a title)
+- You can use Ruby expressions in the `summary` field to fetch data from external sources
+
+This is useful for:
+- Including metrics from external monitoring systems
+- Aggregating data from multiple sources
+- Generating reports from custom databases
+- Adding static sections to your triage reports
+
 You can define such policy as follows:
 
 ```yml

data/lib/gitlab/triage/engine.rb

@@ -268,7 +268,7 @@ module Gitlab
         return if rule_definitions.blank?
 
         rule_definitions.each do |rule_definition|
-          resources_for_rule(resource_type, rule_definition) do |resources|
+          resources_for_rule(resource_type, rule_definition, in_summary: false) do |resources|
             policy = Policies::RulePolicy.new(
               resource_type, rule_definition, resources, network)
 
@@ -336,7 +336,7 @@ module Gitlab
       def summary_parts_for_rules(resource_type, rule_definitions)
         # { summary_rule => resources }
         parts = rule_definitions.each_with_object({}) do |rule_definition, result|
-          to_enum(:resources_for_rule, resource_type, rule_definition).each do |rule_resources, expanded_conditions|
+          to_enum(:resources_for_rule, resource_type, rule_definition, in_summary: true).each do |rule_resources, expanded_conditions|
             # We replace the non-expanded rule conditions with the expanded ones
             result.merge!(rule_definition.merge(conditions: expanded_conditions) => rule_resources)
           end
@@ -355,15 +355,27 @@ module Gitlab
       #
       # @param resource_type [String] The resource type, e.g. +issues+ or +merge_requests+.
       # @param rule_definition [Hash] A rule definition, e.g. +{ name: 'Foo', conditions: { milestone: 'v1' } }+.
+      # @param in_summary [Boolean] Whether this rule is part of a summary definition.
       #
       # @yieldparam rule_resources [PoliciesResources::RuleResources] An object which contains an array of resources.
       # @yieldparam expanded_conditions [Hash] A hash of expanded conditions.
       # @yieldreturn [nil]
       #
       # @return [nil]
-      def resources_for_rule(resource_type, rule_definition)
+      def resources_for_rule(resource_type, rule_definition, in_summary: false)
         puts Gitlab::Triage::UI.header("Gathering resources for rule: **#{rule_definition[:name]}**", char: '-')
 
+        # Skip resource fetching for custom type rules
+        if rule_definition[:type] == 'custom'
+          unless in_summary
+            raise ArgumentError, "type: custom can only be used in summary rules, not in top-level rules (rule: #{rule_definition[:name]})"
+          end
+
+          puts "\n* Skipping resource fetch for custom type rule"
+          yield(PoliciesResources::RuleResources.new([]), {})
+          return
+        end
+
         ExpandCondition.perform(rule_conditions(rule_definition)) do |expanded_conditions|
           # retrieving the resources for every rule is inefficient
           # however, previous rules may affect those upcoming

data/lib/gitlab/triage/entity_builders/summary_builder.rb

@@ -20,6 +20,7 @@ module Gitlab
           @resources = resources
           @network = network
           @separator = separator
+          @is_custom = policy_spec[:type] == 'custom'
         end
 
         def title
@@ -35,7 +36,7 @@ module Gitlab
         end
 
         def valid?
-          title =~ /\S+/ && any_resources?
+          title =~ /\S+/ && (@is_custom || any_resources?)
         end
 
         def any_resources?

data/lib/gitlab/triage/version.rb

@@ -2,6 +2,6 @@
 
 module Gitlab
   module Triage
-    VERSION = '1.46.0'
+    VERSION = '1.47.0'
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: gitlab-triage
 version: !ruby/object:Gem::Version
-  version: 1.46.0
+  version: 1.47.0
 platform: ruby
 authors:
 - GitLab
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2025-12-16 00:00:00.000000000 Z
+date: 2026-02-03 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport