Fix Dockerfile conflict markers broken on main (#3)

* Fix conflict markers on main and guard CI against them

PR #2 merged before the Dockerfile cleanup landed, leaving <<<<<<<
markers that break docker compose build. Restore clean Docker files
and fail CI if conflict markers appear in the tree.

* Add CI check that fails on merge conflict markers

* Narrow conflict-marker CI check to <<<<<<< and >>>>>>>

---------

Co-authored-by: Cursor Agent <[email protected]>
This commit is contained in:
Nick Trochalakis
2026-08-23 23:32:54 +00:00
committed by GitHub
co-authored by Cursor Agent
parent d3ed4566b7
commit 5aa5fef9af
4 changed files with 10 additions and 41 deletions
+10
View File
@@ -10,6 +10,16 @@ jobs:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Reject merge conflict markers
run: |
if git grep -nE '^(<<<<<<<|>>>>>>>)' -- . \
':(exclude)package-lock.json'; then
echo "::error::Merge conflict markers found in tracked files"
exit 1
fi
echo "No conflict markers found"
- uses: actions/setup-node@v4
with:
node-version: "22"