self-development: replace git fetch --unshallow with --depth 100

[kelos-bot]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Removes git fetch --unshallow || true from all self-development workflow templates and replaces it with git fetch origin main --depth 100. This avoids downloading full repository history when only recent commits are needed for rebasing, improving performance of CI workflows.

Which issue(s) this PR is related to:

Fixes #953

Special notes for your reviewer:

Changes are in 4 self-development YAML files:

• kelos-squash-commits.yaml
• kelos-workers.yaml
• kelos-pr-responder.yaml
• kelos-reviewer.yaml

Does this PR introduce a user-facing change?

NONE

---

Summary by cubic

Switch self-development workflows from git fetch --unshallow to git fetch <remote> main --depth 100 to fetch only recent commits and speed up CI rebases. Applies to kelos-squash-commits.yaml, kelos-workers.yaml, kelos-pr-responder.yaml, and kelos-reviewer.yaml; fixes #953.

^{Written for commit 483bf68. Summary will update on new commits.}

[cubic-dev-ai]

3 issues found across 4 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="self-development/kelos-squash-commits.yaml">

<violation number="1" location="self-development/kelos-squash-commits.yaml:60">
P2: Fetching `main` with fixed depth can break later `git merge-base`/squash steps for older branches. Ensure full history is available when the merge-base is outside the shallow window.</violation>
</file>

<file name="self-development/kelos-reviewer.yaml">

<violation number="1" location="self-development/kelos-reviewer.yaml:98">
P1: Fetching `main` with a fixed depth can miss the merge-base used by `git diff origin/main...HEAD`, causing incomplete or failing reviews for older PR branches.</violation>
</file>

<file name="self-development/kelos-workers.yaml">

<violation number="1" location="self-development/kelos-workers.yaml:99">
P2: Using a fixed shallow fetch depth can break rebases for older branches when the merge base is deeper than 100 commits.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

P1: Fetching main with a fixed depth can miss the merge-base used by git diff origin/main...HEAD, causing incomplete or failing reviews for older PR branches.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At self-development/kelos-reviewer.yaml, line 98:

<comment>Fetching `main` with a fixed depth can miss the merge-base used by `git diff origin/main...HEAD`, causing incomplete or failing reviews for older PR branches.</comment>

<file context>
@@ -92,11 +92,10 @@ spec:
         ```
-        git fetch --unshallow || true
-        git fetch origin main
+        git fetch origin main --depth 100
         ```
 
</file context>

Suggested change

	git fetch origin main --depth 100
	git fetch --unshallow || true
	git fetch origin main

[cubic-dev-ai]

P2: Fetching main with fixed depth can break later git merge-base/squash steps for older branches. Ensure full history is available when the merge-base is outside the shallow window.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At self-development/kelos-squash-commits.yaml, line 60:

<comment>Fetching `main` with fixed depth can break later `git merge-base`/squash steps for older branches. Ensure full history is available when the merge-base is outside the shallow window.</comment>

<file context>
@@ -55,10 +55,9 @@ spec:
          ```
-         git fetch --unshallow || true
-         git fetch origin main
+         git fetch origin main --depth 100
          ```
 
</file context>

Suggested change

	git fetch origin main --depth 100
	git fetch origin main --depth 100
	git merge-base origin/main HEAD >/dev/null 2>&1 || git fetch --unshallow

[cubic-dev-ai]

P2: Using a fixed shallow fetch depth can break rebases for older branches when the merge base is deeper than 100 commits.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At self-development/kelos-workers.yaml, line 99:

<comment>Using a fixed shallow fetch depth can break rebases for older branches when the merge base is deeper than 100 commits.</comment>

<file context>
@@ -96,7 +96,7 @@ spec:
       - 0. Set up your working branch. Run this exactly:
         ```
-        git fetch --unshallow || true; git fetch origin main; git rebase origin/main
+        git fetch origin main --depth 100; git rebase origin/main
         ```
       - 1. Check if a PR already exists for branch kelos-task-{{.Number}}.
</file context>

Suggested change

	git fetch origin main --depth 100; git rebase origin/main
	git fetch origin main --depth 100; git rebase origin/main || (git fetch --unshallow origin main && git rebase origin/main)