Skip to content

REQ 031

sergio velderrain edited this page Nov 9, 2026 · 1 revision

REQ-031: Issues-enablement side effect never fails registration

Requirement

add-project.yml's best-effort Issues-enablement step for repositories referenced by a newly registered project shall never cause the registration itself to fail, even if ACTIONS_REPO_ADMIN_TOKEN is unset or a referenced repo's Issues-enable call fails.

Rationale

A registration's primary purpose (upserting PROJECTS_OVERRIDE/VIPM_TOML_CONFIGS) must not be blocked by an unrelated, lower-priority convenience side effect.

Fit Criterion

The "Enable Issue Tracking on Referenced Repos" step runs only after the upsert step has already completed and recorded success; a missing token or a per-repo failure inside it only emits a ::warning::, never a workflow failure.

Verification

Code review of .github/workflows/add-project.yml's "Enable Issue Tracking on Referenced Repos" step (conditioned on the upsert step's own output; every per-repo call is followed by a warning-only fallback, never exit 1).

Source

Software-Requirements-Specification

Priority

Medium

TestID

TEST-031

TestArtifact

Code review of the warning-only, never-exit-1 per-repo fallback

CodeRef

.github/workflows/add-project.yml "Enable Issue Tracking on Referenced Repos" step

Status

Verified (manual)

Clone this wiki locally