redhat-et / redhat-et/ProtoBot
Implement the first GitHub WMS Adapter
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5
- Forks
- 6
- Avg merge
- 23h 24m
- Merged PRs (30d)
- 66
Description
Scope
Implement the first backend translator for GitHub Issues/Projects against the backend-neutral WMS contract. Start with request reads/writes, build-work-item materialization, dependency/status queries, and compare-and-swap behavior or the documented coordinator boundary.
Do not move lifecycle rules into GitHub-specific code. Do not implement Job Site scheduling or autonomous execution here.
Dependencies
- Validation Rules and in-memory WMS child issue.
- #31 contract.
Acceptance criteria
- GitHub-native records map to the ProtoBot request/work-item model without leaking backend concepts to callers.
- Materialization is idempotent under the stable key.
- Stale state/version updates are rejected safely.
- Integration tests use a fake HTTP/API boundary and cover transient failure and retry behavior.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading contract #31 and the Validation Rules and in-memory WMS child issue, then locate the ProtoBot request/work-item model and the fake HTTP/API boundary. Done means GitHub records map without backend leakage, materialization is idempotent, stale updates are rejected, and integration coverage includes transient failures and retries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go
- Domain
- backend-api-design, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100