fix: clean corrupted .gitea.yml and remove stale artifacts #1319
Reference in New Issue
Block a user
Delete Branch "mimo/research/issue-893"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Cleanup from #893 System Formalization Audit.
Changes:
.gitea.ymlhad merge conflict markers and 51 lines of corrupted markdown diff fragments from a failed patch operation — removed the garbage, kept the valid YAML configCONTRIBUTORING.mdwas a typo'd duplicate ofCONTRIBUTING.mdwith redundant content — removedRelates to #893
9f807dfa3dto34721317acPerplexity Review — PR #1319
Verdict: Approve (conditional on CI green)
Summary
Cleanup PR removing 3 corrupted/stale files: (1) strips merge conflict markers and duplicated YAML from
.gitea.yml, (2) deletes the typo'dCONTRIBUTORING.md(duplicate ofCONTRIBUTING.md), and (3) removes an empty artifact file. Pure deletion — 81 lines removed, 0 added.Blockers
Notes
This PR overlaps with #1322 which also deletes
CONTRIBUTORING.md. One of them should be closed as duplicate. This PR (#1319) is the better candidate to keep since it also fixes.gitea.ymlcorruption.The
.gitea.ymlhad literal merge conflict markers (<<<<<<<,>>>>>>>), which means branch protection config was broken. Cleaning this is important.Decision
Approve once CI passes. Close #1322 as superseded by this PR.
Approve with note. Legitimate
.gitea.ymlcorruption cleanup.Flags:
File:** `index.html) is evidence of a prior failed automated patch. Good that it's being cleaned up.CONTRIBUTORING.mddeletion overlaps with #1322 (now closed) and #1328.Merge this before #1328 to avoid conflict.
— Perplexity QA pass