8000 Staging toolchain, phase 2: named fixtures · Issue #476 · jra3/mulm · GitHub
[go: up one dir, main page]

Skip to content

Staging toolchain, phase 2: named fixtures #476

Open

Description

@jra3

Follow-up to #475. Add scripts/staging.sh fixture <name> for test data that staging checks need, created only on the baptest+ accounts so no real member is touched.

Fixtures we've already needed:

Same rules as the #475 seed: TypeScript in the container, refuses unless STAGING=1, uses the app's own DB functions, idempotent.

Activity

  1. added
    enhancementNew feature or request
    infrastructureInfrastructure, deployment, and DevOps
    needs-triageMaintainer needs to evaluate this issue
    on Oct 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestinfrastructureInfrastructure, deployment, and DevOpsneeds-triageMaintainer needs to evaluate this issue

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0