Skip to content

fix(ci): resolve leftover merge-conflict markers in 3 files#72

Merged
hyperpolymath merged 1 commit into
mainfrom
fix-leftover-merge-conflict-markers
Jul 4, 2026
Merged

fix(ci): resolve leftover merge-conflict markers in 3 files#72
hyperpolymath merged 1 commit into
mainfrom
fix-leftover-merge-conflict-markers

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Summary

.github/workflows/instant-sync.yml, .github/workflows/semgrep.yml, and .github/FUNDING.yml all had unresolved <<<<<<< HEAD / ======= / >>>>>>> markers committed straight to main from a prior "sync from parent repo automation" merge. In all three cases both sides were identical (a duplicated SPDX header line) — collapsed to one copy, no other content change.

A file with literal conflict markers isn't valid YAML, so CI has been failing on every PR against this repo regardless of the PR's own diff, since the problem lives in the base branch itself, not any individual PR's changes.

🤖 Generated with Claude Code

.github/workflows/instant-sync.yml, .github/workflows/semgrep.yml, and
.github/FUNDING.yml all had unresolved <<<<<<< HEAD / ======= / >>>>>>>
markers committed straight to main from a prior "sync from parent repo
automation" merge. In all three cases both sides of the conflict were
identical (a duplicated SPDX header line) — collapsed to one copy.

A file with literal conflict markers isn't valid YAML, so CI (including
CodeQL's "actions" language analysis) has been failing on every PR
against this repo regardless of the PR's own diff, since the problem
lives in the base branch, not any individual PR.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@hyperpolymath
hyperpolymath merged commit 37b7649 into main Jul 4, 2026
17 of 20 checks passed
@hyperpolymath
hyperpolymath deleted the fix-leftover-merge-conflict-markers branch July 4, 2026 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant