gen-api: CI drift check
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions, rust, typescript
- Domain
- build-system, ci-cd
Research direction
Start by reading parent issue #97, the rust-ci action, and tools/changed-crates.py to understand how changed crates map to frontends. Then inspect the gen-api declaration, generator configuration, and existing workflow files mentioned by the repository. Done means the CI check skips unrelated PRs, runs for affected frontends or all frontends when shared inputs change, catches an unregenerated schema change, and runs for every frontend on main.
Written by the indexing model from the issue text.
Description
Parent
#97
What to build
CI fails a PR whose committed specs or generated clients differ from what gen-api produces. A new workflow runs gen-api and requires an empty git diff. On PRs it runs only for frontends whose backend crate or its workspace dependencies changed (reusing tools/changed-crates.py, like the rust-ci action), or whose declaration, the shared script or the generator config changed. On main it runs for every frontend.
Acceptance criteria
- Deliberately changing a handler's schema without regenerating turns the check red; reverting turns it green
- A PR touching nothing gen-api-relevant skips the generation
- Changing the shared script or generator config runs it for all frontends
- On
mainthe check runs for every frontend and is green
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 14h 36m
- Merged PRs (30d)
- 24
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from myOmikron/code
-
wayfinder:task
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
wayfinder:task
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
myOmikron/code#102 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
mtg: Self-Rename of an AccountPossibly taken @omikron-agent claimed this today. Openready-for-agent
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Maintainers usually reply within 1 day
Similar issues
-
docs(api): openapi.yaml still documents gif-tools optimize colors as 2-256 instead of 2, 4, 16, 256Openarea: backend documentation priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
snapotter-hq/SnapOtter#2919 ·
Maintainers usually reply within 1 day
-
accepted :+1: bug db/redis
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
beekeeper-studio/beekeeper-studio#4882 · 1 comment ·
Maintainers usually reply within 1 day
-
ready-for-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
konflux-ci/konflux-ui#1630 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
ahmedkhaleel2004/gitdiagram#233 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
simkimsia/netlify-axi#19 ·
Maintainers usually reply within 1 day