chore: sync workflow templates by stranske · Pull Request #127 · stranske/Template

stranske · 2026-01-07T22:04:00Z

Sync Summary

Files Updated

fix_merge_conflicts.md: Conflict resolution prompt - instructs Codex to resolve merge conflicts
conflict_detector.js: Conflict detector - identifies merge conflicts for targeted resolution
issue_formatter.py: Issue formatter - converts raw text to AGENT_ISSUE_TEMPLATE format
llm_provider.py: LLM provider configuration - GitHub Models and OpenAI client setup
LABELS.md: Label definitions and usage

Files Skipped

pr-00-gate.yml: File exists and sync_mode is create_only
ci.yml: File exists and sync_mode is create_only
dependabot.yml: File exists and sync_mode is create_only

Review Checklist

CI passes with updated workflows
No repo-specific customizations were overwritten

Source: stranske/Workflows
Manifest: .github/sync-manifest.yml

Automated sync from stranske/Workflows Template hash: 41168ff7e352 Changes synced from sync-manifest.yml

github-actions · 2026-01-07T22:04:10Z

⚠️ Action Required: Unable to determine source issue for PR #127. The PR title, branch name, or body must contain the issue number (e.g. #123, branch: issue-123, or the hidden marker ).

github-actions · 2026-01-07T22:04:24Z

🤖 Keepalive Loop Status

PR #127 | Agent: Codex | Iteration 0/5

Current State

Metric	Value
Iteration progress	[----------] 0/5
Action	wait (missing-agent-label)
Disposition	skipped (transient)
Gate	success
Tasks	0/8 complete
Keepalive	❌ disabled
Autofix	❌ disabled

🔍 Failure Classification

github-actions · 2026-01-07T22:04:58Z

github-actions · 2026-01-07T22:04:59Z

Autofix updated these files:

scripts/langchain/issue_formatter.py

Copilot

Pull request overview

This PR synchronizes workflow templates from the stranske/Workflows repository, adding merge conflict resolution capabilities and updating LangChain issue formatting documentation. The sync introduces new tooling for automated conflict detection and adds LangSmith tracing support for LLM operations.

Key Changes

Added LangSmith tracing integration to the LLM provider with optional observability features
Introduced conflict detection system with multi-source validation (GitHub API, CI logs, PR comments)
Updated label documentation to reflect streamlined issue formatting workflow with clearer descriptions

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 12 comments.

File	Description
`tools/llm_provider.py`	Adds LangSmith tracing setup with environment configuration for optional observability
`docs/LABELS.md`	Updates agent label documentation, removes deprecated labels, clarifies issue formatting workflow
`.github/scripts/conflict_detector.js`	New conflict detection module with GitHub API integration and multi-source conflict validation
`.github/codex/prompts/fix_merge_conflicts.md`	New Codex prompt template providing step-by-step merge conflict resolution instructions

Copilot · 2026-01-07T22:09:05Z

+            console.debug(`Could not download logs for job ${job.id}: ${logError.message}`);
+            continue;
+          }
+        }
+      } catch (jobError) {
+        console.debug(`Could not list jobs for run ${run.id}: ${jobError.message}`);


The comment states "debug" but uses console.debug() which may not be visible in GitHub Actions logs by default (depends on log level configuration). Consider using console.log() or console.warn() for better visibility in CI environments, or document the required log level settings.

Suggested change

console.debug(`Could not download logs for job ${job.id}: ${logError.message}`);

continue;

}

}

} catch (jobError) {

console.debug(`Could not list jobs for run ${run.id}: ${jobError.message}`);

console.warn(`Could not download logs for job ${job.id}: ${logError.message}`);

continue;

}

}

} catch (jobError) {

console.warn(`Could not list jobs for run ${run.id}: ${jobError.message}`);

Copilot · 2026-01-07T22:09:06Z

+  /fix conflicts and then commit/i,
+  /Merge branch .* into .* failed/i,
+  /<<<<<<< HEAD/,
+  /=======\n/,


The regex pattern /=======\n/ specifically requires a newline character after the conflict marker, but conflict markers may appear with different whitespace (e.g., ======= followed by spaces, different line endings like \r\n on Windows, or no trailing whitespace). Consider using /=======\s*$/m with multiline flag to match the conflict marker more reliably across different environments.

Suggested change

/=======\n/,

/=======\s*$/m,

Copilot · 2026-01-07T22:09:06Z

+| `agents:format` | Issue labeled | Formats raw issue into AGENT_ISSUE_TEMPLATE |
+| `agents:formatted` | Auto-applied | Issue has been formatted by LangChain |


The table rows on lines 14-15 are being inserted between row 13 and row 16, but the formatting creates a visual break. The agents:format and agents:formatted labels should maintain consistent table alignment with the other rows. Ensure proper markdown table continuation without the mid-table insertion causing rendering issues.

Copilot · 2026-01-07T22:09:06Z

-**Workflow:** `agents-70-orchestrator.yml` (Agents 70 Orchestrator)
+**Prerequisites:**
+- Issue must have non-empty body text
+- Repository must have `OPENAI_API_KEY` secret for LLM mode (optional)


The line "- Repository must have OPENAI_API_KEY secret for LLM mode (optional)" is contradictory. If it's optional, rephrase to clarify: "- Repository should have OPENAI_API_KEY secret for LLM-powered formatting (falls back to regex if not available)" or similar wording that makes the optionality clear.

Suggested change

- Repository must have `OPENAI_API_KEY` secret for LLM mode (optional)

- Repository should have `OPENAI_API_KEY` secret for LLM-powered formatting (falls back to regex if not available)

Copilot · 2026-01-07T22:09:07Z

+   ```bash
+   git fetch origin {{base_branch}}
+   ```
+   > Note: Replace `{{base_branch}}` with the actual base branch name (e.g., `main` or `master`)


The template variable {{base_branch}} is used but may not be replaced in all contexts. On line 26, the note says "Replace {{base_branch}} with the actual base branch name" which suggests manual replacement is expected. However, this contradicts the templating syntax which typically expects automatic substitution. Clarify whether this is a Handlebars/Mustache template that will be processed, or if users should manually replace these placeholders.

Suggested change

> Note: Replace `{{base_branch}}` with the actual base branch name (e.g., `main` or `master`)

> Note: `{{base_branch}}` will be automatically set to the PR's base branch (e.g., `main` or `master`).

Copilot · 2026-01-07T22:09:08Z

+            console.debug(`Could not download logs for job ${job.id}: ${logError.message}`);
+            continue;
+          }
+        }
+      } catch (jobError) {
+        console.debug(`Could not list jobs for run ${run.id}: ${jobError.message}`);


The comment states "debug" but uses console.debug() which may not be visible in GitHub Actions logs by default (depends on log level configuration). Consider using console.log() or console.warn() for better visibility in CI environments, or document the required log level settings.

Suggested change

console.debug(`Could not download logs for job ${job.id}: ${logError.message}`);

continue;

}

}

} catch (jobError) {

console.debug(`Could not list jobs for run ${run.id}: ${jobError.message}`);

console.warn(`Could not download logs for job ${job.id}: ${logError.message}`);

continue;

}

}

} catch (jobError) {

console.warn(`Could not list jobs for run ${run.id}: ${jobError.message}`);

Copilot · 2026-01-07T22:09:08Z

+from module import foo, bar
+=======
+from module import foo, baz
+>>>>>>> origin/{{base_branch}}


The template placeholder {{base_branch}} appears in the code comment within the example conflict marker. If this template is processed by a templating engine, this will be replaced even within the example code block, which could confuse the example. Consider escaping the placeholder or using a literal example like "origin/main" instead to ensure the example remains clear and unmodified.

Suggested change

>>>>>>> origin/{{base_branch}}

>>>>>>> origin/main

Copilot · 2026-01-07T22:09:08Z

+
+LangSmith Tracing:
+    Set these environment variables to enable LangSmith tracing:
+    - LANGSMITH_API_KEY: Your LangSmith API key
+    - LANGCHAIN_TRACING_V2: Set to "true" to enable tracing
+    - LANGCHAIN_PROJECT: Project name (default: "workflows-agents")
 """



The docstring has inconsistent formatting. The main module docstring ends at line 13, but then lines 15-19 add a new "LangSmith Tracing:" section after a blank line, which appears to be part of the docstring but breaks the typical docstring structure. This section should either be integrated into the main docstring above line 13, or moved to a separate comment block or documentation file. The current placement makes it unclear whether this is part of the module docstring or a separate comment.

Suggested change

LangSmith Tracing:

Set these environment variables to enable LangSmith tracing:

- LANGSMITH_API_KEY: Your LangSmith API key

- LANGCHAIN_TRACING_V2: Set to "true" to enable tracing

- LANGCHAIN_PROJECT: Project name (default: "workflows-agents")

"""

"""

# LangSmith Tracing:

# Set these environment variables to enable LangSmith tracing:

# - LANGSMITH_API_KEY: Your LangSmith API key

# - LANGCHAIN_TRACING_V2: Set to "true" to enable tracing

# - LANGCHAIN_PROJECT: Project name (default: "workflows-agents")

Copilot · 2026-01-07T22:09:08Z

+
+  const existingComment = comments.find(
+    (c) =>
+      c.body.includes('### ⚠️ Merge Conflict Detected') && c.user.type === 'Bot'


The conflict detection logic relies on checking c.user.type === 'Bot' (line 336) to find existing comments. However, GitHub Apps have user.type === 'Bot' while GitHub Actions using GITHUB_TOKEN have user.type === 'User'. This condition may fail to find existing comments posted by GitHub Actions workflows, leading to duplicate conflict comments. Consider also checking for the bot's specific login name or using a unique marker in the comment body to identify it reliably.

Suggested change

c.body.includes('### ⚠️ Merge Conflict Detected') && c.user.type === 'Bot'

c.body &&

c.body.includes('### ⚠️ Merge Conflict Detected') &&

c.body.includes('*Auto-detected by conflict detector*')

Copilot · 2026-01-07T22:09:09Z

+  const files = conflictResult.files.slice(0, 10); // Limit to 10 files
+  const fileList =
+    files.length > 0
+      ? `\n\n**Potentially affected files:**\n${files.map((f) => `- \`${f}\``).join('\n')}`
+      : '';
+


The comment states "Limit to 10 files" but the user receives no indication when files are truncated. If a PR has more than 10 conflicting files, the remaining files are silently omitted. Consider adding a note to the comment body when files are truncated, such as "...and X more files" to inform users that the list is incomplete.

Suggested change

const files = conflictResult.files.slice(0, 10); // Limit to 10 files

const fileList =

files.length > 0

? `\n\n**Potentially affected files:**\n${files.map((f) => `- \`${f}\``).join('\n')}`

: '';

const maxFilesToShow = 10;

const totalFiles = conflictResult.files.length;

const files = conflictResult.files.slice(0, maxFilesToShow); // Limit to 10 files

let fileList =

files.length > 0

? `\n\n**Potentially affected files:**\n${files.map((f) => `- \`${f}\``).join('\n')}`

: '';

if (totalFiles > maxFilesToShow) {

const remainingCount = totalFiles - maxFilesToShow;

fileList += `\n- _...and ${remainingCount} more file${remainingCount === 1 ? '' : 's'}_`;

}

chore: sync workflow templates from Workflows repo

c97d8ea

Automated sync from stranske/Workflows Template hash: 41168ff7e352 Changes synced from sync-manifest.yml

Copilot AI review requested due to automatic review settings January 7, 2026 22:04

stranske added sync Automated sync from Workflows automated Automated sync from Workflows labels Jan 7, 2026

stranske temporarily deployed to agent-standard January 7, 2026 22:04 — with GitHub Actions Inactive

github-actions Bot added the autofix Let bots format/lint automatically label Jan 7, 2026

chore(autofix): formatting/lint

dd301e9

github-actions Bot added the autofix:patch Autofix patch available label Jan 7, 2026

Copilot started reviewing on behalf of stranske January 7, 2026 22:05 View session

github-actions Bot removed the autofix:patch Autofix patch available label Jan 7, 2026

Copilot AI reviewed Jan 7, 2026

View reviewed changes

stranske merged commit f135377 into main Jan 8, 2026
27 checks passed

stranske deleted the sync/workflows-41168ff7e352 branch January 8, 2026 01:54

		\| `agents:format` \| Issue labeled \| Formats raw issue into AGENT_ISSUE_TEMPLATE \|
		\| `agents:formatted` \| Auto-applied \| Issue has been formatted by LangChain \|

	- Repository must have `OPENAI_API_KEY` secret for LLM mode (optional)
	- Repository should have `OPENAI_API_KEY` secret for LLM-powered formatting (falls back to regex if not available)

	> Note: Replace `{{base_branch}}` with the actual base branch name (e.g., `main` or `master`)
	> Note: `{{base_branch}}` will be automatically set to the PR's base branch (e.g., `main` or `master`).

-  const files = conflictResult.files.slice(0, 10); // Limit to 10 files
-  const fileList =
-    files.length > 0
-      ? `\n\n**Potentially affected files:**\n${files.map((f) => `- \`${f}\``).join('\n')}`
-      : '';
+  const maxFilesToShow = 10;
+  const totalFiles = conflictResult.files.length;
+  const files = conflictResult.files.slice(0, maxFilesToShow); // Limit to 10 files
+  let fileList =
+    files.length > 0
+      ? `\n\n**Potentially affected files:**\n${files.map((f) => `- \`${f}\``).join('\n')}`
+      : '';
+  if (totalFiles > maxFilesToShow) {
+    const remainingCount = totalFiles - maxFilesToShow;
+    fileList += `\n- _...and ${remainingCount} more file${remainingCount === 1 ? '' : 's'}_`;
+  }

Conversation

stranske commented Jan 7, 2026

Sync Summary

Files Updated

Files Skipped

Review Checklist

Uh oh!

github-actions Bot commented Jan 7, 2026

Uh oh!

github-actions Bot commented Jan 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🤖 Keepalive Loop Status

Current State

🔍 Failure Classification

Uh oh!

github-actions Bot commented Jan 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented Jan 7, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Key Changes

Reviewed changes

Uh oh!

Copilot AI Jan 7, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 7, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 7, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 7, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 7, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 7, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 7, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 7, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 7, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 7, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

github-actions Bot commented Jan 7, 2026 •

edited

Loading

github-actions Bot commented Jan 7, 2026 •

edited

Loading