redhat-et / redhat-et/ProtoBot

Add the CI validation gate and seed ProtoBot's specification store

Open
#111 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

blocked component:ears-manager
Dominant language
Go
Stars
5
Forks
6
Avg merge
23h 24m
Merged PRs (30d)
66

Description

Plan ID

EM-08

Purpose

Make ears-manager part of ProtoBot's own repository workflow and prove the first release is usable in CI.

Scope

  • Build and test the Go binary in CI.
  • Run ears-manager check on specification branches as a merge gate.
  • Seed ProtoBot's initial .protobot configuration, artifact registry, and representative records through the governed path.
  • Detect direct edits to registered specification files before merge.
  • Document the local developer command and CI failure/retry behavior.

Dependencies

Depends on EM-07. The command and validation behavior comes from EM-02 through EM-05.

Acceptance criteria

  • CI fails on malformed records, unsafe paths, digest mismatches, dangling references, relationship cycles, and invalid EARS text.
  • CI passes on the seeded valid store.
  • A direct edit to a registered artifact is detected without staging unrelated files.
  • Local and CI diagnostics use the same stable machine-readable error shape.
  • The initial self-hosting fixture is reproducible from a clean checkout.

Out of scope

The Drafting Table, WMS, and Job Site integration remain in #66, #76, and #77.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing EM-07 and the command and validation behavior from EM-02 through EM-05, then locate the ears-manager workflow and .protobot seed path. Done means CI builds and tests the Go binary, runs ears-manager check as a merge gate, detects direct registered-artifact edits, and reproduces the valid self-hosting fixture from a clean checkout.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
ci-cd, devops, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.