Skip to content

feat(stovepipe): Serve repository status - #719

Open
prathshenoy wants to merge 3 commits into
mainfrom
codem-229-project-status-read
Open

prathshenoy wants to merge 3 commits into
mainfrom
codem-229-project-status-read

Conversation

@prathshenoy

@prathshenoy prathshenoy commented Sep 16, 2026

Copy link
Copy Markdown
Collaborator

Summary

What:

  • Return the current validation lifecycle and repository result for a commit.

Why:

  • Give consumers an authoritative status lookup for a validation run.

Test Plan

  • Add unit tests.

Revert Plan

  • Revert this PR. This will remove the read path; existing validation processing is unaffected.

Issues

Stack

  1. docs(stovepipe): Add status lookup RFC #717
  2. feat(stovepipe): Add status lookup contract #718
  3. @ feat(stovepipe): Serve repository status #719

@prathshenoy
prathshenoy force-pushed the codem-229-project-status-read branch from fe55251 to 1268b81 Compare September 16, 2026 19:22
@prathshenoy
prathshenoy force-pushed the codem-229-project-status-read branch from 1268b81 to 8ee4f90 Compare September 16, 2026 19:35
@prathshenoy
prathshenoy force-pushed the codem-229-project-status-read branch from 8ee4f90 to 8c616d8 Compare September 16, 2026 19:52
@prathshenoy
prathshenoy force-pushed the codem-229-project-status-read branch from 8c616d8 to 640e18e Compare September 16, 2026 21:38
@prathshenoy
prathshenoy force-pushed the codem-229-project-status-read branch from 640e18e to 24570d7 Compare September 16, 2026 21:48
@prathshenoy
prathshenoy force-pushed the codem-229-project-status-read branch from 24570d7 to 75d8c90 Compare September 16, 2026 21:55
@prathshenoy
prathshenoy force-pushed the codem-229-project-status-read branch 2 times, most recently from 6580c84 to 95abcb1 Compare September 16, 2026 22:06
@prathshenoy
prathshenoy added this pull request to stack #720 September 16, 2026 22:21
@prathshenoy
prathshenoy force-pushed the codem-229-project-status-read branch 2 times, most recently from a6c1ed5 to 012feb3 Compare September 17, 2026 03:42
@prathshenoy
prathshenoy force-pushed the codem-229-project-status-read branch from 012feb3 to f4c2fc8 Compare September 17, 2026 12:25
@prathshenoy
prathshenoy marked this pull request as ready for review September 17, 2026 13:42
@prathshenoy
prathshenoy force-pushed the codem-229-project-status-read branch from f4c2fc8 to 249c95e Compare September 17, 2026 16:10
@prathshenoy
prathshenoy force-pushed the codem-229-project-status-read branch from 249c95e to 57850cd Compare September 17, 2026 18:15
@prathshenoy
prathshenoy force-pushed the codem-229-project-status-read branch from 57850cd to d6876d8 Compare September 17, 2026 18:19
**What**:
- Define repository and project validation lookup semantics.
- Specify staged rollout, consistency, completion, and pagination behavior.

**Why**:
- Establish a stable public contract before implementation begins.
- Separate generic validation status behavior from repository-specific integrations.
**What**:
- Publish a queue-scoped validation-status lookup contract.
- Include repository status and future project-result response fields.

**Why**:
- Let consumers integrate against a stable validation-status interface.
- Preserve a compatible path to project-level results.
**What**:
- Return the current validation lifecycle and repository result for a commit.
- Distinguish unknown, pending, completed, and inconsistent validation records.

**Why**:
- Give consumers an authoritative status lookup for a validation run.
- Establish the read path before project-level results are available.
@prathshenoy
prathshenoy force-pushed the codem-229-project-status-read branch from d6876d8 to d8e8912 Compare September 18, 2026 14:37
Base automatically changed from codem-229-project-status-contract to main September 18, 2026 21:16
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