Skip to content

chore(ci): remove un-instantiated e2e.yml (0 jobs, permanently failing) - #24

Merged
hyperpolymath merged 1 commit into
mainfrom
chore/remove-uninstantiated-e2e
Jul 28, 2026
Merged

chore(ci): remove un-instantiated e2e.yml (0 jobs, permanently failing)#24
hyperpolymath merged 1 commit into
mainfrom
chore/remove-uninstantiated-e2e

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

This repos .github/workflows/e2e.ymlis an **un-instantiated scaffold**:jobs:is present but every job block is commented out. An emptyjobs:map is invalid, so the run dies with **0 jobs** andconclusion=failure— permanently, on every push touchingsrc/, ffi/ortests/**`.

It has never run a single test, so nothing is lost by removing it.

Why delete rather than instantiate: comparing git blob SHAs against a known-pure template clone shows this repos src/` is the RSR scaffold, differing in at most 4 files (largely just the repo name). There is no project-specific behaviour here to exercise end-to-end yet, and a job written anyway would pass without testing anything — a fake gate.

Debt recorded, not hidden: this repo has no E2E coverage. When real code lands, add a genuine E2E job and prove it can fail. The scaffold remains available in the template repo.

🤖 Generated with Claude Code

jobs: is present but every job block is commented out. An empty jobs: map is
invalid, so the run dies with 0 jobs and conclusion=failure on every push that
touches src/**, ffi/** or tests/**. It has never run a test.

Deleted rather than instantiated: blob-SHA comparison against a pure template
clone shows this repo's src/ differs from the scaffold in <=4 files, so there is
no project behaviour to exercise end-to-end. Writing a job anyway would pass
without testing anything -- a fake gate.

Debt: this repo has NO e2e coverage, and this file never provided any.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@sonarqubecloud

Copy link
Copy Markdown

@gitar-bot

gitar-bot Bot commented Jul 28, 2026

Copy link
Copy Markdown
CI failed: The root shape check failed in CI because the new .githooks/ directory was added to the repository root without updating the root allowlist.

Overview

1 change-related failure found across 1 analyzed log, caused by a repository structure validation check failing on a newly added root directory.

Failures

Root Shape Validation Failure (confidence: high)

  • Type: build
  • Affected jobs: 90322202542
  • Related to change: yes
  • Root cause: The script scripts/check-root-shape.sh validates that all root directory entries are allowlisted. The PR added a new .githooks/ directory at the repository root, but did not add it to .machine_readable/root-allow.txt.
  • Suggested fix: Add .githooks/ to .machine_readable/root-allow.txt or move the .githooks directory into an appropriate existing subdirectory.

Summary

  • Change-related failures: 1 failure due to a missing entry in the root allowlist for .githooks/
  • Infrastructure/flaky failures: 0
  • Recommended action: Update .machine_readable/root-allow.txt to include .githooks/ or relocate the directory.
Code Review ✅ Approved

Removes the un-instantiated, permanently failing e2e.yml workflow scaffold since it contains zero jobs and has never run tests. No issues found.

Auto-approved and auto-merge armed: No blocking issues found.
Please see Auto-approve Docs for details on setting custom approval criteria. — merges when pipeline and required approvals pass.

Tip

Comment Gitar fix CI or enable auto-apply: gitar auto-apply:on

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Auto-apply Compact
gitar auto-apply:on         
gitar display:verbose         

Was this helpful? React with 👍 / 👎 | Gitar

@hyperpolymath
hyperpolymath merged commit 2a4a32b into main Jul 28, 2026
43 of 45 checks passed
@hyperpolymath
hyperpolymath deleted the chore/remove-uninstantiated-e2e branch July 28, 2026 15:28
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