Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Operator limits: end-to-end journey of a limited workspace

Closed
  • Is something wrong?
#285 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
testing

Research direction

Start from the existing e2e stack under app/e2e/ and its fake GitHub and fake LLM, then read the TESTING.md entry format. This journey depends on children #269–#284, so most of its behavior is not yet built and cannot be run end to end. Done means the journeys T01–T09 run green against the fakes, with a plain no-entitlements journey alongside.

Written by the indexing model from the issue text.

Description

area: app type: chore

Part of #268. Depends on #269, #270, #271, #272, #273, #274, #275, #276, #277, #278, #279, #280, #281, #282, #283, #284.

Problem

Each child proves its own behavior at the lowest level. Nothing proves the whole chain a real operator relies on: a limited workspace runs, is refused, is told so on the pull request, is reset from outside, and its usage can be read — while an instance that never switched any of this on is untouched.

Behavior

One journey on the existing e2e stack (fake GitHub, fake LLM, the real runner where the stack already uses it), with a second, plain journey for an instance without entitlements.

Scope

An e2e journey under app/e2e/ plus the fake additions it needs, TESTING.md entry. No product change; findings go to new issues.

Out of scope

Real network or model calls, a real external service (a script plays its role over the operator API).

Test cases

ID kind level case expected
T01 regression e2e an instance with no operator token and no entitlements webhook → review → comment as before; operator routes are missing paths
T02 behavior e2e the script sets default entitlements (managed key, two Diff runs per period) and a tier configuration two pull requests are reviewed with the operator's key and the tier model; the fake LLM saw require_parameters
T03 behavior e2e a third review refused: run quota_exhausted, one notice on the pull request, no model call, no usage record
T04 behavior e2e the usage feed two settled records with measured cost and tier, in order, no model id, no repository data
T05 behavior e2e the script moves period_start forward the next push is reviewed
T06 behavior e2e the script suspends the workspace next review refused with the neutral notice; unsuspending restores it
T07 security e2e a member's views (settings, plan page, runs, usage, comments) contain no tier model id, key, amount or cost
T08 behavior e2e an Owner clicks Manage plan and the script redeems the token identity returned once; second redeem refused
T09 behavior e2e an own-key workspace on the same instance unaffected by the managed workspace's limits and tiers
Dominant language
TypeScript
Stars
0
Forks
1
Avg merge
1h 15m
Merged PRs (30d)
217

Getting set up

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.

More from ExpidetGames/code-reviewer

All issues in ExpidetGames/code-reviewer

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.