Skip to content

Conversation

@patchmemory
Copy link
Owner

Problem

The dev-submodule-sync workflow fails on every merge to main with:

fatal: repository 'https://github.com/patchmemory/scidk-dev.git/' not found
fatal: clone of 'https://github.com/patchmemory/scidk-dev.git' into submodule path failed

This happens because GitHub Actions cannot access the private scidk-dev repository.

Solution

Remove the automated submodule sync workflow entirely. The dev submodule pointer is managed manually when merging, which is the correct approach for this repository setup.

Changes

  • Removed: .github/workflows/dev-submodule-sync.yml

Result

  • ✅ No more failing CI jobs on merge to main
  • ✅ Manual control over dev submodule pointer updates remains
  • ✅ Simpler CI with only essential tests (pytest + E2E)

🤖 Generated with Claude Code

Co-Authored-By: Claude noreply@anthropic.com

The dev-submodule-sync workflow consistently fails with 'Repository not found'
because GitHub Actions cannot access the private scidk-dev repository.

Issue: CI always fails on merge to main with:
  fatal: repository 'https://github.com/patchmemory/scidk-dev.git/' not found
  fatal: clone of 'https://github.com/patchmemory/scidk-dev.git' into submodule path '/home/runner/work/scidk/scidk/dev' failed

Solution: Remove automated submodule sync entirely. The dev submodule pointer
is managed manually when merging, which is the correct approach for this setup.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@patchmemory patchmemory deleted the fix/remove-dev-submodule-workflow branch January 13, 2026 20:14
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.

2 participants