Have parity between pre confirmation statuses and `Success` and `Failed` statuses

Repository metrics

Stars

57,084 stars (57,084 stars)

PR merge metrics

Avg merge 8h 53m (Avg merge 8h 53m)1 merged PR in 30d (1 merged PR in 30d)

Description

This issue does not include a description.

Contributor guide

Research direction

Identify where pre confirmation statuses and Success/Failed statuses are defined and used. Look for inconsistencies in status mapping and ensure they are aligned.

Tech stack

rust

Domain

backendapi

Issue type

Bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

2

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

Active

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Mostly clear

Prerequisites

RustGit

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

60