Better handling for required workflows

Return the workflow path from the run rather than trying to fetch the workflow information when the workflow information is missing or refers to a required workflow.
github · Jun 27, 2024 · 37b6ead · 37b6ead
1 parent 9b7c22c
commit 37b6ead
Show file tree

Hide file tree

Showing 3 changed files with 16 additions and 1 deletion.
diff --git a/lib/api-client.js b/lib/api-client.js
diff --git a/lib/api-client.js.map b/lib/api-client.js.map
diff --git a/src/api-client.ts b/src/api-client.ts
@@ -139,6 +139,14 @@ export async function getWorkflowRelativePath(): Promise<string> {
   );
   const workflowUrl = runsResponse.data.workflow_url;
 
+  const requiredWorkflowRegex = /\/repos\/[^/]+\/[^/]+\/actions\/required_workflows\/[^/]+/;
+  if (!workflowUrl || workflowUrl === "" || requiredWorkflowRegex.test(workflowUrl)) {
+    // For required workflows, the workflowUrl is invalid so we cannot fetch more informations
+    // about the workflow.
+    // However, the path is available in the original response.
+    return runsResponse.data.path as string;
+  }
+
   const workflowResponse = await apiClient.request(`GET ${workflowUrl}`);
 
   return workflowResponse.data.path as string;