ls1intum/artemis/ci-triage

Triage a red Artemis build

Keep completed implementations available for CI and review

Use drafts only while the implementation is unfinished. Once implementation is complete, open the PR as non-draft or mark it ready for review immediately: full CI and review bots do not run on drafts. Pending or failing CI, reviews and test-server validation do not by themselves require draft status. Keep unverified checklist items open and require passing checks and approvals before merge; follow PR readiness.

Identify the failing check

gh pr checks <pr-number>
gh run view <run-id> --log-failed

The aggregate All required CI Passed is defined in .github/workflows/ci.yml. Trace the failing check through its called workflow; job names are prefixed by the caller (for example, Quality / Server Code Style). Check the repository's required-check settings before claiming that an advisory failure blocks merging.

PR and non-PR E2E jobs can use different topologies: a pull request runs one node, develop runs three nodes with Redis (Valkey) as distributed data provider. Compare their definitions in .github/workflows/ci-e2e.yml before treating a develop-only failure as flaky.

Classify before changing code

Use reference/known-failure-patterns.md to distinguish timeouts, architecture gates, missing workflow runs, and known harness failures from application defects. A single failure is not evidence of flakiness; compare logs and execution conditions.

A latest PR run that is pending with no jobs can be waiting for an obsolete run to release its concurrency slot. Follow the cancellation entry in the reference before rerunning or cancelling jobs.

Re-run when justified

• Server Tests: never use `gh run rerun --failed`. The suite's sharding and reporting mean a

partial re-run does not reproduce the original conditions. Use a full re-run: gh run rerun <run-id>.

• No run started at all: this is not something a re-run fixes. See the "no CI at all" and

"dropped event" entries in the reference file.

• A workflow file changed in the branch: classic PATs need the workflow scope to push it.

Check the triggering event and checked-out revision when identifying the workflow version.

Investigate Scorecard findings

Read the published report at https://api.securityscorecards.dev/projects/github.com/ls1intum/Artemis and check its date and commit before comparing it with the working tree. Branch-protection findings cover release branches as well as develop; missing release signatures refer to release assets, not just GitHub's attestation store.

Pin every external action, including actions/* and github/*, to a full commit SHA with a # vX.Y.Z comment. Resolve the upstream tag to its commit rather than guessing the hash. Renovate's helpers:pinGitHubActionDigests preset maintains these references. See .github/workflows/README.md for the workflow policy. Run actionlint -shellcheck= after editing workflows.

Reproduce a defect

Use skills/server-arch-gates/SKILL.md for architecture and style checks, skills/write-tests/SKILL.md for JUnit and Vitest, and skills/e2e-pr-check/SKILL.md for Playwright. Do not mask an unexplained failure with retries or a larger timeout.