Skip to content

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

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)#52
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>
@gitar-bot

gitar-bot Bot commented Jul 28, 2026

Copy link
Copy Markdown
CI failed: 4 CI validation failures occurred due to contract errors, banned ReScript files, missing OpenSSF state files, and unformatted Rust code; all jobs failed independently of the removed e2e workflow.

Overview

Multiple CI checks failed across the repository due to governance policy violations, missing configuration or contract files, and code formatting discrepancies.

Failures

K9 Contract Validation Failure (confidence: high)

  • Type: build
  • Affected jobs: 90322307657, 90322307732
  • Related to change: unclear
  • Root cause: The validation script validate-k9.sh encountered 8 errors while scanning K9 files (missing K9! magic number, missing pedigree blocks, and missing name field).
  • Suggested fix: Review the failing K9 contract files, ensure they start with the 'K9!' magic number on the first non-empty line, and include a valid pedigree block containing required metadata.

Banned ReScript File Violation (confidence: high)

  • Type: build
  • Affected jobs: 90322312583
  • Related to change: unclear
  • Root cause: Repository governance policy (cicd_rules/banned_language_file) detected a tracked ReScript file (affinescript/packages/affine-res/src/AffineScript.res) without an exemption.
  • Suggested fix: Remove the .res file or add an appropriate inline pragma / .hypatia-ignore entry if intentional.

OpenSSF Compliance Failure (confidence: high)

  • Type: configuration
  • Affected jobs: 90322307407
  • Related to change: unclear
  • Root cause: The OpenSSF compliance check failed because the required .machine_readable/STATE.a2ml file was missing from the repository.
  • Suggested fix: Create the .machine_readable directory and add the required STATE.a2ml file.

Rust Code Formatting Check Failure (confidence: high)

  • Type: tooling
  • Affected jobs: 90322568559
  • Related to change: yes
  • Root cause: The cargo fmt check failed because rustfmt reported formatting diffs in Rust source files.
  • Suggested fix: Run cargo fmt locally to format the codebase, review changes, and commit them.

Summary

  • Change-related failures: 1 (Rust formatting check failed due to unformatted code changes in the PR)
  • Infrastructure/flaky failures: 0
  • Recommended action: Run cargo fmt locally to fix formatting, address the missing OpenSSF and K9 validation configurations, and remove or exempt the banned ReScript file.
Code Review ✅ Approved

Removes the permanently failing, uninstantiated e2e.yml workflow scaffold that contained zero jobs. 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

@gitar-bot

gitar-bot Bot commented Jul 28, 2026

Copy link
Copy Markdown

⚠️ Gitar auto-approved this PR but could not enable auto-merge: auto-merge is disabled for this repository — enable "Allow auto-merge" in the repository settings.

@gitar-bot gitar-bot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gitar has auto-approved this PR and enabled auto-merge (configure)

@gitar-bot gitar-bot Bot added the gitar-approved Added by Gitar label Jul 28, 2026
@hyperpolymath
hyperpolymath merged commit 6760a17 into main Jul 28, 2026
36 of 41 checks passed
@hyperpolymath
hyperpolymath deleted the chore/remove-uninstantiated-e2e branch July 28, 2026 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gitar-approved Added by Gitar

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant