From ee7a724b608fa30e3664bbc2e99e19e72559b15a Mon Sep 17 00:00:00 2001
From: Vincent Ambo <mail@tazj.in>
Date: Mon, 26 Dec 2022 13:16:10 +0300
Subject: fix(ops/pipelines): explicitly set contexts for annotations

I think what might be going on with b/231 is that the annotations
somehow started conflicting because they don't have contexts set.

Lets try setting a context and see if it changs anything ...

Change-Id: I62ed57f9e24f08e4e7215f05d35cfa769e2e2c24
Reviewed-on: https://cl.tvl.fyi/c/depot/+/7640
Reviewed-by: sterni <sternenseemann@systemli.org>
Autosubmit: tazjin <tazjin@tvl.su>
Tested-by: BuildkiteCI
---
 tools/rust-crates-advisory/default.nix | 1 +
 1 file changed, 1 insertion(+)

(limited to 'tools')

diff --git a/tools/rust-crates-advisory/default.nix b/tools/rust-crates-advisory/default.nix
index a187963473d6..da7eb7544703 100644
--- a/tools/rust-crates-advisory/default.nix
+++ b/tools/rust-crates-advisory/default.nix
@@ -114,6 +114,7 @@ depot.nix.readTree.drvTargets {
       command = buildkiteReportStep {
         command = [ depot-rust-crates-advisory-report ];
         style = "warning";
+        context = "depot-crate-advisories";
       };
     };
   };
-- 
cgit 1.4.1